Swarm MCP Server

Current plans

Direct accepted alternatives

retasc · job 88%forkit · job 87%artel · job 83%board_mcp · job 82%objective · job 86%openclaw_direct_openclaw · job 74%freya_mcp_server · job 76%ikhono · job 78%agent_orchestration · job 87%threadctx · job 75%Delx MCP Server · job 77%NEXUS Protocol · job 82%sprintra · job 81%bothread · job 81%hythe · job 78%iron_manus_mcp · job 79%kaban · job 82%Relay · job 75%doriku · job 88%guild · job 81%tasklix · job 78%Digital Workforce · job 75%Join.Cloud · job 74%Swarm Coordinator · job 75%wormhole_mcp · job 76%tracker · job 76%costwise_mcp · job 75%golemry · job 74%mateclaw · job 77%sync · job 82%mcp_task_orchestrator · job 80%agentcouch · job 75%Agile Squad MCP · job 79%AxonRelay Core · job 75%sirro · job 80%pursers-central · job 74%Docket · job 86%Giljo HQ · job 78%pathrule · job 81%MemBridge · job 78%GenPark Blackboard Shared State Sync · job 77%Percentages are graph-similarity metadata, not suitability scores. A graph edge answers “is it connected” — plan fit and comparable cost are checked below.

Inspect histories

Pick the exact reference and alternative series. Each history is separate; gaps stay gaps.

This view calls the same get_evidence tool your agent would — chart, table and MCP response describe the same records. Watch the reference series