Other MCP clients

Any client that speaks remote MCP can connect to https://vocalvideo.com/api/mcp. The only question is how it authenticates.

Clients that sign in from a URL

If the client supports OAuth for remote servers, the URL is all it needs — it opens a Vocal Video sign-in and you click Allow, exactly as with Claude.

Claude Code

claude mcp add --transport http vocal-video https://vocalvideo.com/api/mcp

Then run /mcp inside a session and pick Vocal Video to sign in.

Cursor — add to .cursor/mcp.json (or the global ~/.cursor/mcp.json) and approve the sign-in when Cursor prompts:

{
  "mcpServers": {
    "vocal-video": { "url": "https://vocalvideo.com/api/mcp" }
  }
}

Claude Desktop uses the connector on your Claude account — there's no config file to edit. Follow Connect Claude.

Clients that take a bearer header

If the client has nowhere to sign in but lets you set headers, use a workspace API key from Settings → API keys:

{
  "mcpServers": {
    "vocal-video": {
      "url": "https://vocalvideo.com/api/mcp",
      "headers": { "Authorization": "Bearer <your-api-key>" }
    }
  }
}

A key is either read or write; pick read unless the client needs to change things. Keys are shown once and act as the person who created them.

Clients that only run local (stdio) servers

Bridge to the HTTP endpoint with mcp-remote, which handles the sign-in for you:

{
  "mcpServers": {
    "vocal-video": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://vocalvideo.com/api/mcp"]
    }
  }
}

Choosing toolsets

Every variant accepts the same ?toolsets= query on the URL — see What Claude can reach. For an IDE agent, ?toolsets=all is usually the right call: it has context to spare and you'll want every tool available.

Protocol details — versions, methods, error channels — live in the MCP reference.