MCP server for EchoRift infrastructure primitives (BlockWire, CronSynth, Switchboard, Arbiter)
npm install @echorift/mcpOfficial MCP server for EchoRift infrastructure primitives (BlockWire, CronSynth, Switchboard, Arbiter). Makes EchoRift's agent infrastructure callable as MCP tools so any MCP client can treat EchoRift like a native capability layer.
``bash`
npx @echorift/mcp
`bashBlockWire (optional, defaults to https://blockwire.echorift.xyz)
BLOCKWIRE_BASE_URL=https://blockwire.echorift.xyz
MCP Client Configuration
$3
Use this configuration for Claude Desktop or any MCP client supporting stdio transport:
json
{
"mcpServers": {
"echorift": {
"command": "npx",
"args": ["@echorift/mcp"],
"env": {
"CRONSYNTH_X402_SESSION": "your-session",
"SWITCHBOARD_AGENT_ID": "0x...",
"SWITCHBOARD_PRIVATE_KEY": "0x..."
}
}
}
}
`$3
For clients supporting remote HTTP endpoints:
json
{
"mcpServers": {
"echorift": {
"url": "https://mcp.echorift.xyz/api/mcp",
"transport": "http"
}
}
}
`Note: Stdio mode is recommended for production use. Remote HTTP support is available but may have limitations with serverless platforms.
Remote Endpoint Setup
The server supports both stdio (local) and remote HTTP endpoints. Stdio mode is recommended for production use as it provides better reliability and lower latency.
$3
Stdio mode runs the server locally as a child process:
bash
npx @echorift/mcp
`This is the most reliable and performant option. See "MCP Client Configuration" above for config snippet.
$3
For remote deployments (e.g., Vercel), the server exposes an HTTP endpoint:
Endpoint:
Transport Type:
(compatible with MCP remote clients)Usage:
`json
{
"mcpServers": {
"echorift": {
"url": "https://mcp.echorift.xyz/api/mcp",
"transport": "http"
}
}
}
`Note: Full HTTP/SSE transport requires long-running connections, which can be challenging with serverless platforms. Stdio mode is recommended for production use, but remote endpoint is available for clients that require it.
$3
1. Clone and deploy:
bash
git clone https://github.com/echorift/echorift-mcp.git
cd echorift-mcp
vercel deploy
`2. Set environment variables in Vercel dashboard:
-
-
-
- Other optional service URLs3. Configure domain: Point
to your Vercel deployment4. Verify: Visit
https://mcp.echorift.xyz/api/mcp (GET request) to verify server info$3
Different MCP clients support different transport modes:
- Claude Desktop: Supports stdio mode (recommended)
- Custom clients: May support HTTP/SSE or Streamable HTTP
Refer to your MCP client's documentation for remote server configuration options.
Tools
$3
-
blockwire_subscribe_prepare_tx - Generate on-chain transaction payload for webhook subscription
- blockwire_feed - Pull recent blockchain events via x402 endpoint$3
-
cronsynth_schedule_create - Create a scheduled webhook trigger with cron expression
- cronsynth_schedule_list - List all scheduled webhook triggers
- cronsynth_schedule_delete - Delete a scheduled webhook trigger$3
-
switchboard_task_enqueue - Enqueue a task to a swarm queue
- switchboard_task_claim - Claim a task from a swarm queue
- switchboard_task_complete - Mark a claimed task as complete$3
-
arbiter_lock_acquire - Acquire a distributed lock with fencing token
- arbiter_lock_release - Release a distributed lock using fencing token
- arbiter_leader_get - Get current leader for a swarm
- arbiter_election_run - Run a leader election for a swarmResources
-
echorift://queues - Switchboard swarm queues and stats
- echorift://cron/jobs - CronSynth scheduled jobs
- echorift://blockwire/subscriptions - BlockWire webhook subscriptions
- echorift://arbiter/locks - Active Arbiter distributed locksPrompts
-
swarm-safe-cron - Create a swarm-safe task pipeline with cron scheduling
- chain-event-router - Subscribe to chain events and route tasks by event type
- distributed-locking - Set up distributed locking for exclusive resource accessCapability Map
Quick reference for common needs:
- Need timers? ā
cronsynth_schedule_create
- Need exclusive portfolio writes? ā
- Need a work queue? ā
- Need chain event ingestion? ā š Full Capability Map - Detailed guide with examples and use cases
š OpenAPI Specification - Complete API schema
Security Model
- What data leaves the machine? All tool calls are forwarded to EchoRift API endpoints. Authentication credentials (x402 sessions, private keys) should be kept secure via environment variables.
- What is gated? Treasury tools require
MIT