Echorift Mcp
Operate EchoRift primitives—BlockWire, CronSynth, Switchboard, and Arbiter—from your agent via MCP instead of juggling separate CLIs.
Overview
EchoRift MCP is an Operate-phase MCP server that exposes BlockWire, CronSynth, Switchboard, and Arbiter infrastructure tools to AI agents.
What is this MCP server?
- Single MCP surface for four EchoRift primitives: BlockWire, CronSynth, Switchboard, Arbiter
- @echorift/mcp npm 0.1.0 with stdio transport and optional treasury tools via ECHORIFT_ENABLE_TREASURY
- CronSynth x402 session env CRONSYNTH_X402_SESSION for paid cron flows
- Switchboard signing via SWITCHBOARD_AGENT_ID and SWITCHBOARD_PRIVATE_KEY
- Early 0.1.0 release—infra MCP, not a hosted PaaS dashboard
- Registry and package version 0.1.0
- Four named primitives in description: BlockWire, CronSynth, Switchboard, Arbiter
- stdio transport; up to four documented environment variables plus optional treasury flag
What problem does it solve?
Running EchoRift primitives from an agent session means copying CLI calls and env secrets across four different surfaces.
Who is it for?
Indie agent operators already on EchoRift who want MCP-native control of cron, routing, and treasury-adjacent infra.
Skip if: Builders with no EchoRift deployment who only need generic cron or a simple VPS deploy skill.
What do I get? / Deliverables
One stdio MCP registration lets your agent invoke BlockWire, CronSynth, Switchboard, and Arbiter tools with centralized env-based auth.
- Unified MCP tool access to four EchoRift primitives
- Optional treasury tool surface when enabled by env flag
- Agent-operable infra changes without custom shell scripts per service
Recommended MCP Servers
Journey fit
EchoRift tools manage live agent infrastructure, scheduling, and routing after you have something running in production. BlockWire, CronSynth, Switchboard, and Arbiter are operational infra controls, which maps to the infra subphase.
How it compares
EchoRift-specific infra MCP with wallet signing hooks, not a general cloud provisioning marketplace.
Common Questions / FAQ
Who is EchoRift MCP for?
Developers operating EchoRift-backed agent systems who want BlockWire, CronSynth, Switchboard, and Arbiter reachable from Claude Code or Cursor.
When should I use EchoRift MCP?
Use it in Operate when you adjust schedules, routing, or treasury-enabled automation on a live EchoRift stack from an agent.
How do I add EchoRift MCP to my agent?
Install @echorift/mcp, set CRONSYNTH_X402_SESSION and Switchboard variables as needed, optionally ECHORIFT_ENABLE_TREASURY=1, and add the stdio server to your MCP config.