Skip to main content

specstream-mcp-stdio

A stdio proxy for the SpecStream MCP server at https://api.specstream.ai/mcp. Use it with clients that only start local servers, such as Zed, Cline and Continue. Clients that connect to a remote URL do not need it.

The proxy forwards to the same Streamable HTTP service that remote clients use, so your agent works on your account: the same balance, permissions and spending limits you have.

Install

Python 3.12 or newer. The package has no dependencies.

pip install specstream-mcp-stdio

The command is specstream-mcp-stdio. In a GUI client, use its absolute path if the environment it was installed into is not on PATH.

Create an API key under Agents & API in your SpecStream workspace. Set SPECSTREAM_API_KEY in the private environment of the client, outside prompts and shared configuration. SPECSTREAM_MCP_URL is an optional endpoint override.

Client configuration

For clients that take an mcpServers entry:

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

Zed uses context_servers with the same fields. Continue takes a YAML file:

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 }}

Use the tools

Reconnect your client and list the tools. Start with compile to read a request, or list_specs and list_projects to find saved work.

New paid work goes quote_capacity_work, then authorize_capacity_work with the quote ID and hash, the approved maximum in confirm_max_cents and a stable request key. Reading saved results does not start more paid work. See the agent guide.

Connection problems

The proxy needs the endpoint and a valid key. If it cannot connect, check the client's environment and the key's permissions. Keep TLS verification on.

Protocol messages use stdin and stdout; diagnostics use stderr. The proxy keeps the negotiated HTTP session and does not follow redirects with credentials.

Source and issues: github.com/Specstreamai/specstream-tools. MIT license.

Metadata

Release files for specstream-mcp-stdio 1.2.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for specstream-mcp-stdio 1.2.1
File Size Uploaded Provenance Actions
specstream_mcp_stdio-1.2.1.tar.gz 25.0 kB Without provenance Details for specstream_mcp_stdio-1.2.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for specstream-mcp-stdio 1.2.1
File Interpreter ABI Platform Actions
specstream_mcp_stdio-1.2.1-py3-none-any.whl Python 3 none any Details for specstream_mcp_stdio-1.2.1-py3-none-any.whl

Total release size: 51.8 kB

Release files / specstream_mcp_stdio-1.2.1.tar.gz

Download URL specstream_mcp_stdio-1.2.1.tar.gz
Size 25.0 kB
Tags Source
SHA-256 checksum
How to use checksums
6b9f8bfa52bc4a1a2dbe953674f2115eef34dd366025e5cbe8ad919dc73c2e8a
BLAKE2b-256 checksum
How to use checksums
6ca023598cf56280bfb9c52911b19a7f820d6e3cb3eaf7cb46f9a3bc389ff046
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.15

Release files / specstream_mcp_stdio-1.2.1-py3-none-any.whl

Download URL specstream_mcp_stdio-1.2.1-py3-none-any.whl
Size 26.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a899c09381c975450474c5c510b233dec4876433279ece9ef62031de86aadb14
BLAKE2b-256 checksum
How to use checksums
60e02a6eb321093988e96449e39f635a9f17656a464f8178275207748c0206dc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.15

Security for specstream-mcp-stdio 1.2.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page