TodoNote MCP

What TodoNote MCP does

TodoNote MCP exposes TodoNote task and note operations to AI agents through the Model Context Protocol. It supports reading existing tasks and notes, creating new tasks, and updating records. The server is intended for workflows where an agent needs to inspect or modify information held in TodoNote.

Its remote HTTP design makes TodoNote available as a hosted MCP endpoint rather than as a locally run process. That distinction matters when selecting an MCP connection method: the agent connects to a remote service, while TodoNote MCP handles the communication with the TodoNote workspace.

How it works

An MCP-compatible client connects to the remote TodoNote MCP endpoint over HTTP. The agent can then invoke the server's supported operations for retrieving TodoNote content or changing records. Read operations cover tasks and notes; write operations include task creation and record updates.

Access is granted through OAuth permissions. Those permissions determine the access an agent receives when it uses the server, so the authorization step is part of the connection between the client, TodoNote MCP, and TodoNote. This makes the server suitable for agent workflows that need authenticated access to workplace and productivity data.

Tools and capabilities

TodoNote MCP supports the following operations:

• Read TodoNote tasks.
• Read TodoNote notes.
• Create tasks in TodoNote.
• Update TodoNote records.
• Use OAuth-granted permissions for authorized access.

Together, these capabilities cover a basic task-management loop: an agent can inspect existing work, review related notes, add a task, and modify records. The available operations are focused on TodoNote data rather than general-purpose project-management or document systems.

Limitations and notes

TodoNote MCP is centered on TodoNote tasks, notes, and records. Its connection model is remote HTTP, and its access model uses OAuth-granted permissions. Developers should therefore choose an MCP client and deployment configuration that can connect to a remote HTTP server and complete the required authorization flow.

The server's documented scope is limited to reading tasks and notes, creating tasks, and updating records. Workflows requiring other TodoNote actions should be evaluated against the operations exposed by the server before adoption.