Skip to main content

Connect other AI clients to Mixmax (MCP)

Connect Cursor, Windsurf, or any other MCP-compatible client to Mixmax over the Mixmax MCP server.

Beta: The Mixmax MCP server is in beta, available through Mixmax Labs at no extra cost. As it matures, some capabilities may become part of specific Mixmax plans.

Any MCP client that supports Streamable HTTP can connect to Mixmax. This article covers Cursor, Windsurf, and a generic setup for everything else. For Claude, see Connect Claude to Mixmax (MCP). For ChatGPT, see Connect ChatGPT to Mixmax (MCP).

Server details

  • URL: https://mcp.mixmax.com/mcp

  • Transport and auth: Streamable HTTP, OAuth 2.1

Before you start

Turn on the MCP server experiment in Mixmax Labs: open Settings & feedback in the sidebar's Mixmax Labs section and toggle the experiment on. Enabling it adds MCP settings to your sidebar, where per-capability permissions live. For how Labs works, see Mixmax Labs overview.

Cursor

  1. Open Customize in the sidebar, then go to the MCP servers section.

  2. Add a new server, or edit your mcp.json directly:

    {
  "mcpServers": {
    "mixmax": {
      "url": "https://mcp.mixmax.com/mcp"
    }
  }
}

  3. Save, then authenticate in the browser when prompted.

Windsurf

  1. Open Settings, then Tools, then Windsurf Settings, and click Add Server. Or click View Raw Config to edit mcp_config.json directly:

    {
  "mcpServers": {
    "mixmax": {
      "serverUrl": "https://mcp.mixmax.com/mcp"
    }
  }
}

  2. Press the refresh button after adding the server, then authenticate in the browser when prompted.

Any other MCP client

Point the client at https://mcp.mixmax.com/mcp using its remote or HTTP server option. The client must support two things: the Streamable HTTP transport, and OAuth 2.1 authorization. No API key is involved; sign-in happens in the browser.

Signing in

The first time your client calls Mixmax, the server answers with a 401. That's expected, not an error — it kicks off the sign-in flow:

  1. A browser window opens to the Mixmax sign-in page.

  2. Sign in and approve access.

  3. The client retries the original request and your data appears.

You stay signed in after that. You'll only be asked again after 90+ days of inactivity, or if an admin revokes access.

Try your first query

Start with a question you already know the answer to:

  • "What meetings do I have this week?"

  • "List my sequences."

When you recognize the answer, you're connected. Start with reads — write capabilities are separate per-user levers in MCP settings.

Troubleshooting

Symptom

What it means

A tool is missing, or a write returns a permission error

That's your permission lever, not a bug. Reads are on by default; writes are opt-in. Turn the capability on in MCP settings in Mixmax.

The Labs experiment card isn't visible

Your admin turned it off or locked it, or the rollout hasn't reached your workspace yet.

401 on the first call

Expected. It triggers the browser sign-in flow.

The client can't connect at all

Confirm the client supports Streamable HTTP and OAuth 2.1, the URL is exactly https://mcp.mixmax.com/mcp, and the experiment is on in Mixmax Labs.

Learn more

Related Articles
Did this answer your question?