Coordination layer for AI agents across isolated developer local environments (devices)
Coordination layer for AI agents across isolated developer local environments (devices)
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.
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| agent | generated context gets scattered across tools |
| self | hosting or security requirements |
| forkflux | Stateful FastAPI coordination service for agents, roles, jobs, events, artifacts, and lifecycle transitions. |
| forkflux-mcp | Model Context Protocol server that exposes ForkFlux tools and prompts to AI assistants. |
Read, search and edit files inside allowed directories with the Model Context Protocol reference Filesystem server.
Retrieve version-aware library documentation and code examples with Context7 MCP, using resolve-library-id and query-docs.
An MCP server that gives your AI assistant direct access to your system clipboard: read what you copied, or write clean text straight to it. Works with any MCP-compatible client, including Claude Code, Claude Desktop…
Track public GitHub repos: free snapshot, paid release, star & issue intel via x402 USDC.
Design your site's AI avatar in the ASMI studio; your coding agent ships it into your repo.
Model Context Protocol (MCP) server to execute aider-specific code editing operations