LabscoMCP early access ↗
Piotr1215MCP SERVER · OFFICIAL PROJECT

MCP Agentic Framework

Let several agents talk to each other — register an identity, discover who else is online, exchange direct messages and broadcasts through a file-backed queue.

by Piotr1215 ↗Reasoning Scaffolds & Agent Workflow Engines✓ Official

No longer maintained. The GitHub repository for this server is archived — no fixes or security updates are expected.

View project ↗

LABSCO SUMMARY

Bidirectional messaging, which is what sub-agents do not give you.

Claude Code's sub-agents are invoked and return; here agents register at runtime and message each other in both directions, which is what you need when a task involves discussion or disagreement rather than delegation. The trade-off is that nothing is predefined — an agent exists because it registered, and dies when it unregisters. Two behaviours to plan around: a message is deleted once read, so it can only be collected by one agent once, and a broadcast never reaches its own sender.

What it is

An MCP server that acts as a message bus between agents. Each agent registers itself at runtime with a name and a description, discovers the others, and exchanges asynchronous messages — one to one, or broadcast to everyone. Storage is plain files, so there is nothing external to run.

What you get

  • An agent registered with a display name and a description of its role, and removed again when it is done — register-agent, unregister-agent
  • Every currently registered agent listed with its id, description, status and last activity time — discover-agents
  • Direct messages sent between two agents by id, and unread messages collected — each message readable once, then deleted — send-message, check-for-messages
  • A broadcast to every registered agent except the sender, at low, normal or high priority, returning how many recipients it reached — send-broadcast
  • An agent's status set to online, offline, busy or away, so the others can see who is available — update-agent-status
  • Help drafting a reply, a status update, a yes/no decision or an analysis for an agent, answered through MCP sampling — agent-ai-assist; and one switch that turns write access on or off for every agent at once, callable only by the agent the server names — toggle-writes
  • Agents and messages stored under /tmp/mcp-agentic-framework/, with file locking to keep concurrent writes from colliding and no outbound network calls

Requirements

No account and no key. It is not on npm — install from a clone with npm install, then start it with npm run start:http and point the client at http://127.0.0.1:3113/mcp with "type": "http", which also gives you a /health endpoint. Kubernetes manifests and a Justfile are included for running it as a shared service behind a LoadBalancer.

Setup effort

Build from source — git clone https://github.com/Piotr1215/mcp-agentic-framework.git