SpecStream

The live web data engine for teams and agents.

Website · Docs · Pricing · MCP Registry

One platform to build, search, extract, enrich, map, and monitor data across the entire web.

Ask for any dataset in plain words, and SpecStream builds it from the entire live web: every match found, extracted and enriched into structured records, then monitored for change. It runs through the API and MCP, and inside Sheets, CRMs, Slack, n8n, Zapier and the other tools teams already use.

Search:

curl -G https://api.specstream.ai/v1/web-search \

-H "Authorization: Bearer $SPECSTREAM_API_KEY" \ --data-urlencode "q=What is the population of Japan?"

Extract:

curl https://api.specstream.ai/v1/extract \

-H "Authorization: Bearer $SPECSTREAM_API_KEY" \ -H "Content-Type: application/json" \ -d '{"urls": ["https://example.com"]}'

• Source URL and read time on every value.
• The Search API and Extract API need no quote and no approval. Each search or page takes its flat price from your balance.
• In Deep Search, the most a run can cost is shown and approved before it runs. Only delivered rows are billed, and a run that finds nothing costs nothing.
• A saved request reruns hourly to yearly, and each row is labeled changed, unchanged or no longer matching.
• Your agent works on your account, inside the spending limits you set.

This repository holds what you install around SpecStream: MCP client setup, agent plugins and skills, SDKs, the n8n node, a GitHub Action, and examples. The product itself runs at specstream.ai. Licensed MIT.

Connect an agent

The MCP server is https://api.specstream.ai/mcp (Streamable HTTP). Your agent works on your account: the same balance, permissions and spending limits you have.

1. Open Agents & API in the workspace and create an API key. Give it only what the task needs: read, prepare, or execute, the projects it may use, an expiry, and a spending limit.
2. Put it in an environment variable, so no file holds it:

   export SPECSTREAM_API_KEY="ss_live_..."

1. Add the server to your client, below.

Clients that support MCP sign-in can connect without a key. Each guide at specstream.ai/docs/mcp shows the current steps.

New accounts start with $10 of credit for 30 days, no card.

Claude

In Claude, go to Customize > Connectors, choose Add custom connector, name it SpecStream and paste https://api.specstream.ai/mcp. Steps for both sign-in and a key: docs/mcp/claude.

Claude Code

claude mcp add --transport http specstream https://api.specstream.ai/mcp \

--header "Authorization: Bearer $SPECSTREAM_API_KEY"

Or install the plugin, which adds the server and the six skills. It signs you in through your browser the first time, so no key is needed:

/plugin marketplace add specstream/specstream-tools

/plugin install specstream@specstream

ChatGPT

Go to ChatGPT Plugins, choose the plus button, then Add custom MCP server. Paste https://api.specstream.ai/mcp under Connection and set Authentication to OAuth. Steps: docs/mcp/chatgpt.

Codex

Add to ~/.codex/config.toml:

[mcp_servers.specstream]

url = "https://api.specstream.ai/mcp" bearer_token_env_var = "SPECSTREAM_API_KEY"

Cursor

Add to ~/.cursor/mcp.json, or .cursor/mcp.json in one project:

{

"mcpServers": { "specstream": { "url": "https://api.specstream.ai/mcp", "headers": { "Authorization": "Bearer ${env:SPECSTREAM_API_KEY}" } } } }

VS Code

Add to .vscode/mcp.json. VS Code asks for the key once and keeps it out of the file.

{

"inputs": [ { "type": "promptString", "id": "specstream-key", "description": "SpecStream API key", "password": true } ], "servers": { "specstream": { "type": "http", "url": "https://api.specstream.ai/mcp", "headers": { "Authorization": "Bearer ${input:specstream-key}" } } } }

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

{

"mcpServers": { "specstream": { "serverUrl": "https://api.specstream.ai/mcp", "headers": { "Authorization": "Bearer ${env:SPECSTREAM_API_KEY}" } } } }

Zed, Cline, and Continue

Cline also connects to the hosted server directly with OAuth sign-in: cline mcp install specstream --transport http https://api.specstream.ai/mcp. Zed and Continue, and Cline if you prefer a key, use the stdio proxy. It forwards your key from the environment and nothing else.

pip install specstream-mcp-stdio

Zed, in settings.json:

{

"context_servers": { "specstream": { "command": "specstream-mcp-stdio", "args": [], "env": { "SPECSTREAM_MCP_URL": "https://api.specstream.ai/mcp" } } } }

Cline, in cline_mcp_settings.json:

{

"mcpServers": { "specstream": { "command": "specstream-mcp-stdio", "args": [], "env": { "SPECSTREAM_MCP_URL": "https://api.specstream.ai/mcp" } } } }

Continue, in .continue/mcpServers/specstream.yaml:

name: SpecStream

version: 1.0.0 schema: v1 mcpServers:

• name: specstream type: stdio command: specstream-mcp-stdio args: [] env: SPECSTREAM_MCP_URL: https://api.specstream.ai/mcp SPECSTREAM_API_KEY: ${{ secrets.SPECSTREAM_API_KEY }}

Start Zed and Cline from a shell where SPECSTREAM_API_KEY is set. Agents installing SpecStream for someone can follow llms-install.md.

Gemini CLI

Install the extension (the MCP server plus instructions to show the price and wait for a yes):

gemini extensions install https://github.com/specstream/specstream-tools

Or add only the server:

gemini mcp add --transport http specstream https://api.specstream.ai/mcp \

--header "Authorization: Bearer $SPECSTREAM_API_KEY"

Or in ~/.gemini/settings.json:

`jso