Connect an AI Client (MCP)

Try asking: “”

The Claude Code CLI. Works with either method.

Method A (sign-in)

claude mcp add --transport http  

Claude Code opens a browser sign-in the first time it uses a tool from the server.

Method B (bearer token)

claude mcp add --transport http   \
  --header "Authorization: Bearer YOUR_TOKEN"

Try asking: “”

Method A. Requires Developer Mode on a paid plan.

1. Enable Developer Mode.
2. Settings > Connectors > Create.
3. Enter , set Authentication to OAuth.
4. Save and complete sign-in.

HTTPS remote endpoints only. If the connector offers Bearer instead of OAuth, use method B.

Try asking: “”

Add the server to an mcp.json file - project-level (.cursor/mcp.json) or global (~/.cursor/mcp.json).

Method A (sign-in)

{
  "mcpServers": {
    "": {
      "url": ""
    }
  }
}

Cursor discovers the sign-in page automatically and opens it in your browser the first time a tool is used - no Client ID/Secret needed in the file.

Method B (bearer token)

{
  "mcpServers": {
    "": {
      "url": "",
      "headers": { "Authorization": "Bearer YOUR_TOKEN" }
    }
  }
}

Try asking: “”

MCP Client by Zapier - either method.

1. Apps > + Add connection → search MCP Client.
2. Paste , choose Streamable HTTP.
3. OAuth yes → method A sign-in. OAuth no → paste a bearer token from the curl example (refresh every 24h).

Try asking: “”

Use MCP Client Tool with Bearer auth (method B).

1. Add the node and wire it to your AI Agent.
2. Endpoint , Transport HTTP Streamable.
3. Authentication → Bearer; paste a token from the curl example.
4. Fetch tools, pick which to expose, save.

Try asking: “”

Use the MCP Client app (either the “Call a tool” or “Execute an action with AI” module).

1. Add an MCP Client module to your scenario and create a new connection.
2. Choose + new MCP server and paste .
3. If Make detects OAuth support it prompts a sign-in (method A). Otherwise, a credential field appears below the URL - paste a bearer token from the curl example (method B).

For any other MCP-compatible client, or a custom integration you're building yourself.

OAuth-capable clients (method A)

Our servers support standard OAuth 2.1 discovery (RFC 8414) and dynamic client registration (RFC 7591). Point a compliant client at the URL below with no credentials in the config - it will discover the sign-in page on its own, the same way Claude and Cursor do:

{
  "mcpServers": {
    "": {
      "url": ""
    }
  }
}

Header / bearer-token clients (method B)

If your client can only send a static header, mint a token with the curl example above and set it directly:

{
  "mcpServers": {
    "": {
      "url": "",
      "headers": { "Authorization": "Bearer YOUR_TOKEN" }
    }
  }
}

Not every client uses this exact JSON shape - treat it as a reference for the two required pieces: the MCP URL, and (if needed) the bearer header.