Documentation

Memo / Todo MCP integration guide

Memo and Todo share the Streamable HTTP endpoints /mcp and /mcp/readonly. A credential's scopes determine which tools the client can see and call.

Quick start

1. Open Settings → Access tokens, create a token, and copy it immediately. It cannot be displayed again.
2. Select memo:read or todo:read for read access. Add the matching *:write scope for create, update, and delete operations.
3. Use https://<your-host>/mcp/readonly for read-only clients, or https://<your-host>/mcp when writes are needed.
4. Add Authorization: Bearer <your-token> to the client configuration. The client performs initialize and manages the session.

Tokens expire after 90 days by default; 30-day and non-expiring options may also be available. Revoke a token immediately if it may have leaked.

Cursor example

{
  "mcpServers": {
    "mesq": {
      "url": "https://<your-host>/mcp/readonly",
      "headers": { "Authorization": "Bearer <your-token>" }
    }
  }
}

Access model

The X-MCP-Readonly: true header also forces read-only mode. OAuth and personal access tokens support the same Memo and Todo scopes.

Sessions

The response header Mcp-Session-Id identifies the session. Send it on later requests. Inactive sessions expire after about 30 minutes. Multi-instance deployments must route a session consistently by this ID.

Memo tools

Memo tools cover listing, keyword and semantic search, reading, creating, updating, soft deletion, tag management, and attachment upload/read. Use upload_memo_resource first, then pass its path to create_memo when creating a memo with attachments.

MCP attachment resources use memo://resource/{encodedPath}. Base64 reads are intended for files up to 5 MB; larger supported files should be read through MCP resources or their authenticated preview URL.

Todo tools

Use get_todo_context to discover spaces, columns, boards, and inboxes. Use create_todo_inbox_item for quick capture and create_todo_task for a specific board column. Todo attachments use todo://attachment/{encodedPath}.

Toolsets can be narrowed with X-MCP-Toolsets, including todos, todo-spaces, todo-columns, todo-inbox, todo-attachments, and todo-trash.

Content limits

Troubleshooting

The server does not currently expose MCP prompts or resources/subscribe. User-created Memo and Todo content is always returned in its original language.