mailnix Docs
    mailnix / Connect an MCP client

    MCP for AI agents

    Connect an MCP client

    The mailnix MCP server lives at https://mcp.mailnix.ch/mcp (streamable HTTP transport) and implements OAuth 2.1 with dynamic client registration, so any spec-compliant client can connect without pre-shared credentials.

    The universal recipe

    1. Point your client at https://mcp.mailnix.ch/mcp.
    2. The client discovers the authorization server automatically (RFC 9728 protected-resource metadata) and opens the mailnix consent page in your browser.
    3. Approve. If you are signed in to app.mailnix.ch, approve as your account and the session binds to it immediately; otherwise the session starts anonymous (sandbox-only) and can be claimed later.

    Per-client notes

    • Claude (Desktop / claude.ai / Claude Code): add a custom connector / remote MCP server with the URL above. OAuth runs in the browser on first use.
    • ChatGPT: add mailnix as a connector in Settings. ChatGPT requires the OAuth path; the consent page handles it.
    • Cursor: add the server under MCP settings with the URL above.
    • VS Code / Continue / Windsurf / Zed: all support remote MCP servers with OAuth; supply the URL and follow the browser flow.
    • MCP Inspector: paste the URL and use the built-in OAuth flow for interactive debugging.

    Headless / CI use: mint a token via client_credentials against the anonymous-bootstrap client for a sandbox session, or issue an API key in the dashboard (Settings, API keys) for the REST surface. See Authentication.

    First calls to make

    • account_status tells the agent whether the session is anonymous or claimed, plus quota state.
    • email_provider_list_presets, email_send_test, and email_trace_lookup cover the core send-and-debug loop.
    • The full catalog is on the tool reference.

    Troubleshooting

    • The server requires the MCP-Protocol-Version header on post-initialize requests; every current client sends it.
    • Sessions carry an Mcp-Session-Id; if your client loses it the server responds 404 and the client should re-initialize.
    • Tokens are audience-bound to https://mcp.mailnix.ch/mcp. A REST API key will not work on the MCP surface, and vice versa.