We are adding support for the Model Context Protocol (MCP) in Agenda 22.2 for macOS. MCP is an open standard that allows AI assistants like Claude and Codex to interact directly with your apps. With MCP enabled, your AI assistant can search, read, create, and edit notes in Agenda — all from the conversation.
MCP is disabled by default. You can find it in Agenda > Integrations, where you can enable the server and copy the configuration for your AI tool of choice.
If you can’t get it configured, often the best thing to do is ask the AI Assistant itself for instructions.
What does it allow you to do? Here are some examples:
Ask your AI assistant to find notes by text, tags, people, or dates
Have it read the full content of a note and summarise or analyse it
Create new notes, projects, or categories from a conversation
Append action items or follow-ups to existing notes
Mark notes as completed, on the agenda, or pinned
Open a specific note in Agenda from your AI assistant
Ask for help on any Agenda topic, or links to videos
Anoteonprivacy: Agenda’s MCP server runs locally on your Mac and does not upload your data anywhere. However, any note content retrieved by your AI assistant will be sent to that assistant’s cloud service (e.g. Anthropic, OpenAI) as part of the conversation. Only enable MCP if you are comfortable with this.
If the file already has other MCP servers, just add the “agenda” entry to the existing mcpServers object. Then restart Claude for Desktop to pick up the change.
If the agenda server actually speaks raw HTTP (request/response) rather than SSE (streaming), then Claude Desktop may not support it natively yet. In that case you’d need a proxy or adapter that bridges HTTP to stdio or SSE. But try "sse" first — many MCP servers that expose an HTTP endpoint are actually SSE under the hood.
The error is clear: Claude Desktop is looking at mcpServers.agenda.command and finding it undefined. It expects every MCP server entry to have a "command" field (stdio format). It doesn’t support "type": "sse" or "type": "http" at all — at least not in your version.
So Claude Desktop simply doesn’t support URL-based/remote MCP servers in its config. Every server must be a local process it can spawn.
Your options:
Run agenda via a stdio wrapper. If the agenda MCP server has a CLI/npx package, use that instead — same pattern as your Readwise entry.
Better for most users to have an MCP that works with Claude Desktop (like Readwise, Craft, and several others), than depending on Claude Code which is great for coders and command line enthusiasts, but I image not for the bulk of the population.
I suggest considering Claude’s advice and get some experienced help on coding this piece.
(FWIW, the command Agenda provided works fine in the Claude CLI.)
Yeah, I’ll see what I can do. It’s tricky with a sandboxed app. Every other MCP server I’m seen for Mac app has been this HTTP type.
I’ll leave the final word to Claude Desktop itself…
The irony is that the HTTP/SSE approach is actually the right architecture for a sandboxed Mac app. Agenda can spin up a local server on a port, stay within its sandbox, and serve MCP that way. It’s Claude Desktop that’s the bottleneck by not supporting remote transports yet.
Update: I’m looking into an option to provide a plugin that you can add straight to Claude Desktop.