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/specstream/specstream-tools. MIT license.

Metadata

Release files for specstream-mcp-stdio 1.2.3

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.3
File Size Uploaded Provenance Actions
specstream_mcp_stdio-1.2.3.tar.gz 25.3 kB With provenance Details for specstream_mcp_stdio-1.2.3.tar.gz

Built distribution (wheel)

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

Total release size: 52.6 kB

Release files / specstream_mcp_stdio-1.2.3.tar.gz

Download URL specstream_mcp_stdio-1.2.3.tar.gz
Size 25.3 kB
Tags Source
SHA-256 checksum
How to use checksums
1a04ccf35e50307166cee3409f8944f2e09f37d8c8b03603dad701f90583cd15
BLAKE2b-256 checksum
How to use checksums
9622ec75b52919f46475921f9861f92f881c449279c5a7d0423f616be5a6030c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.

Transparency log

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

Download URL specstream_mcp_stdio-1.2.3-py3-none-any.whl
Size 27.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
cccc8a399bdfb68c007f6036d39fbc9cd902bbb11725143f1c51966367dd2823
BLAKE2b-256 checksum
How to use checksums
aaf89ebc5fb57da55faabf64d46f828629b987ea6a72bc351e362dbae5259b42
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.

Transparency log

Security for specstream-mcp-stdio 1.2.3

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.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for specstream_mcp_stdio-1.2.3.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.

Transparency log

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