You want help finishing a launch brief. The current draft, an unresolved download question, and earlier decisions are already in your task notes. Reconstructing them in a new chat means deciding what to copy and whether it is still current.
With MCP, a compatible AI client can use tools to retrieve that material from TodoNote. This guide walks through an illustrative first session: find the task, read the evidence, propose a next step, and check a requested change. Example notes and responses are demonstrations, not a transcript or a guarantee of an AI client's behavior.
Prepare one task with enough context
Start with a task titled “Prepare the launch brief for trial users.” Add the latest draft or a link to it, a short statement of current progress, and any unresolved questions. If your note only says “finish this,” the agent has little reliable context to retrieve.
Prepare the launch brief for trial users
Current state: Draft ready; the product image still needs updating.
Decision: Focus on two changes that matter to existing trial users.
Open question: Has the Windows download link been verified?
Next: Verify the link before final review. This note does not yet contain a verification result.
Keep the record understandable before connecting
A useful title makes the task easier to find. Separate completed checks from open questions so a summary cannot reasonably confuse them. If several tasks have similar names, retain enough detail to distinguish the correct release.
You can use the working-note outline to prepare this information. You do not need a separate document written specially for AI.
Connect a compatible remote MCP client
Use a client that supports remote MCP over HTTP and OAuth authorization. Settings labels vary by client; the following steps describe the connection without assuming a particular interface.
Server URL
https://web.todonote.app/api/mcp- Add a remote MCP server using the address above.
- Sign in to your TodoNote account when authorization opens.
- Read the requested permissions before approving, then return to the client and check that its tools are available.
Read access permits the client to retrieve account data through the available read tools. Write access additionally permits changes through write tools and includes read access. The permissions are not a per-task sharing switch: naming one task in a prompt does not technically restrict the connection to that task.
If the client supports requesting read-only access, that is sufficient for the retrieval exercise below. Otherwise, review the actual request before deciding whether to approve it. See the security and data access overview for more context.
Find the title, then read the note
Find tasks with “launch brief” in their title. If more than one looks relevant, show the candidates and ask which to use. Read the chosen task and its note. Summarize its current state, unresolved questions, and suggested next steps. Name the source task and distinguish recorded facts from your suggestions. Do not modify anything.
TodoNote's MCP task search matches text in task titles. It does not search every document's body. Finding a task and reading its note are separate steps, so a search result alone is not enough to summarize the work. If a keyword appears only in the note, try a known title fragment or ask the client to list candidate tasks first.
For the illustrative note, a grounded response would say the draft is ready, the image needs updating, and download verification remains open. It should not claim the download works: the source contains no such result. Suggestions for a review checklist should be labeled as suggestions.
Check the named task, its status, and the cited note before accepting the summary. If the agent found nothing or could not read the document, resolve that gap before asking it to plan from memory.
The tool calls behind that request
search_tasks— Search a title fragment, such as “launch brief”, and confirm which task to use.get_task— Check its ID, status, tags, and direct subtasks.get_task_document_markdown— Read the actual note before summarizing it. The title and metadata alone do not contain the draft.
Approve a specific change and inspect the result
Create a subtask called “Verify the Windows download link” under the launch-brief task we just reviewed. In its note, say to open the release download page, check the Windows link, and record the result. Do not set a date, mark anything complete, or change the parent note. Return the created task's ID.
This step requires write permission. Open the result in TodoNote and check its title, parent, note, and status. Before retrying a request that timed out, look for the task: the write may have succeeded even if the client did not receive the response.
“Ask me before editing” is an instruction to the AI client, not an additional permission enforced by the server. When a connection has write access, its available write tools can change data. Keep the distinction clear when choosing what to authorize.
For the new follow-up, the client uses create_task with the confirmed parentId. It then writes the instructions into the returned task ID with set_task_document_markdown. Check both the created task and its note: creating the title alone does not save the instructions.
If the first attempt fails
- No connection: Check the endpoint and that the client supports remote HTTP MCP with OAuth. A local-command-only integration uses a different setup.
- No matching task: Check the signed-in account and search a title fragment, rather than a phrase found only in the body.
- Read works, write does not: Review the granted scope and whether the client exposes the write tools.
- The answer lacks evidence: Ask which task and note were actually read. Correct missing context before requesting an update.
A useful first session ends with a summary you can trace to your records and, if requested, a change you have inspected. You can continue using TodoNote without connecting an AI client.