MCP Clients

Not a coding tool? If you are a personal AI assistant such as Grok Bot, Meta Muse, OpenClaw, Instinct, or Poke, or you are setting one up, this is not your page. Go to Personal AI Agents.

For Claude Code, Claude Desktop, Cursor, and Codex, the recommended setup is the Bland plugin: the MCP server plus skills for every part of the platform, /bland:* commands, and Norm, the agent builder. Start there. This page is for everything else: clients the plugin does not cover (VS Code, Windsurf, Gemini CLI, your own agent loop), and the four plugin hosts when you want the bare toolset with nothing layered on top.

Prerequisites

Your Bland API key from the dashboard
For every client, the same two values:
- URL: https://api.bland.ai/v1/mcp
- Header: Authorization: Bearer YOUR_BLAND_API_KEY

Prefer the Bland plugin here; it does the most in Claude Code. For the server alone, add it in one command:

claude mcp add --transport http bland https://api.bland.ai/v1/mcp \
  --header "Authorization: Bearer $BLAND_API_KEY"

Verify the connection:

claude mcp list

claude mcp list showing the bland server connected

Inside a session, run /mcp to see the server’s tools, or just ask:

> list my pathways and tell me which ones have no published version
> pull the transcript of my last call and explain where the agent went off script
> create a pathway that qualifies inbound leads and books a demo

By default claude mcp add configures the server for the current project only. Add --scope user to make it available in every project.

A Claude Code session using the Bland MCP to list pathways and report which have a published production version

Prefer the Bland plugin from the Cursor marketplace. For the server alone, use the one-click install:Install in CursorAfter installing, open Cursor Settings → MCP and replace YOUR_BLAND_API_KEY with your real key.Or add it by hand to ~/.cursor/mcp.json (global) or .cursor/mcp.json in your project:

{
  "mcpServers": {
    "bland": {
      "url": "https://api.bland.ai/v1/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_BLAND_API_KEY"
      }
    }
  }
}

Restart Cursor (or toggle the server in Settings → MCP) and the Bland tools appear in the agent’s tool list.

Tools that place calls or publish agents have real-world side effects. Keep Cursor’s tool-approval prompts on for the Bland server rather than auto-approving everything.

Prefer the Bland plugin, which installs into Codex from the same marketplace. For the server alone, add to ~/.codex/config.toml:

[mcp_servers.bland]
url = "https://api.bland.ai/v1/mcp"
bearer_token_env_var = "BLAND_API_KEY"

Export BLAND_API_KEY in your shell profile, then restart Codex. If your Codex version has trouble with HTTP servers, use the stdio bridge in the Any client tab.

Install in VS Code, or add to .vscode/mcp.json:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "bland-api-key",
      "description": "Bland API key",
      "password": true
    }
  ],
  "servers": {
    "bland": {
      "type": "http",
      "url": "https://api.bland.ai/v1/mcp",
      "headers": {
        "Authorization": "Bearer ${input:bland-api-key}"
      }
    }
  }
}

VS Code prompts for the key on first use and stores it securely. It never lands in the config file.

Prefer the Bland plugin, which installs into Claude Desktop and stores the key for you.Without the plugin, Claude Desktop’s custom connectors expect OAuth, so use the stdio bridge with your API key instead. Add to claude_desktop_config.json (Settings → Developer → Edit Config):

{
  "mcpServers": {
    "bland": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://api.bland.ai/v1/mcp",
        "--header", "Authorization: Bearer ${BLAND_API_KEY}"
      ],
      "env": { "BLAND_API_KEY": "org_your_key_here" }
    }
  }
}

Requires Node.js 18+. Restart Claude Desktop after saving.

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "bland": {
      "serverUrl": "https://api.bland.ai/v1/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_BLAND_API_KEY"
      }
    }
  }
}

Add to ~/.gemini/settings.json:

{
  "mcpServers": {
    "bland": {
      "httpUrl": "https://api.bland.ai/v1/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_BLAND_API_KEY"
      }
    }
  }
}

For clients not listed here (or your own agent loop), either:Native HTTP: configure a streamable-HTTP MCP server with the URL and header above.Stdio bridge: if the client only supports stdio servers, mcp-remote bridges any of them to the Bland endpoint:

npx -y mcp-remote https://api.bland.ai/v1/mcp \
  --header "Authorization: Bearer $BLAND_API_KEY"

Raw JSON-RPC: the endpoint is plain HTTP POST, so you can drive it directly:

curl -X POST https://api.bland.ai/v1/mcp \
  -H "Authorization: Bearer $BLAND_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

Next steps

Bland plugin

The recommended setup for Claude Code, Claude Desktop, Cursor, and Codex.

Tool reference

Everything the MCP server can do.

Docs for agents: llms.txt

Welcome

Getting Started

Core Bland Features

AI Agents & MCP

Basic Tutorials

Advanced Features

Platform Information

SDKs & Tools

Bland Enterprise

Prerequisites

Next steps

Bland plugin

Tool reference

​Prerequisites

​Next steps

Bland plugin

Tool reference

Prerequisites

Next steps