MCP-first. Zero-token CLI. REST when you need it.
Pipeline ships a hosted MCP server for AI clients, a deterministic CLI for scripts and CI, and a small REST surface for prospect + campaign ingestion. Same API key across all three, 84 tools available to MCP and CLI.
Pick the surface that fits your stack.
Same API key, same data. The MCP server and the CLI expose the same 84-tool surface; the REST endpoints cover the most common ingestion paths.
Drive every Pipeline agent from Claude Code, Cursor, Codex, or any MCP client. JSON-RPC 2.0 over HTTPS. 84 tools, same auth as everything else.
pipeline-gtm mirrors the MCP surface but ships as a deterministic CLI: cron-safe, pipe-friendly, exit-code-correct. No model round-trip required.
A small, focused REST surface for prospect + campaign ingestion. Bearer auth with the same key as MCP and the CLI. Use it from anything that can curl.
The 5 REST endpoints rendered as an interactive Scalar reference: request + response schemas, curl/JS/Python samples, live try-it. Spec at/openapi.json.
87 tools across 21 categories. One call pattern up top, then a clean per-tool reference: name, description, parameter table, JSON schema. Built for agents to read, humans to grep.
Hosted MCP server. 84 tools.
The recommended way to drive Pipeline from an AI client. Use the hosted endpoint over HTTPS, or run the pipeline-mcp npm package locally as a STDIO proxy.
// claude code · ~/.claude/mcp.json{"mcpServers": {"pipeline": {"url": "https://www.pipeline.help/api/mcp-server","headers": {"Authorization": "Bearer <key>"}}}}// or one-shot$ claude mcp add pipeline \https://www.pipeline.help/api/mcp-server
# local STDIO if your client requires it# (e.g. Claude Desktop without HTTP support)$ npx pipeline-mcp# claude desktop · claude_desktop_config.json{"mcpServers": {"pipeline": {"command": "npx","args": ["pipeline-mcp"],"env": {"PIPELINE_API_KEY": "<key>"}}}}
Zero-token CLI. Mirrors the MCP surface.
Deterministic, cron-safe, pipe-friendly. No model round-trip — same tools, but you call them directly. Use it from CI, shell scripts, or a local cron.
# auth once with the same key as MCP$ export PIPELINE_API_KEY=sk_...# discover commands (mirrors MCP tool names)$ npx pipeline-gtm --help# run a tool directly$ npx pipeline-gtm list-agents$ npx pipeline-gtm scout-run --brief ./brief.md$ npx pipeline-gtm icp-score --threshold 70# pipe-friendly · JSON out · exit code on failure$ npx pipeline-gtm export-table tbl_a1 \--filter "icp>70" --json \| jq -r '.rows[].linkedin_url'# cron-safe — exit 0 on success, non-zero otherwise$ npx pipeline-gtm researcher-enrich \--campaign cam_8x4f --quiet
REST endpoints for ingestion.
A small, focused REST surface. Use the MCP server or CLI for the full 84-tool surface; use REST when you want to wire Pipeline into a script that can curl.
# Bearer auth · same key as MCP / CLI# Generate one from workspace → settings → API keys# POST /api/v1/prospects — bulk-add prospects to a campaign$ curl https://www.pipeline.help/api/v1/prospects \-H "Authorization: Bearer $PIPELINE_KEY" \-H "Content-Type: application/json" \-d '{"campaign_id": "cam_8x4f","prospects": [{"linkedin_url": "linkedin.com/in/jane","first_name": "Jane","company_name": "Helix"}]}'# GET /api/campaigns — list + create campaigns# GET /api/auth/validate — verify the key is live
// note: The REST surface is intentionally narrow. For full coverage (research, scoring, drafting, sending), use the MCP server or pipeline-gtm CLI — they expose the same 84 tools.
What teams build.
Connect the hosted MCP server in your AI coding tool. Run campaigns, inspect rows, and iterate on prompts from your agent loop.
claude mcp add pipeline https://www.pipeline.help/api/mcp-serverWrap pipeline-gtm in a GitHub Action. Kick off a research run, push enriched rows into a campaign, fail the build on a contract violation. Deterministic exit codes, no model in the loop.
$ npx pipeline-gtm scout-run --brief ./brief.mdPOST a payload of LinkedIn URLs (or full prospect rows) into an existing campaign. Same Bearer token, rate-limited per workspace.
POST /api/v1/prospects · Authorization: Bearer …