> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vobiz.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Server

> Connect Claude, Cursor, VS Code, and other AI clients directly to the Vobiz documentation through the Model Context Protocol (MCP). Step-by-step setup with npx and native configs.

The Vobiz docs ship with a hosted **Model Context Protocol (MCP)** server. Point any MCP‑aware client - Claude Desktop, Claude Code, Cursor, VS Code, ChatGPT desktop - at it and the assistant can search and read every page of these docs in‑context, so answers stay current with the live site instead of the model's training snapshot.

## Install with one command

```bash theme={null}
npx add-mcp https://docs.vobiz.ai/mcp
```

That's it. `add-mcp` scans your machine for installed MCP clients (Claude Desktop, Claude Code, Cursor, VS Code, Windsurf…), shows a checklist of which ones to wire up, writes the right config block to each, and prompts you to restart anything that needs it. The command is idempotent - re‑run it any time you install a new client.

```text Server endpoint theme={null}
https://docs.vobiz.ai/mcp
```

* **Transport:** Streamable HTTP (no auth, public).
* **What it exposes:** full‑text search and page fetch across the Vobiz documentation site.
* **What it is not:** this is **not** the Vobiz REST or Partner API - it only reads docs. For programmatic call/account access, use the [API Reference](/account) instead.

## Prerequisites

* An MCP‑aware client (Claude Desktop, Claude Code, Cursor, VS Code 1.99+, etc.).
* **Node.js 18+** for `npx`. If `node --version` prints `v18` or higher, you're set.
* An internet connection - the server is hosted, nothing runs locally.

## Manual setup per client

If you'd rather wire each client up by hand (or `add-mcp` didn't detect yours), the sections below show the exact config for each.

### Claude Desktop

