Skip to the page
Get started free

ForgeCode

Add SpecStream to ForgeCode with one entry in .mcp.json, and the terminal coding agent can search the live web, read pages and ask for structured data in the middle of a task. Sign in once in the browser, or send an API key from your environment.

SpecStream for ForgeCodeCoding agents

What you need

  • ForgeCode installed (curl -fsSL https://forgecode.dev/cli | sh), with a model provider set up.
  • A SpecStream account. New accounts start with $10 of credit, no card. Create one.

  1. 1. Add SpecStream to .mcp.json

    ForgeCode reads MCP servers from .mcp.json in your project, and from .mcp.json in its own config folder for every project. An entry with a url is a remote server, and ForgeCode connects to it over Streamable HTTP, the transport SpecStream speaks. Create .mcp.json at the root of your project:

    .mcp.json
    {
      "mcpServers": {
        "specstream": {
          "url": "https://api.specstream.ai/mcp"
        }
      }
    }

  2. 2. Or add it from the command line

    forge mcp import writes the same entry for you. With --scope user it goes to ForgeCode's config folder, so every project gets SpecStream. Without it, it goes to the project's .mcp.json.

    Terminal
    forge mcp import --scope user '{"mcpServers":{"specstream":{"url":"https://api.specstream.ai/mcp"}}}'

  3. 3. Sign in to SpecStream

    SpecStream asks for sign-in, so ForgeCode needs a token before it can list the tools. Run the login command with the server's name. A browser window opens on SpecStream's sign-in: approve the access ForgeCode asks for. ForgeCode stores the token, refreshes it when it expires and reloads its servers.

    Before this step, ForgeCode reports that the server requires authentication and names the same command.

    Terminal
    forge mcp login specstream

  4. 4. Accept the project file and ask

    The first time ForgeCode starts in a project with a new or changed .mcp.json, it says Untrusted MCP config was found at with the file's path and offers Accept or Reject. Choose Accept. An entry in the user file is not asked about.

    Then ask in a ForgeCode session, for example:

    In ForgeCode
    Find the latest stable release of PostgreSQL, read its release notes, and list the changes that affect logical replication.

Use an API key instead of signing in

On a server or in CI, where no browser opens, send a SpecStream API key. Create one in Agents & API: choose API keys, then Create API key, and give it a spending limit above 0.

Export it as SPECSTREAM_API_KEY in the shell that starts ForgeCode. ForgeCode fills {{env.NAME}} in a header from its environment, so the key stays out of the file. "oauth": false tells ForgeCode to send the header and skip sign-in.

Where the files are

The project file is .mcp.json in the folder you start ForgeCode from. When both files name specstream, the project file wins.

The user file is .mcp.json in ForgeCode's config folder: ~/forge on installs that already have that folder, ~/.forge on new ones, or the folder FORGE_CONFIG names. After you edit a file by hand, run forge mcp reload.

What ForgeCode calls

ForgeCode lists SpecStream's tools with the rest of its tools, and the agent picks them by the task.

  • search_web answers a question from the live web, with the sources it read, each with url, title, site and snippet.
  • read_pages returns the main text of up to 20 pages as Markdown.
  • compile reads a request for structured data and says what SpecStream will look for. quote_capacity_work prices it and spends nothing.
  • authorize_capacity_work starts the work after you approve the maximum, and list_find_rows reads the rows, with a source URL and read time on every value.

Why SpecStream in a coding agent

A coding agent needs release notes, changelogs and API docs as they read today. SpecStream's Search API reads each answer from the live web at the moment of the call. It scores 97.9 F-score on all 1,000 SimpleQA Verified questions and 64.0 item F1 on all 200 WideSearch tasks. Scores and method are on the benchmarks page.

Cost

Adding SpecStream to ForgeCode is free. Each search_web call is one Search API call at $5 per 1,000 searches of up to 10 results, and each page read_pages reads is $0.80 per 1,000 pages; a page with no text is not charged. Both come out of your balance with no quote and no approval, within the key's spending limit.

Deep Search is priced per row, and nothing runs until you approve the maximum its quote shows: authorize_capacity_work needs it in confirm_max_cents, and a run cannot cost more. See billing.

If it does not connect

  • forge mcp list shows the configured servers, and forge mcp show specstream shows the entry ForgeCode read.
  • A 401 means no token or key reached SpecStream. Run forge mcp login specstream again, or check that SPECSTREAM_API_KEY is exported in the shell that starts ForgeCode.
  • A tool call stops after 300 seconds unless the entry sets timeout, in seconds.
  • "disable": true in the entry turns SpecStream off without deleting it.

Disconnect

forge mcp logout specstream removes the stored token, and forge mcp remove specstream removes the entry; add --scope user for the user file. Revoke a key in SpecStream's Agents & API. Every tool is described in the MCP guide. Questions go to [email protected].

More

SpecStream for ForgeCode covers what it does in ForgeCode on one page. Every other tool has its guide in Connect your tools. You see the most a request can cost before it starts, and the matches are paid from your balance. Billing has the details. For help, email [email protected].