MCP Server (Beta)

The pipe0 MCP server lets you search and enrich data directly from any MCP-compatible client. This includes Claude, ChatGPT, Claude Code, Cursor, and custom agents.

The server exposes pipe0's enrichment and search capabilities as MCP tools.

MCP server URL

https://api.pipe0.com/v1/mcp

Authentication

The MCP server authenticates with OAuth. When you connect, your client opens a browser window where you sign in to pipe0 and approve access. You never enter a client ID or client secret. The server registers clients automatically through dynamic client registration.

API keys do not work for the MCP server. They keep working for the REST API. If your client configuration sends an Authorization header with an API key, remove the header and reconnect with OAuth.

Claude and Cowork

Connectors added on claude.ai are available in the Claude web app, the desktop app, and Cowork.

Open Settings > Connectors and click Add custom connector.

Enter a name, for example pipe0, and set the remote MCP server URL to https://api.pipe0.com/v1/mcp. Leave the OAuth client ID and secret under Advanced settings empty.

Click Add, then Connect. Sign in to pipe0 in the browser window and approve access.

Claude Code

Add the server from your terminal:

Add the pipe0 MCP server

claude mcp add --transport http pipe0 https://api.pipe0.com/v1/mcp

Run /mcp inside Claude Code, select pipe0, and choose Authenticate. Claude Code opens the browser for the OAuth flow and stores the token.

Cursor

Add the server to ~/.cursor/mcp.json, or to .cursor/mcp.json inside a project:

.cursor/mcp.json

{
  "mcpServers": {
    "pipe0": {
      "url": "https://api.pipe0.com/v1/mcp"
    }
  }
}

Open Settings > MCP. Cursor shows a login prompt next to pipe0. Click it to sign in and approve access.

ChatGPT

Open Settings > Plugins, select the MCPs tab, and choose Connect to a custom MCP.

Enter a name, for example pipe0. Set the type to Streamable HTTP and the URL to https://api.pipe0.com/v1/mcp. Leave the bearer token and header fields empty.

Click Save, then sign in to pipe0 in the browser window and approve access.

Other MCP clients

Any client that supports the streamable HTTP transport and OAuth can connect with this configuration:

MCP configuration

{
  "mcpServers": {
    "pipe0": {
      "url": "https://api.pipe0.com/v1/mcp"
    }
  }
}

The client discovers the OAuth endpoints from the server and starts the sign-in flow on first use.

Available tools

The server exposes the full pipe0 surface, grouped by what an agent does with it:

Discover: browse the catalogs and their schemas (list_pipes, list_searches, list_effects, get_pipe_schema, get_search_schema, get_effect_schema, get_guide, get_provider_context, autocomplete_field).
Account resources: list what your organization already has (list_connections, list_secrets, list_sheets, list_buckets, list_schedules).
Validate: dry-run a payload before spending credits (validate_pipes, validate_search, validate_effects).
Run: execute searches, enrichments, and effects, and track them (run_pipes_oneshot, run_search_oneshot, run_effects, check_run_status, wait_for_run, cancel_effect_run, verify_outcome).
Sheets: create and read enrichment sheets (create_sheet, get_sheet_schema, get_sheet_rows, get_field_values, check_pipe_fit, get_recent_effects).
Schedules: automate recurring runs (create_schedule, update_schedule, delete_schedule).

Tools that spend credits or mutate data ask for confirmation on the first call; the agent retries with confirm: true to proceed.

All MCP requests are billed like regular API requests.

Next steps

Pipe catalog

Every pipe_id and its config shape.

Search catalog

Every search_id and its filters.

MCP Server (Beta)

On this page