Claude Desktop currently launches MCP servers over stdio, so you wrap the hosted HTTP endpoint with [`mcp-remote`](https://www.npmjs.com/package/mcp-remote). No global install needed - `npx` fetches it on first run.

<Steps>
  <Step title="Open the config file">
    * **macOS:** `~/Library/Application Support/Claude/claude_desktop_config.json`
    * **Windows:** `%APPDATA%\Claude\claude_desktop_config.json`
    * **Linux:** `~/.config/Claude/claude_desktop_config.json`

    If the file doesn't exist yet, create it with `{}` as its content.
  </Step>

  <Step title="Add the Vobiz server">
    Merge this block into your config:

    ```json claude_desktop_config.json theme={null}
    {
      "mcpServers": {
        "vobiz-docs": {
          "command": "npx",
          "args": ["-y", "mcp-remote", "https://docs.vobiz.ai/mcp"]
        }
      }
    }
    ```
  </Step>

  <Step title="Restart Claude Desktop">
    Quit Claude fully (⌘Q on macOS) and reopen it. The new tools surface under the 🔌 / hammer icon in the prompt bar - you should see entries like `search` and `fetch` listed under `vobiz-docs`.
  </Step>

  <Step title="Try it">
    Ask Claude:

    > Using the vobiz-docs MCP server, how do I start an audio stream from XML?

    Claude will call the `search`/`fetch` tools and answer from the live docs.
  </Step>
</Steps>

### Claude Code

Claude Code (the CLI) speaks Streamable HTTP natively - no `mcp-remote` shim required.

<Steps>
  <Step title="Add the server">
    Run from any project directory:

    ```bash theme={null}
    claude mcp add --transport http vobiz-docs https://docs.vobiz.ai/mcp
    ```

    Use `--scope user` to make the server available across every project, or `--scope project` to commit the config alongside the repo:

    ```bash theme={null}
    claude mcp add --transport http --scope user vobiz-docs https://docs.vobiz.ai/mcp
    ```
  </Step>

  <Step title="Verify it loaded">
    ```bash theme={null}
    claude mcp list
    ```

    `vobiz-docs` should appear with a ✓ next to it. Inside a session, type `/mcp` to see live status and the tools the server exposes.
  </Step>

  <Step title="Use it in a session">
    Anywhere in a Claude Code conversation:

    > Look up the `<Stream>` XML attributes in the Vobiz docs and write me a minimal handler.

    Claude Code will call `vobiz-docs__search` / `vobiz-docs__fetch` automatically.
  </Step>
</Steps>

### Cursor

Cursor reads MCP servers from `~/.cursor/mcp.json` (global) or `.cursor/mcp.json` (per‑project).

<Steps>
  <Step title="Edit the MCP config">
    Open **Cursor → Settings → MCP → Edit Config**, or edit the file directly:

    ```json ~/.cursor/mcp.json theme={null}
    {
      "mcpServers": {
        "vobiz-docs": {
          "command": "npx",
          "args": ["-y", "mcp-remote", "https://docs.vobiz.ai/mcp"]
        }
      }
    }
    ```
  </Step>

  <Step title="Enable & test">
    Back in Settings → MCP, toggle `vobiz-docs` on. The status dot should turn green within a few seconds. Open a new chat and ask a Vobiz‑specific question - Cursor surfaces an "MCP" badge when it pulls from the server.
  </Step>
</Steps>

### VS Code

VS Code 1.99+ has first‑class MCP support behind the **Copilot Chat → Agent** mode.

<Steps>
  <Step title="Create the workspace config">
    Inside your project, create `.vscode/mcp.json`:

    ```json .vscode/mcp.json theme={null}
    {
      "servers": {
        "vobiz-docs": {
          "type": "http",
          "url": "https://docs.vobiz.ai/mcp"
        }
      }
    }
    ```

    Prefer a global setup? Run the **MCP: Add Server** command from the palette (⇧⌘P) and paste the same URL.
  </Step>

  <Step title="Use it in agent mode">
    Open the Copilot Chat panel, switch to **Agent**, and click the 🛠 tools menu - enable `vobiz-docs`. Ask the agent anything about Vobiz and it will fetch from the docs automatically.
  </Step>
</Steps>

### Any other MCP client

The hosted URL works with any client that speaks Streamable HTTP. Two common one‑off invocations:

```bash Run mcp-remote directly theme={null}
npx -y mcp-remote https://docs.vobiz.ai/mcp
```

```bash Probe with the MCP Inspector theme={null}
npx -y @modelcontextprotocol/inspector npx -y mcp-remote https://docs.vobiz.ai/mcp
```

The Inspector launches a small web UI where you can list tools, call `search` with a query, and inspect raw JSON‑RPC traffic - handy when integrating a brand‑new client.

## Verify the connection

A quick sanity check that works in any client:

> Use the Vobiz MCP server to find the page that documents the `playedStream` event, then quote its first paragraph.

If the assistant returns content from [/xml/stream/stream-events](/xml/stream/stream-events), the connection is healthy. If it answers from memory (or gets details wrong), the server isn't actually wired up - re‑check the config file and restart the client.

## Troubleshooting

<Warning>
  Most issues are config‑file syntax or stale processes - not server‑side problems. The endpoint is publicly reachable; if `curl https://docs.vobiz.ai/mcp` returns a response, the server is up.
</Warning>

* **Claude Desktop shows no tools after editing the config.** Fully quit (⌘Q / right‑click → Quit). A window close alone keeps the process alive and the old config cached.
* **`npx: command not found`.** Install [Node.js 18+](https://nodejs.org). On macOS with Homebrew: `brew install node`.
* **`mcp-remote` errors out on first run.** Clear the npx cache: `rm -rf ~/.npm/_npx` and try again. Corporate proxies sometimes block the npm registry - set `HTTPS_PROXY` accordingly.
* **Claude Code says `Server failed to connect`.** Run `claude mcp list` to see the current entry, remove it with `claude mcp remove vobiz-docs`, then re‑add. The `--transport http` flag is required - without it the CLI assumes stdio.
* **VS Code: tools menu is empty.** You're not in Agent mode. Switch the Copilot Chat dropdown from *Ask* to *Agent*; MCP tools only surface there.

## Related

* [Claude Code docs](https://docs.claude.com/en/docs/claude-code) - official setup and `claude mcp` reference.
* [Model Context Protocol spec](https://modelcontextprotocol.io) - protocol details, transports, and SDKs.
* [Vobiz Partner API](/partner/api) - for programmatic access to accounts, CDRs, and KYC, separate from the docs MCP server.