memos
English中文
Sign in

DocumentationAPI reference

Rust · 0.1.0

MCP tool catalog

Use the discovered tool schema, including its body wrapper, rather than copying a REST request verbatim.

See MCP setup and security before connecting a client. The links below describe the REST contracts used by the tools, not a promise that every REST operation is an MCP tool.

Tool names and arguments

The catalog derives names such as memo_list_memos and memo_create_memo from selected operation IDs. Path and query inputs are top-level tool arguments; a REST JSON payload goes under body. For example, the create tool takes body.content rather than a top-level content argument. tools/list supplies the authoritative inputSchema and annotations for the connected version; the catalog adjusts several shared REST schemas to the operation's actual writable input.

{"name":"memo_list_memos","arguments":{"pageSize":20,"filter":"pinned == true"}}

Identity, safety and errors

The adapter forwards the bearer Authorization header to the same REST implementation. It does not forward a browser's refresh cookie or grant additional privileges. Tool annotations are hints for client presentation, not user authorization. Writes, deletions, invitations and replacement operations still have real effects. An operation failure returns a tool result with isError: true and a text explanation; inspect that result instead of assuming the JSON-RPC exchange means the action succeeded.

Selected operations