SearchPipe is a remote MCP Server (streamable-http): one URL gives any AI coding agent real-time web search, full-text page extraction and cited answers. Below are copy-paste configuration snippets for Claude Code, Cursor, OpenAI Codex, OpenCode and Pi.
Sign up and verify your email — a default API key (prefix sp-) is generated automatically. Reveal it any time under "API Keys".
Append your key to /mcp/ — this single URL is all every client below asks for:
https://searchpipe.tech/mcp/?api_key=sp-YOUR_API_KEYTip: the API Keys page has a "one-line setup" copy button — paste that sentence into any agent and it configures itself.
Jump straight to your agent: Claude Code · Cursor · Codex · OpenCode · Pi.
Ask your agent to "use the searchpipe tool to look up the latest FastAPI release notes". A successful searchpipe_search call with source links confirms the setup. Note: a successful MCP handshake alone proves nothing — the handshake is unauthenticated; only a real tool call validates the key.
Fastest path — one CLI command (--transport http selects the remote HTTP transport):
claude mcp add --transport http searchpipe \
"https://searchpipe.tech/mcp/?api_key=sp-YOUR_API_KEY"
# Confirm it is registered
claude mcp listOr declare it in project scope via .mcp.json (share with your team via git):
{
"mcpServers": {
"searchpipe": {
"type": "http",
"url": "https://searchpipe.tech/mcp/?api_key=sp-YOUR_API_KEY"
}
}
}Open Cursor Settings → MCP → "Add MCP server", or edit ~/.cursor/mcp.json (global) / .cursor/mcp.json (project) directly:
{
"mcpServers": {
"searchpipe": {
"url": "https://searchpipe.tech/mcp/?api_key=sp-YOUR_API_KEY"
}
}
}Save and toggle the server on in the MCP panel. The same snippet works in Cline, Windsurf and VS Code (.vscode/mcp.json) — they all read a standard mcpServers map.
Codex reads MCP servers from ~/.codex/config.toml. Add a streamable-HTTP server entry with the url field:
[mcp_servers.searchpipe]
url = "https://searchpipe.tech/mcp/?api_key=sp-YOUR_API_KEY"
enabled = trueIf you prefer not to put the key in the URL, keep it in an environment variable and let Codex send it as a bearer token:
[mcp_servers.searchpipe]
url = "https://searchpipe.tech/mcp/"
bearer_token_env_var = "SEARCHPIPE_API_KEY"
enabled = true
# In your shell: export SEARCHPIPE_API_KEY=sp-YOUR_API_KEYRun codex mcp list to confirm the server is loaded, then start a session and trigger a search.
Add a remote MCP entry to opencode.json (project root) — "remote" is the type for streamable-HTTP servers:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"searchpipe": {
"type": "remote",
"url": "https://searchpipe.tech/mcp/?api_key=sp-YOUR_API_KEY",
"enabled": true
}
}
}To keep the key out of the config file, use headers instead:
{
"mcp": {
"searchpipe": {
"type": "remote",
"url": "https://searchpipe.tech/mcp/",
"headers": {
"Authorization": "Bearer sp-YOUR_API_KEY"
},
"enabled": true
}
}
}Restart OpenCode so it reloads the config, then check the tools list for searchpipe_search.
Pi keeps its core minimal and does not ship an MCP client — MCP support comes from the community extension pi-mcp-adapter. Install it once:
pi install npm:pi-mcp-adapterThen register SearchPipe in ~/.pi/agent/mcp.json (global) or .pi/mcp.json (project):
{
"mcpServers": {
"searchpipe": {
"url": "https://searchpipe.tech/mcp/?api_key=sp-YOUR_API_KEY"
}
}
}The adapter also supports "imports" — if SearchPipe is already configured in Cursor or Claude Code, you can inherit it instead:
{
"imports": ["cursor", "claude-code"]
}Restart Pi after editing; tools appear with an adapter prefix.
Every client above ends up with the same single tool. Key parameters:
| Parameter | Default | Description |
|---|---|---|
query required | — | What to search for |
max_results | 5 | 1–20 results |
include_answer | false | Also generate a cited AI answer |
include_raw_content | false | Return full extracted page text |
search_depth | basic | basic = 1 credit, advanced = 2 credits |
Failed or moderated calls are automatically refunded. Full field-level response shape: API docs.
The key did not reach the server: the URL lost its ?api_key= part (often a redirect dropping the query string when the trailing slash is missing). Always copy the exact MCP link from the dashboard — it ends in /mcp/?api_key=… — or switch to header-based auth, which survives redirects.
The key was revoked, or the trailing sp-… got truncated when copying. Re-copy from API Keys.
Normal for streamable-http: add -H "Accept: application/json, text/event-stream" and request /mcp/ (with the trailing slash).
The adapter must be installed before the config takes effect: run pi install npm:pi-mcp-adapter, restart Pi, and check the tools list again.
POST /search reference and error codesFree credits on signup — paste one URL into Claude Code, Cursor, Codex, OpenCode or Pi and start searching.
Get an API Key