MCP Server

Let external AI tools read and write to your workspace.

Instead of switching apps to look something up, Claude Desktop or Cursor can search your OnePagers, read your transcripts, and even create sessions for you, all from inside the conversation you are already having.

Azynote's own Chat is tight, contextual, and scoped to what you are viewing. Exposing Azynote as an MCP server gives you Claude's or Cursor's full capabilities with your Azynote knowledge as a backend.

If you want to go the other way and plug external tools into Azynote's own chat, see MCP Client.

What this unlocks

• Ask Claude Desktop "what do we know about the Acme pricing discussion?" and Claude searches your notes, reads the relevant OnePagers, and synthesizes an answer.
• Ask Cursor to "find the session where the customer mentioned the SSO blocker" while you are coding a fix.
• Dictate a meeting summary to Claude and have it create a full session in Azynote, attach notes, and generate a OnePager, all in one prompt.
• Combine your Azynote workspace with other MCP servers (GitHub, Brave Search, your filesystem) in a single chat.

Set up in Azynote

1. Open Settings > AI Configuration.
2. Click Connect MCP Client.
3. A dialog appears with a ready-to-copy JSON config for your current workspace.
4. Click Copy to Clipboard.

The JSON is already personalized with your workspace path. The rest of the setup happens in the external client.

Connect Claude Desktop

1. Open the Claude Desktop config file at:

   ~/Library/Application Support/Claude/claude_desktop_config.json
   

2. Paste the JSON from Azynote into the mcpServers section. It will look like:

   {
     "mcpServers": {
       "azynote": {
         "command": "/Applications/Azynote.app/Contents/MacOS/Azynote",
         "args": ["--mcp-server", "--workspace", "/Users/you/AZYNOTE_NOTES"]
       }
     }
   }
   

3. Save the file.

4. Restart Claude Desktop. Config changes are only picked up on restart.

5. In a new Claude conversation, ask "what tools do you have from Azynote?" and you will see the list.

Connect Cursor

Cursor uses the same JSON format. Go to Cursor Settings > Extensions > MCP Servers and paste the same block. Restart Cursor to activate.

Other MCP-compatible clients follow a similar pattern. The JSON block Azynote generates works identically across them all.

Multiple workspaces

You can connect more than one workspace at the same time. Just add one MCP entry per workspace in your client config:

{
  "mcpServers": {
    "azynote-personal": {
      "command": "/Applications/Azynote.app/Contents/MacOS/Azynote",
      "args": ["--mcp-server", "--workspace", "/Users/you/Personal"]
    },
    "azynote-work": {
      "command": "/Applications/Azynote.app/Contents/MacOS/Azynote",
      "args": ["--mcp-server", "--workspace", "/Users/you/Work"]
    }
  }
}

Claude will see both and can switch between them in the same conversation.

What external AI can do

Once connected, the external AI has access to a full set of Azynote actions, grouped by purpose:

• Explore: list your subjects, sessions, OnePagers, and recent activity.
• Search: keyword and semantic search across your whole workspace.
• Read: pull the notes, transcripts, and attachments from any session. Ask targeted questions about a single session.
• Create: start a new subject, open a session, write a note, attach a file, produce a OnePager.
• Organize: tag subjects, add links, rename sessions, link sessions to multiple subjects, update one-line summaries.
• Manage workspaces: switch workspaces, list them, create a new one.

In practice: anything you can do in the UI, Claude or Cursor can do for you over MCP.

Good to know

• The main Azynote app does not need to be running. The MCP server runs as a separate headless process, started on demand by your AI client.
• Local only. Communication happens over stdio, not a network port. Only processes on your machine can talk to the server. No authentication is required because no network exposure exists.
• Workspace is fixed per entry. Each MCP entry in your client config is bound to one workspace. Switching workspaces in Azynote's UI does not change what the MCP server sees, and vice versa.
• Restart the client after config changes. Claude Desktop and Cursor cache the MCP config at launch.