# SpecStream [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/Specstreamai/specstream-tools  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/specstream

## Description
Give your agent finished lists from the live web: every row with its source, priced per match.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "specstream": {
    "command": "uvx",
    "args": ["specstream-mcp-stdio"],
    "env": {
      "SPECSTREAM_API_KEY": ""
    }
  }
}
```

**Requires environment variables:** `SPECSTREAM_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What SpecStream MCP server does

The SpecStream MCP server gives an agent access to SpecStream’s hosted live-web data service. An agent can describe the list it needs in ordinary language, such as organizations matching a condition and an additional field to collect. The returned rows include the web page each result came from, so the output can be traced back to its source.

SpecStream is intended for requests where the result set needs to be assembled from current web pages rather than from a fixed local dataset. The service shows a quote before work begins and charges for matches; a request that finds no matches costs nothing according to the project documentation. Accounts, permissions, and spending limits apply to the connected workspace.

## How it works

The hosted MCP endpoint is `https://api.specstream.ai/mcp` and uses Streamable HTTP. Connect an MCP-compatible client directly to that URL, then authenticate with an API key or a client-supported MCP sign-in flow. The repository describes the endpoint as exposing 97 tools.

An API key can be restricted by access level, projects, expiration, and spending limit when it is created in the SpecStream workspace. The agent operates against the account associated with that authentication. A typical interaction consists of describing a list, reviewing the price, approving the permitted maximum, and receiving the resulting rows with source pages.

The SpecStream MCP server is hosted; this repository contains the surrounding installation options rather than the core web service. Those options include a Python client and command, a TypeScript SDK, agent skills, a Claude Code plugin, a Cursor plugin, an n8n node, a VS Code extension, a GitHub Action, and examples for selected agent frameworks.

## Setup and configuration

Create an API key in the workspace’s Agents & API area and expose it as `SPECSTREAM_API_KEY` rather than placing it in a configuration file. Direct HTTP clients can send it as a Bearer token. Clients that support MCP sign-in may connect without manually supplying a key.

Clients with documented configurations include Claude, Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf, Gemini CLI, and others listed in the repository. Zed, Cline, and Continue use the `specstream-mcp-stdio` package because their documented setup starts a local process. That proxy forwards the request to the hosted endpoint and uses `SPECSTREAM_MCP_URL` for the remote URL.

New accounts receive $10 of work free for 30 days with no card, as stated in the README. Usage remains subject to the account’s permissions and spending settings.

## Tools and capabilities

The documented MCP connection supports:

- Plain-language requests for complete lists from live web sources
- Row-level source pages for tracing returned data
- Pre-run pricing and approval of a maximum spend
- Account-based permissions and spending limits
- Delivery of results to connected agent clients
- Agent workflows named `compile`, `review-work`, `approve-work`, and `continue-work`

The repository also includes an n8n community node that reads a request, displays its quote, accepts an approval limit, and returns results. A GitHub Action can run a request and upload a CSV. These are separate integration paths around the same SpecStream service rather than additional MCP endpoint deployments.

## Limitations and notes

The product itself runs at SpecStream’s hosted service; installing this repository does not create a standalone local data engine. The README does not provide a fixed domain list, a guaranteed schema for every request, or a complete description of all 97 tool names, so suitability depends on whether the requested web list can be found and matched by the service.

Keep API keys out of checked-in client files. For clients that require local startup, ensure the environment variable is available to the process that launches the stdio proxy. Pricing applies before execution, but the actual account balance, permissions, project access, and configured spending limit determine whether a request can proceed. The repository is licensed under MIT.

_Full upstream README: https://allmcps.com/mcp/specstream/readme_