Zadano MCP — plan
A personal remote Model Context Protocol server with four tools: memo_write, memo_search, upload and transcribe. This page says what the tools do, how sign-in works and what data the server keeps.
| MCP endpoint | https://mcp.zadano.app/mcp (Streamable HTTP, POST) |
|---|---|
| Protocol | MCP 2026-07-28 (stateless, per-request metadata, server/discover). Clients on 2025-11-25 and older revisions with an initialize handshake are served too, without sessions. |
| Access | OAuth 2.1 bearer token. Only clients the owner approved get one. |
| Protected resource metadata | https://mcp.zadano.app/.well-known/oauth-protected-resource/mcp |
What the tools do
Every tool declares an input schema and an output schema in tools/list. Every result carries structuredContent that matches the output schema, and the same JSON as a text block. A failure the caller can fix comes back as a tool result with isError: true and a plain message.
memo_write — save a note
Input { text }. Saves the text exactly as given in the notebook of this server. Result { id, created_at }.
memo_search — find notes
Input { query, limit? }. Looks for the words of the query in all notes, ignoring case. A note matches when it contains at least one word; notes with more matching words come first, then newer notes. An empty query lists the newest notes. Result { notes: [{ id, text, created_at, author }], total }, where author is the name of the client that saved the note.
The notebook is shared: there is one notebook, and every approved client reads and writes the same notes.
upload — put a file on the server
Input { filename, content?, encoding?, source_url?, mime_type? }. Send the file bytes as base64 in content, or text with encoding: "utf8", or give source_url and the server downloads the file. Limit 15 MB. Result { url, id, filename, size, mime_type, sha256 }.
url is a link on this server, https://mcp.zadano.app/files/…. Anyone who has the link can open it; no sign-in. The link holds a random 128-bit id, so it cannot be guessed, but it is public: do not upload what must stay private.
transcribe — audio to timestamped text
Input { url, language? }. Downloads the audio or video file at the URL (up to 50 MB; a link from upload works) and runs a Whisper speech model on this server. Result { segments: [{ start, end, text }], text, language, duration }. start and end are seconds from the beginning of the audio. The audio is not sent to any third party.
How sign-in works
The server follows the MCP authorization specification. It is an OAuth 2.1 resource server, and it runs its own small authorization server on this host (issuer https://mcp.zadano.app).
- A request to
/mcpwithout a valid token gets401with aWWW-Authenticate: Bearerheader. Itsresource_metadatapoints to the protected resource metadata (RFC 9728), which names the authorization server and this page. - The client reads the authorization server metadata (RFC 8414) at
https://mcp.zadano.app/.well-known/oauth-authorization-server. - The client identifies itself. Preferred: a Client ID Metadata Document — the
client_idis an https URL of a JSON document withclient_id,client_nameandredirect_uris. Also accepted, for older clients: dynamic client registration (RFC 7591) at/register. - The client sends the user's browser to
/authorizewith PKCE (S256, required) andresource=https://mcp.zadano.app/mcp. - The browser shows a consent page with the client's name, id and redirect address. Only the owner of this server can approve: the page asks for the owner password. Nobody else can let a client in, and there is no self-service sign-up.
- After approval the browser returns to the client with a one-time code and the issuer (
iss, RFC 9207). The client exchanges the code at/tokenfor an access token (valid 1 hour) and a refresh token (valid 30 days, rotated on every use). - The client sends
Authorization: Bearer …on every request. Tokens are bound to this server (https://mcp.zadano.app/mcp) and carry the scopemcp, which covers all four tools.
Access ends when the token expires without refresh, when the client calls /revoke, or when the owner deletes the grant on the server.
What data the server keeps
| Data | What is stored | How long |
|---|---|---|
| Notes | The note text, the time, and the id and name of the client that saved it. | Until the owner deletes them. |
| Uploaded files | The file bytes, file name, content type, size, SHA-256, upload time and the id of the uploading client. | Until the owner deletes them. |
| Transcripts | The transcript, keyed by the SHA-256 of the audio, so a repeated call answers at once. Audio fetched from other hosts is processed in memory and not stored. | Until the owner deletes them. |
| Clients | For registered clients: the name, redirect addresses and, if the client asked for one, a hash of its secret. Metadata documents are fetched when needed and cached in memory for 5 minutes. | Unused registrations are removed over time. |
| Tokens | Only SHA-256 hashes of access and refresh tokens, with the client they belong to and the expiry time. One-time codes are deleted on use. | Deleted after expiry: 1 hour (access), 30 days (refresh). |
| Logs | Operational logs of the reverse proxy and the server: time, path, status, client id on approval. No note text, file content, passwords or tokens. | Rotated by the host. |
The server sets no cookies and uses no analytics or third-party services. All data stays on one virtual server in the EU. The owner password is never stored in the database.
Machine-readable: protected resource metadata · authorization server metadata