PipeCrush APIMCP ServerLive

Connect Claude to PipeCrush.

PipeCrush runs a remote MCP server at api/mcp. Point Claude Code, Cursor, or another MCP client at the endpoint with your API key and Claude can look up records and make updates in your workspace — no server to install or run.

Get your API key Explore the REST API

45 tools, no code to write

Optional read-only keys

Claude

Connected to PipeCrush

Which leads came in this week, and do any of them need a follow-up?

list_leadscreated_after: "monday"

create_tasktitle: "Follow up with Jane"

Twelve leads came in this week. Two have no activity since Tuesday — I've created a follow-up task for Jane at Acme and can draft one for the other if you'd like.

How it works

Three steps, about ten minutes, no code.

Create an API key

In PipeCrush, go to Settings, then API Keys, and click Create key (admin role required). Choose a read-only key if the agent only needs to look things up. Copy the key immediately — it is shown only once.

Point your MCP client at the endpoint

Add https://www.pipecrush.tech/api/mcp to your MCP client with your API key in the Authorization header — one command for Claude Code, one config block for Cursor, VS Code, or Gemini CLI.

Start asking

Restart or reconnect your client and ask about your pipeline. Claude discovers the 45 PipeCrush tools automatically and uses them to look up and update your records.

Connect your MCP client

The server lives at https://www.pipecrush.tech/api/mcp. Every client sends your API key the same way — as a bearer token in the Authorization header.

Claude Code

One command:

claude mcp add --transport http pipecrush https://www.pipecrush.tech/api/mcp \
  --header "Authorization: Bearer pc_live_your_key_here"

Cursor / VS Code

Add a streamable-http server to your MCP config:

{
  "mcpServers": {
    "pipecrush": {
      "url": "https://www.pipecrush.tech/api/mcp",
      "headers": {
        "Authorization": "Bearer pc_live_your_key_here"
      }
    }
  }
}

Gemini CLI

Add an entry to settings.json:

{
  "mcpServers": {
    "pipecrush": {
      "httpUrl": "https://www.pipecrush.tech/api/mcp",
      "headers": {
        "Authorization": "Bearer pc_live_your_key_here"
      }
    }
  }
}

Claude Desktop, the claude.ai web connectors, and ChatGPT connectors don't yet support a custom Authorization header, so they can't connect directly — use Claude Code in the meantime. Broader client support, including a downloadable local server, is coming soon.

The API key travels in every request — protect it like a password. If a key leaks, revoke it in Settings → API Keys and create a new one; traffic on the old key stops immediately.

45 tools, one per operation

Every tool maps to one operation on the PipeCrush REST API: 24 record tools — list, create, fetch, or update across all six record types — plus 21 action tools that send email, enroll a lead in a sequence or campaign, place a call, send a text, and book an appointment. There are no delete tools because the API has no delete endpoints.

The action tools do the thing, not queue it for review — an agent calling send_email sends a real email. Give an agent a read-only key unless you intend that.

Record type	list	create	get	update
contacts	list_contacts	create_contact	get_contact	update_contact
leads	list_leads	create_lead	get_lead	update_lead
customers	list_customers	create_customer	get_customer	update_customer
tasks	list_tasks	create_task	get_task	update_task
tickets	list_tickets	create_ticket	get_ticket	update_ticket
deals	list_deals	create_deal	get_deal	update_deal

Built so you can trust an agent with it

An AI agent with access to your CRM deserves the same scrutiny as a new hire. Here is what the server does — and refuses to do — with that access.

Your key stays in one header

The endpoint reads your API key from the Authorization header on each request, sends it only to PipeCrush over TLS, and scrubs it from every log line and error message.

No delete tools

The API has no delete endpoints and the server exposes no delete tools. The worst a confused agent can do is create or edit a record — never destroy one.

Read-only keys

Create a read-only key in Settings → API Keys and only the 26 lookup tools are exposed. Claude can answer questions about your data without being able to change it.

Isolation enforced server-side

Every request runs through the same tenant isolation as the rest of PipeCrush. A key can only ever see its own organization's data — the agent cannot broaden that.

Bounded by your key's own permissions

Every write the agent makes runs under your API key against your own workspace — so even if it is misled by text inside a record it just read, nothing it does can reach beyond what that key is already allowed to touch. Give agents a read-only key if they only need to look things up.

Frequently asked questions

What is the Model Context Protocol (MCP)?

MCP is an open standard that lets AI assistants like Claude connect to outside tools and data sources. The PipeCrush MCP server speaks that standard, so Claude can read and update your PipeCrush records the same way it would use any other tool.

What do I need to connect Claude to PipeCrush?

Two things: a PipeCrush account with an API key (created by an admin in Settings under API Keys) and an MCP client — Claude Code, Cursor, VS Code, or Gemini CLI. Setup is one command or one config block — no server to install and no code to write.

How do I connect to the PipeCrush MCP server?

Add https://www.pipecrush.tech/api/mcp to your MCP client with your API key in the Authorization header. Claude Code has a one-line command; Cursor, VS Code, and Gemini CLI use a small JSON config block. See the setup steps above for the exact commands.

Can Claude delete my records?

No. The PipeCrush API has no delete endpoints, and the MCP server exposes no delete tools. Claude can list, look up, create, and update records — nothing it does through the server can destroy data.

What is a read-only key?

When you create an API key in Settings → API Keys, you can leave write access off. A read-only key only unlocks the 26 lookup tools — Claude can answer questions about your pipeline but cannot create or change anything. Use it for reporting, research, and any agent that only needs lookups.

What data can Claude see?

Exactly what the API key can see: the key acts with the data visibility of the user who created it, and all access stays inside your organization. Record contents are passed to Claude as data for the conversation you're having — nothing is stored by the server itself.

Do MCP tool calls count against my rate limit?

Yes. MCP tool calls share the same limit as the REST API — 120 requests per minute per key — and each tool call counts as 2 requests. A burst of lookups can hit the limit faster than the same work over the REST API directly.

Can I use this with Claude Desktop or the claude.ai web connectors?

Not yet — Claude Desktop, claude.ai web connectors, and ChatGPT connectors don't support the custom Authorization header the endpoint needs today. Use Claude Code in the meantime; broader support is coming with OAuth.

Put Claude to work in your pipeline

Create a free PipeCrush account, generate an API key, and point Claude Code or another MCP client at the endpoint above.