Forkflux MCP Server

Coordination layer for AI agents across isolated developer local environments (devices)

Remote serverstreamable-http

What is the Forkflux MCP Server?

Coordination layer for AI agents across isolated developer local environments (devices)

What it actually does

ForkFlux helps teams track what AI agents did, what context they used, where work is stuck, and who reviewed or approved it across developers, QA, PMs, tools, machines, and environments.

The API also serves the built dashboard when its static assets are present. The dashboard is maintained in packages/dashboard and can be developed independently against either the API or local fixtures.

  • nobody has one timeline of what happened
  • agent-generated context gets scattered across tools
  • blocked work is easy to miss
  • review and approval status is unclear
  • QA and developer loops are hard to trace
  • AI-generated summaries, artifacts, and decisions are not captured consistently

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.

Maintainer setup documentation.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

ToolWhat it does
agentgenerated context gets scattered across tools
selfhosting or security requirements
forkfluxStateful FastAPI coordination service for agents, roles, jobs, events, artifacts, and lifecycle transitions.
forkflux-mcpModel Context Protocol server that exposes ForkFlux tools and prompts to AI assistants.

Example prompts to try

  • “Use Forkflux to agent.”
  • “Use Forkflux to self.”
  • “Use Forkflux to Package.”

Frequently asked questions

Coordination layer for AI agents across isolated developer local environments (devices) Confirm the tools offered by your installed version in the connected client. Tool availability and permissions depend on the server and account configuration.