Firedrill

io.github.firedrill-toolsPublished by GitHub account firedrill-toolsv2.2.2Updated Nov 7, 2026

Operate simulations and inspect retained evidence with Firedrill.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Remote Firedrill operator server that lets a coding agent discover schemas, prepare simulations, and inspect retained evidence.

What you can do
  • Discover schemas and context: read the advertised tool definitions and choose a project or environment
  • Prepare simulations: preview and admit small authored recipes, with optional checks and Tools
  • Inspect and compare results: read reports and retained evidence for runs using exact scope and cursors
  • Manage synthetic Tools: handle authorized, short-lived synthetic target Tools
  • Guide execution handoff: return continuation details so a customer-owned runner can attach to the same batch
When to use it
Use it when you want a coding agent to set up and review Firedrill simulations and their retained evidence on your behalf, while actual target execution stays with a separately authorized customer-owned runner.
Requirements
A remote Streamable HTTP endpoint; no local package, CLI or Node.js install is needed. Browser OAuth sign-in through WorkOS is required, with the host storing the credential. Account creation, email verification and invitations remain manual steps.
Before you install
Mutations require saved idempotency keys, so reconcile uncertain replies rather than repeating actions. Synthetic Tool grants are separate short-lived target credentials; never copy operator tokens into target input or model context. Native command execution is not a sandbox, and Tool rewind does not reset the external app. Do not paste tokens into chat or repository configuration, and do not transfer credentials between MCP, CLI and CI clients.

Installation

In SourceWeft

  1. Open Firedrill in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.firedrill-tools%2Ffiredrill/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "firedrill": {
      "type": "http",
      "url": "https://mcp.firedrill.run/mcp"
    }
  }
}

README

Firedrill operator MCP

Operate Firedrill from a coding agent: discover schemas, prepare simulations, inspect retained evidence, compare runs and manage authorized synthetic Tools. This is the operator → Firedrill connection on the human's behalf. It does not sign in to the coding-agent provider or the application being simulated.

Connect directly

Use Firedrill's remote Streamable HTTP endpoint:

text
https://mcp.firedrill.run/mcp

No local MCP package, Firedrill CLI or Node.js installation is required for this connection. Configure it through your host's native commands. For Codex:

sh
codex mcp add firedrill --url https://mcp.firedrill.run/mcpcodex mcp login firedrill

For Claude Code project scope:

sh
claude mcp add --scope project --transport http firedrill https://mcp.firedrill.run/mcpclaude mcp login firedrill

Codex writes user-wide MCP settings. Claude uses the selected project's .mcp.json and asks for project approval. In Cursor, add "firedrill": { "url": "https://mcp.firedrill.run/mcp" } under mcpServers in .cursor/mcp.json and use its browser sign-in. In Kimi Code, use /mcp-config to add a project HTTP server at that URL, then /mcp-config login firedrill. Preserve other servers. Skills/plugin installation is a separate native action.

For one-click setup links and host-specific instructions, open Connect your agent.

The browser authorization uses WorkOS. Review the identity and intended organization, and let the host store its OAuth credential privately. Do not paste tokens into chat or repository configuration. Account creation, email verification, invitations and host trust remain explicit human steps when required; never bypass them with another identity or replacement organization.

Remote MCP can prepare work and read retained results; it cannot execute a repo on the customer's machine. Actual target execution uses a separately authorized customer-owned CLI/SDK runner. CLI sign-in is separate from the MCP host's OAuth session. CI supplies its own scoped credential through a secret store and never opens browser approval. Do not transfer credentials between these clients.

First useful workflow

  1. Read firedrill_discover, then the advertised firedrill_schema definitions.
  2. Read firedrill_context and deliberately choose the project/environment.
  3. Inspect the application's real command, HTTP or native invocation seam. Preview a small authored recipe before admitting it. Checks and Tools are optional; evaluation is a separate explicit choice.
  4. If authorized to execute, preserve the creation key and exact arguments. Follow the returned continuation through the CLI or native SDK to attach a customer-owned runner to that same batch. Do not create a second batch.
  5. Read reports/evidence using exact scope and returned cursors. Keep execution, outcome, assessment and CI gate separate; missing evidence is not zero.

Mutations require saved idempotency keys. After an uncertain reply, reconcile the same action/key; never repeat a target merely to recover its evidence. Synthetic Tool grants are separate, short-lived target credentials. Never copy operator tokens into target input or model context. Native/ordinary command execution is not a sandbox, and Tool rewind does not reset the external app.

The companion firedrill-skills repository supplies optional task-oriented instructions. Installing instructions is not permission to run a simulation, upload customer source, change workspace trust or authorize another account.

Repository contents

server.json describes the remote Streamable HTTP endpoint for the official MCP Registry. Connecting uses that endpoint, not an npm MCP installation. Registry metadata does not deploy a server or prove that browser authorization works.

Previously distributed client source, exact dependency records and their license notices remain in this repository. They contain no Firedrill engine, service, database or managed HTTP server. Their presence is not an onboarding step, and local environment settings do not configure the managed remote connection.

License

The client is proprietary under the client use permission. Third-party code retains its own notices under notices/ and bundled package licenses. A readable source export does not make the private service open-source.

Source: README.md at commit 0a47912

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

3
  1. v2.2.2LatestOct 19, 2026
  2. v2.1.0Oct 18, 2026
  3. v2.0.0Oct 18, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.