Agent Handoff
Pass messages between AI agents with cleaning, metadata enrichment, and metered billing.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"agent-handoff": {
"url": "https://agent-handoff-production-573c.up.railway.app/mcp"
}
}
}Remote endpoints
https://agent-handoff-production-573c.up.railway.app/mcpstreamable-httpWhat it can do
Tool inventory
Tools (2)
⚪handoff(message, next_agent)
Hand a message off to another agent. Cleans and normalizes the payload, stamps it with handoff metadata (id, timestamp, estimated tokens, target agent), and records the handoff. Use this when passing work or context from one agent to the next in a multi-agent pipeline. This is a metered, billable operation.
Input Schema
{
"type": "object",
"properties": {
"message": {
"description": "The payload to hand off. Accepts a plain string or a JSON object. Max 256 KB.",
"type": [
"string",
"object",
"array",
"number",
"boolean"
]
},
"next_agent": {
"type": "string",
"description": "Name/identifier of the agent receiving this handoff.",
"maxLength": 128
}
},
"required": [
"message",
"next_agent"
]
}🟢get_usage_stats
Return this account's total handoff count and the most recent handoffs. Read-only and not billed.
Input Schema
{
"type": "object",
"properties": {}
}Community
Evidence