SearchPipe is a remote MCP Server (streamable-http transport): paste the MCP link into your client and your agent gains real-time web retrieval, full-text extraction and cited answers — nothing to deploy locally.
MCP (Model Context Protocol) is an open protocol for connecting AI clients to external tools and data sources. The traditional approach runs the search server locally (a stdio MCP server) — you install dependencies, upgrade versions and manage processes yourself. A remote MCP Server moves all of that to our side; the client only needs a URL:
Register a SearchPipe account and verify your email — a default API key is generated automatically. Find it under "API Keys" in the console (masked by default; click "Show" to reveal the plaintext, as often as you like). You can create additional keys anytime.
sp-YOUR_API_KEYAppend the key to /mcp/ to form the full URL — this is what the client asks for:
https://searchpipe.tech/mcp/?api_key=sp-YOUR_API_KEYFollow the per-client examples below (Claude Code uses the CLI; Cursor / Cline / VS Code use a JSON config).
In a conversation, ask it to "use searchpipe_search to look up today's news" — results with links and snippets confirm the setup worked.
One command (--transport http selects the remote HTTP transport):
claude mcp add --transport http searchpipe \
"https://searchpipe.tech/mcp/?api_key=sp-YOUR_API_KEY"
# List configured servers
claude mcp listAdd an mcpServers entry to your client's MCP config (Cursor: ~/.cursor/mcp.json; VS Code: .vscode/mcp.json or the user-level config):
{
"mcpServers": {
"searchpipe": {
"url": "https://searchpipe.tech/mcp/?api_key=sp-YOUR_API_KEY"
}
}
}Some clients require an explicit remote HTTP declaration:
{
"mcpServers": {
"searchpipe": {
"type": "http",
"url": "https://searchpipe.tech/mcp/",
"headers": { "Authorization": "Bearer sp-YOUR_API_KEY" }
}
}
}If your client supports custom headers, prefer the Authorization: Bearer style — the key never appears in URLs or logs.
The MCP server exposes a single tool, searchpipe_search, with parameters identical to the REST API's POST /search:
| Parameter | Type | Default | Description |
|---|---|---|---|
query required | string | — | Search question or keywords |
max_results | int | 5 | Number of results (1–20) |
include_answer | bool | false | Generate a cited answer |
include_raw_content | bool | false | Return the full extracted page body |
search_depth | string | basic | basic / advanced; affects credit cost |
For the field-level response shape, see API docs · Response shape.
This is normal streamable-http validation: the request must accept both JSON and SSE. When testing with curl, add -H "Accept: application/json, text/event-stream"; a browser opening /mcp directly and getting 406 is also expected — not a service outage.
The canonical endpoint is /mcp/ (trailing slash). Clients follow redirects automatically; with curl, add -L or request /mcp/ directly.
Check three things: the key starts with sp-; it hasn't been revoked in the console; and the trailing sp-… wasn't truncated when copying the link. If a key leaks, revoke and recreate it in the console immediately.
A cold query runs the full "multi-engine retrieval → extraction → LLM reranking" chain and typically takes a few seconds; identical query and parameters within the cache TTL (default 300s) return in milliseconds.
Free credits on signup — copy the MCP link and go. Nothing to install locally.
Get an API Key