janreges/axon-mcp
If you are the rightful owner of axon-mcp and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.
Axon is a Model Context Protocol (MCP) server designed to facilitate task and message coordination between AI agents.
MCP Task Management Server
Production-ready server for orchestrating and coordinating tasks between multiple AI agents.
MCP Task Management Server is a robust and reliable solution designed for efficient task management in multi-agent systems. If you're building applications where multiple AI agents need to collaborate, share work, and communicate, our server provides a centralized hub that simplifies the entire process and ensures reliable task management.
Forget about complex setup and state management. Thanks to the zero-configuration approach using SQLite, the server is ready to use within seconds. Focus on your agents' logic, not on task management infrastructure.
โจ Key Features
- ๐ค Seamless Multi-Agent Coordination: Enables multiple agents to efficiently collaborate on shared goals, claim tasks, and share results
- ๐ Production-Ready & Robust: Designed for real-world deployment with race condition handling and reliable task timeout mechanism (15 minutes; timed-out tasks are automatically released back to the pool)
- ๐ Comprehensive MCP Implementation: Full support for 22 key MCP functions covering the entire task lifecycle โ from creation through claiming to completion
- โก Zero-Configuration Setup: Thanks to integrated SQLite database (single-file), server startup is trivial. No external database server dependencies
- ๐ฌ Built-in Messaging: Agents can communicate directly with each other through the built-in messaging system, facilitating complex coordination
- ๐ฏ Workspace Automation: Ideal for workflow automation where tasks need to be dynamically assigned and their status tracked
1. ๐ฆ Installation
# Download and install the latest binary (macOS / Linux x86_64)
curl -s https://raw.githubusercontent.com/janreges/axon-mcp/main/install.sh | bash
# For Windows users, please refer to the "Building from Source" section
# or check the GitHub Releases page for pre-built binaries
# Script will output the final path, e.g.:
# Installed axon-mcp to /usr/local/bin/axon-mcp
๐ก Note: Remember the displayed path โ you'll need it in the next step.
2. ๐ Starting the MCP Server
Before starting, replace the parameters in <> with your actual values:
# Replace <project-name> with your project name (no spaces)
# Replace <full-path-to-project> with the full path to your project
axon-mcp --start \
--port=8499 \
--project=<project-name> \
--project-root="<full-path-to-project>"
Example with real values:
axon-mcp --start \
--port=8499 \
--project=my-web-app \
--project-root="/Users/jan/projects/my-web-app"
What happens:
- Creates
.axon/
and.claude/
folders (if they don't exist) - Initializes SQLite DB as
.axon/axon.<project-name>.sqlite
- Server listens on
http://localhost:8499
3. ๐ Connecting Claude to Running Server
Prerequisites: Make sure you have the Claude CLI tool installed before proceeding.
cd <full-path-to-project>
claude mcp add --url http://127.0.0.1:8499
Example:
cd /Users/jan/projects/my-web-app
claude mcp add --url http://127.0.0.1:8499
โ Done! Claude now forwards all MCP calls over HTTP; no additional setup needed.
4. Feature Highlights
- Multi-agent coordination โ HTTP transport supports concurrent requests from multiple agents
- Task discovery & claiming โ agents can find and atomically claim work based on capabilities
- Inter-agent messaging โ targeted communication within task contexts with threading support
- Per-project isolation โ each project gets its own database, no cross-project data leakage
- Complete MCP spec โ all 22 MCP functions available via JSON-RPC over HTTP
- Production logging โ structured request logs with timing and parameter truncation
4.1 Structured Request Logging Example
When you run commands, you'll see clean, single-line logs like:
2025-08-04 13:16:30 [health_check] [0 ms]
2025-08-04 13:16:36 [create_task] [0 ms] code="TASK-001", description="Long description text...", name="Task name..."
2025-08-04 13:17:02 [create_task_message] [0 ms] author_agent_name="[REDACTED]", content="Message content...", message_type="handoff"
Features:
- Timestamp in YYYY-MM-DD HH:MM:SS format
- Function name in brackets
- Execution time in milliseconds
- Parameters with strings truncated to 30 characters + "..."
- Sensitive data redaction for security (passwords, tokens, keys)
- Array formatting as
[N items]
for clean output
5. Complete MCP Function Reference
Axon implements 22 comprehensive MCP functions organized in four categories:
๐ Core Task Management (9 Functions)
create_task
- Create new tasks with validationupdate_task
- Modify task metadata and descriptionsassign_task
- Transfer ownership between agentsget_task_by_id
- Retrieve task by numeric IDget_task_by_code
- Retrieve task by human-readable code (e.g.,TASK-123
)list_tasks
- Query tasks with filters (owner, state, date range)set_task_state
- Change task lifecycle state with validationarchive_task
- Move completed tasks to archivehealth_check
- Check server health and status
๐ค Multi-Agent Coordination (5 Functions)
discover_work
- Find available tasks based on agent capabilitiesclaim_task
- Atomically claim unassigned tasks for executionrelease_task
- Release claimed tasks back to the poolstart_work_session
- Begin time tracking for task workend_work_session
- Complete work session with productivity metrics
๐ฌ Inter-Agent Messaging (2 Functions)
create_task_message
- Send targeted messages within task contexts- Types:
handoff
,question
,comment
,solution
,blocker
, custom - Threading: Reply chains with
reply_to_message_id
- Types:
get_task_messages
- Retrieve messages with advanced filtering- Filter by sender, recipient, message type, threading
๐ Workspace Setup Automation (6 Functions)
get_setup_instructions
- Generate AI workspace setup instructionsget_agentic_workflow_description
- Generate agent workflow recommendationsregister_agent
- Register AI agent with capabilities and contact infoget_instructions_for_main_ai_file
- Get template for main coordination filecreate_main_ai_file
- Generate main AI coordination file (CLAUDE.md, etc.)get_workspace_manifest
- Generate complete workspace manifest
6. Technical Details
Why HTTP transport?
HTTP-only design choice: Traditional STDIO-based MCP servers cannot handle concurrent requests needed for multi-agent coordination, task discovery, and long-polling workflows. Our server uses HTTP transport to enable simultaneous agent connections and real-time task coordination.
Architecture
Multi-crate Rust workspace designed for performance and maintainability:
axon-mcp/
โโโ core/ # ๐งฉ Domain models and business logic
โโโ database/ # ๐๏ธ SQLite repository implementation
โโโ mcp-protocol/ # ๐ MCP server with HTTP transport
โโโ mcp-server/ # ๐ Main binary and configuration
โโโ mocks/ # ๐งช Test utilities and fixtures
Comparison with Traditional MCP Servers
Traditional MCPs | Axon MCP | |
---|---|---|
Transport | STDIO (single request) | HTTP (concurrent) |
Use Case | Single agent interaction | Multi-agent coordination |
State storage | Flat files | .axon/axon.<PROJECT>.sqlite |
Integration | Custom configuration | claude mcp add (built-in) |
Key Technical Advantages:
- Concurrent request support: HTTP enables multiple agents to work simultaneously
- Task coordination: Atomic claiming, work sessions, and inter-agent messaging
- Project-scoped databases: Each project gets its own SQLite file
- Production ready: Structured logging, health checks, graceful shutdown
7. Troubleshooting
Symptom | Possible Fix |
---|---|
Port 8888 already in use | Pick another port: --port=9090 |
axon-mcp: command not found | Confirm the install path shown by the curl script is on $PATH , or invoke it with the absolute path. |
claude mcp add fails to connect | โข Verify the MCP server URL and port. โข Ensure the server is running in the same network namespace. โข Check for proxy/firewall rules blocking localhost. |
Database locked errors | Rare on local FS; if seen, ensure only one server instance points at the same .axon/*.sqlite . |
Need verbose output | Start the server with --log-level=debug . |
8. Example Usage with curl
Once your server is running, you can test it with curl:
Note: The MCP-Protocol-Version
header specifies the API version for compatibility.
# Health check
curl -X POST http://127.0.0.1:8499/mcp \
-H "Content-Type: application/json" \
-H "MCP-Protocol-Version: 2025-03-26" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "health_check",
"params": {}
}'
# Create a task
curl -X POST http://127.0.0.1:8499/mcp \
-H "Content-Type: application/json" \
-H "MCP-Protocol-Version: 2025-03-26" \
-d '{
"jsonrpc": "2.0",
"id": 2,
"method": "create_task",
"params": {
"code": "DEMO-001",
"name": "Example Task",
"description": "This is a demo task created via HTTP"
}
}'
# List tasks
curl -X POST http://127.0.0.1:8499/mcp \
-H "Content-Type: application/json" \
-H "MCP-Protocol-Version: 2025-03-26" \
-d '{
"jsonrpc": "2.0",
"id": 3,
"method": "list_tasks",
"params": {
"limit": 10
}
}'
9. Development
Building from Source
# Clone and build
git clone https://github.com/janreges/axon-mcp.git
cd axon-mcp
cargo build --workspace
# Run tests
cargo test --workspace
# Start development server
cargo run --bin axon-mcp -- --start --port=8888 --project=dev --project-root=/tmp/dev-project
Useful Make Commands
make help # Show all available commands
make build # Build all crates
make test # Run all tests
make check-status # Show project status
10. Contributing & Feedback
We love PRs, issues and suggestions.
Open a ticket or contribute at GitHub Issues.
11. License
MIT ยฉ 2025 Jan Reges & Contributors. See for full text.
๐ง Axon MCP: Task coordination and management for AI agents.