MCP Client

Plug external MCP servers into Azynote so the chat can use them.

Plenty of MCP servers already exist. GitHub, Brave Search, filesystem browsers, web scrapers, Slack, Notion, and more. When you connect one of them to Azynote, its tools become available to Azynote's agent during chat. Ask "pull the last three issues I opened on GitHub" and Azynote uses the GitHub MCP server to get them.

If you want to go the other way and expose Azynote's data to Claude Desktop or Cursor, see MCP Server.

Add a server

  1. Open Settings > AI Configuration > MCP Servers.
  2. Turn on Enable MCP Integration (the global switch at the top).
  3. Click Add Server in the "Configured Servers" section.
  4. Fill in the form:
    • Server Name (for example, github)
    • Description (optional)
    • Transport: pick Stdio (runs a local command) or HTTP (connects to a URL)
    • For Stdio: the Command to run (for example npx) and Arguments (for example -y @modelcontextprotocol/server-github)
    • For HTTP: the URL and the Auth type (None or OAuth 2.0)
    • Timeout (default: 30 seconds)
    • Allowed Tools: an optional comma-separated whitelist. Leave empty to expose all tools from that server.
  5. Click Test to validate the connection. Azynote spawns the command or pings the URL and reports how many tools are available, or what error came back.
  6. Click Save.

See it working

Each configured server appears as a card with:

  • The transport type and endpoint (for example, "Stdio: npx" or "HTTP: http://localhost:3000/mcp")
  • An enable/disable toggle
  • An auth status badge ("Not Authenticated" / "Authenticated" / "Token Expired") for OAuth servers
  • Edit, Delete, and Test buttons
  • The last test result, with a tool count or the error message

Disabled servers stay in the list but are not started. Enable one and its tools light up in the next chat message.

Tools become available automatically

Once a server is enabled, Azynote's chat agent picks up its tools without any extra step. Tools are namespaced by server to avoid collisions: a GitHub MCP server's create_issue tool appears to the agent as github_create_issue.

You do not call tools directly. Ask the chat a question in plain language and the agent decides which tool to use and when.

Authenticate an HTTP server

Some HTTP MCP servers require OAuth. For those, the server card shows an Authenticate button.

  1. Click Authenticate. Azynote opens your browser.
  2. Sign in on the provider's page and grant access.
  3. Azynote receives a token and stores it inside your workspace.
  4. The badge turns green: Authenticated.

When the token expires, the badge turns amber. Click Re-authenticate to refresh it. Revoke removes the stored token.

Good to know

  • Workspace-scoped. Your MCP client configuration lives in the current workspace. Different workspaces can have different sets of external servers enabled.
  • Stdio servers run commands on your Mac. Adding a server means giving it permission to run its command with its arguments. Only add servers from sources you trust.
  • External runtimes are your responsibility. Many MCP servers need Node.js, Python, or other tools to be installed. If the Test button returns "command not found", install the prerequisite and try again.
  • Tool filtering. Use the Allowed Tools whitelist to restrict a server to a safe subset, for example only read-only operations.
  • Auto-start. Enabled servers start automatically when Azynote launches. Disabled servers stay dormant until you toggle them.