Forkflux MCP server

ForkFlux 🐜

Self-hosted coordination and audit layer for AI-assisted engineering teams.

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.

📚 Documentation: https://docs.forkflux.ai/

🎥 ForkFlux in action

Why ForkFlux exists

AI coding agents are becoming part of real engineering workflows. They write code, review changes, run tests, update tickets, summarize work, and hand tasks between developers, QA, PMs, and other agents.

But most teams still track AI-assisted work through a messy mix of Slack messages, Jira or Linear comments, GitHub PRs, temporary markdown files, local agent sessions, and CI logs.

That creates a visibility gap:

• 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
• teams cannot easily answer "what did the agent do, why, and who checked it?"

ForkFlux gives AI-assisted engineering teams a shared workflow timeline for handoffs, context, artifacts, blockers, status changes, and approvals.

What ForkFlux is

ForkFlux is a self-hosted coordination and audit layer for AI-assisted engineering work.

It captures structured workflow events from agents and humans, including:

• task handoffs
• context payloads
• changed files, branches, commits, PRs, and other artifacts
• status changes
• blocked and failed work
• review notes
• approval events
• handoff history between roles and teammates

The goal is not to replace Jira, Linear, GitHub, Slack, or your AI coding tools.

ForkFlux sits alongside your existing workflow and gives your team a structured record of AI-assisted work that would otherwise be scattered across comments, chats, local sessions, and temporary files.

What it is NOT

❌ ForkFlux is not another AI assistant.

❌ ForkFlux is not a local agent framework.

❌ ForkFlux is not shared memory for one developer’s local agents.

❌ ForkFlux is not a replacement for Jira, Linear, GitHub, or Slack.

🔗 ForkFlux is infrastructure for teams that already use AI agents and need better visibility, coordination, and auditability around the work those agents touch.

How it works

ForkFlux coordinates AI-assisted work through a shared, self-hosted workflow layer.

A typical workflow looks like this:

1. A developer or PM starts a task in their normal workflow.
2. An AI assistant performs work, such as changing code, updating an API contract, writing tests, or preparing a review.
3. The assistant publishes structured context to ForkFlux: summary, target role, constraints, artifacts, links, and next action.
4. Another teammate or agent claims the work, such as QA, reviewer, frontend, backend, DevOps, or PM.
5. ForkFlux records the status transition and keeps the full handoff history.
6. If work is blocked, failed, completed, or needs human approval, that event is captured in the timeline.
7. The team can inspect what happened, where work is stuck, and what needs attention next.

ForkFlux started with agent-to-agent handoffs. The broader goal is to provide an audit trail and control layer for AI-assisted engineering workflows.

What is included

ForkFlux is a monorepo with two main packages:

Shortened. The full README is on GitHub.