Model Context Protocol

Connect your AI agent to Chuhching

Chuhching speaks MCP — the open standard for giving AI agents real tools. Generate a token and Claude, Cursor, VS Code, Cline, or Windsurf can search podcasts, send pitches, reply to your inbox, and run your pipeline, right inside the model's tool surface.

Get started free Generate a token

Server URL: https://pitchiq-mcp-production.up.railway.app/mcp

What your agent can do

Discover

Search podcasts, creators, and curators, and surface live opportunities that match your profile.

Pitch

Draft personalized, on-brand pitches and send them — then keep follow-up sequences moving.

Inbox

Read, triage, and reply to conversations without leaving your agent's chat window.

Pipeline

Create deals, move stages, and keep your CRM current as each conversation progresses.

Schedule

Book meetings and manage availability the moment a lead says yes.

Analytics & tasks

Pull performance summaries, list and create tasks, and check your wiki — all by asking.

Three steps to connect

Generate a token

In Chuhching, open Settings → Integrations → MCP and create a scoped access token. Read is always on; add write scopes (outreach, inbox, pipeline, scheduling) as needed.

Add the server to your client

Pick your client below, paste the config, and drop in the token. The server URL is the same everywhere.

Start driving Chuhching

Restart your client and the Chuhching tools appear in your agent's tool list. Ask it to find shows, draft a pitch, or move a deal.

Set up your client

Copy the config for your tool. Generate a token first (it's free) — then paste it where you see the placeholder.

Connect your client

Server URL: https://pitchiq-mcp-production.up.railway.app/mcp

Each snippet has a <YOUR_TOKEN> placeholder — swap in a token from Settings → Integrations → MCP.

The desktop app launches MCP servers locally, so it reaches our hosted endpoint through the open-source mcp-remote bridge (npx fetches it on first run — no install). Newer builds with native HTTP transport can use the simpler second form.

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

Open Claude → Settings → Developer → Edit Config (or open the file above).
Paste the snippet and replace <YOUR_TOKEN> with your token.
Fully quit and reopen Claude Desktop. PitchIQ's tools appear in the tool list within seconds.

mcp-remote bridge — works on every version (recommended)

{
  "mcpServers": {
    "pitchiq": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://pitchiq-mcp-production.up.railway.app/mcp",
        "--header",
        "Authorization: Bearer <YOUR_TOKEN>"
      ]
    }
  }
}

Native HTTP — only if your build supports HTTP transports

{
  "mcpServers": {
    "pitchiq": {
      "type": "http",
      "url": "https://pitchiq-mcp-production.up.railway.app/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

The bridge form needs Node.js installed (for npx). If tools don't appear, confirm Node is on your PATH and that you fully restarted the app.

Claude Desktop MCP docs ↗

About your token

Tokens are scoped — grant only the access an agent needs (read-only, or specific write scopes like outreach or pipeline). We store only a hash, never the plaintext, so we can't show a token twice; if a machine is compromised, revoke it and generate a new one. Treat tokens like passwords — never commit one to a public repo.

Give your agent a CRM

Start free, generate a token, and let your AI agent get you booked — discovery, pitches, and pipeline without leaving the chat.

Get started free