Skip to content

MCP tools

Server: npx -y @forkstage/mcp (stdio). It uses the sign-in and driver settings of the machine it runs on, the same as the CLI.

Tool Input Result
environment_create repository? (path, current by default), driver? the fork’s id and address, plus a paragraph telling the agent what it has and how to use it
environment_status environment? the forks this machine knows about, with service states
environment_exec environment?, command, service?, timeout? exit code and output; recorded in the proof
environment_http_request environment?, method, path, headers?, body? status, headers and body from the fork’s app; recorded
environment_test environment?, only? each test run with result and counts; recorded
environment_logs environment?, service?, tail? recent logs
environment_note environment?, text writes a line into the proof, in the agent’s words
environment_destroy environment? strikes the fork and returns the proof’s headline

environment defaults to the latest fork created from the repository.

Forkstage gives you a disposable copy of this repository’s whole stack. Create one with environment_create at the start of a task, then use exec, http_request and test inside it to run the app, reproduce the bug and prove your change. Everything you run is recorded as proof for the pull request. Destroy it with environment_destroy when you finish.

  • Tools never return secrets; the fork’s database is reachable only through environment_exec.
  • Long commands: timeout is in seconds, up to 3600.
  • The server is a plain JSON-RPC stdio process with no network listener of its own.