# Connect your client - Veezee docs

One MCP server, many hosts. Endpoint: `https://mcp.veezee.io/all` (streamable-http, all three platforms on one connection; per-platform mounts `/linkedin`, `/reddit`, `/x`). Clients that support the MCP authorization spec (Claude Code, claude.ai, ChatGPT developer-mode connectors) open a Veezee sign-in in your browser on connect: email code, no password, no card, zero keys to copy. Other clients: mint a free key with `POST https://api.veezee.io/v1/keys/mint` and every host below connects under a shared per-IP daily budget; buy a key at https://veezee.io/upgrade for more. Snippets verified against each client's official docs on 2026-07-11; "tested" marks what was actually exercised against production.

## Claude Code

```
claude mcp add --transport http veezee "https://mcp.veezee.io/all?src=docs-clients"
```

Terminal; persists to ~/.claude.json (or project .mcp.json with --scope). Opens a Veezee sign-in in your browser (email code, no password, no card); approving it connects the account, zero keys involved. Headless or CI: mint a free key over REST instead and put it in the client's connection headers.. Status: tested end to end (real binary, 2026-07-11: linkedin_get_company at 4 credits, zero errors). Official docs: https://code.claude.com/docs/en/mcp

## claude.ai (web)

```
Settings > Connectors > Add custom connector > https://mcp.veezee.io/all?src=docs-clients
```

claude.ai settings UI, no config file. Team/Enterprise: Organization settings > Connectors. Enable per-chat from the + menu. Leave the optional client id/secret fields blank. Connecting opens a Veezee sign-in (email code, no password, no card); approving it connects the account, zero keys involved.. Status: config path verified against official docs; not app-tested. Official docs: https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp

## ChatGPT

```
Settings > Security and login > Developer mode (on)
chatgpt.com/plugins > + > MCP server URL: https://mcp.veezee.io/all?src=docs-clients
```

ChatGPT settings UI, no config file; workspace plans may need admin approval for Developer mode. Adding the connector opens a Veezee sign-in (email code, no password, no card); approving it connects the account, zero keys involved.. Status: UI path verified against official docs 2026-07-19; not app-tested. Official docs: https://developers.openai.com/apps-sdk/deploy/connect-chatgpt

## Cursor

```
{
  "mcpServers": {
    "veezee": { "url": "https://mcp.veezee.io/all?src=docs-clients" }
  }
}
```

.cursor/mcp.json (project) or ~/.cursor/mcp.json (global). Status: config verified against official docs; desktop flow pending a human run (BLOCKERS.md). Official docs: https://cursor.com/docs/context/mcp

## Windsurf

```
{
  "mcpServers": {
    "veezee": { "serverUrl": "https://mcp.veezee.io/all?src=docs-clients" }
  }
}
```

~/.codeium/windsurf/mcp_config.json (note the serverUrl key, not url). Status: config verified against official docs; not app-tested. Official docs: https://docs.devin.ai/desktop/cascade/mcp

## VS Code (Copilot agent mode)

```
{
  "servers": {
    "veezee": { "type": "http", "url": "https://mcp.veezee.io/all?src=docs-clients" }
  }
}
```

.vscode/mcp.json (top-level key is "servers", and "type": "http" is required). Status: config verified against official docs; not app-tested. Official docs: https://code.visualstudio.com/docs/copilot/chat/mcp-servers

## Codex CLI

```
codex mcp add veezee --url "https://mcp.veezee.io/all?src=docs-clients"
codex mcp login veezee
codex mcp list   # verify: veezee listed with its tools

# or in ~/.codex/config.toml:
[mcp_servers.veezee]
url = "https://mcp.veezee.io/all?src=docs-clients"
```

~/.codex/config.toml. Known issue: some Codex builds complete the OAuth sign-in but never attach the server's tools (openai/codex issue 20009). If login succeeds and the Veezee tools still never appear, update Codex, or skip OAuth: mint a free key and set it via bearer_token_env_var (key path on /docs/cli). Status: tested end to end (real binary, headless codex exec, 2026-07-11: linkedin_get_company, error-recovery flow); commands re-verified against official docs 2026-07-19. Official docs: https://learn.chatgpt.com/docs/extend/mcp?surface=cli

## Cline

```
{
  "mcpServers": {
    "veezee": { "type": "streamableHttp", "url": "https://mcp.veezee.io/all?src=docs-clients" }
  }
}
```

Cline panel > MCP Servers > Remote Servers, or cline_mcp_settings.json. Set "type": "streamableHttp" explicitly.. Status: config verified against official docs; not app-tested. Official docs: https://docs.cline.bot/mcp/configuring-mcp-servers

## Zed

```
{
  "context_servers": {
    "veezee": { "url": "https://mcp.veezee.io/all?src=docs-clients" }
  }
}
```

Zed settings.json under "context_servers", or Settings > AI > MCP Servers > Add Remote Server. Status: config verified against official docs; not app-tested. Official docs: https://zed.dev/docs/ai/mcp

## Plain REST (curl)

```
curl -s -X POST https://api.veezee.io/v1/keys/mint | jq -r .key > ~/.veezee/key

curl "https://api.veezee.io/v1/linkedin/companies?identifier=microsoft" \
  -H "Authorization: Bearer $(cat ~/.veezee/key)"

# hit the daily cap? buy a key at https://veezee.io/upgrade, then:
curl "https://api.veezee.io/v1/linkedin/companies?identifier=microsoft" \
  -H "Authorization: Bearer $VEEZEE_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)"
```

Any HTTP client. Contract: https://veezee.io/openapi.json. Metered calls need an Idempotency-Key header, even on GET (free-tier calls do not).. Status: tested end to end (the e2e suite runs this against production on every deploy). Official docs: https://veezee.io/openapi.json

## SDK

`npm install @veezee/sdk` (Node 20+): typed client for every tool, retries and Idempotency-Keys built in. `npm install -g @veezee/sdk` also gives the `veezee` CLI. Docs: https://veezee.io/docs/sdk and https://veezee.io/docs/cli.

All three servers are listed in the official MCP Registry: MCP Registry: io.veezee servers (https://registry.modelcontextprotocol.io/v0/servers?search=io.veezee).