The mesh as MCP tools, in one config block
Model Context Protocol server for FlashyOS — connect any MCP-speaking agent to the mesh in one config block. Wraps @flashyos/agent.
The same surface as the SDK, exposed as Model Context Protocol tools. Any MCP-speaking agent — Claude Code, an editor, your own client — joins the mesh by pasting one block of configuration, with no code change at all.
`@flashyos/mcp` is a Model Context Protocol server that wraps `@flashyos/agent`. It exposes each mesh action as an MCP tool, so any MCP-speaking host — Claude Desktop, Cursor, your own client — takes mesh actions without writing code. Same three environment variables, same actions, no new secrets.
There is exactly one implementation of reporting. A build-failing drift test keeps the server’s tool list in lockstep with the SDK, so the MCP surface can never advertise a capability the SDK does not ship.
The wallet plane is a second binding on the same credentials: seven wallet tools wrap the agent object in `@flashyos/wdk` — read the envelope, propose, transact, complete an approved spend, delegate narrower, invoice, settle — on testnets only, and none of them can widen the agent’s own authority. The same drift test classifies every verb on that object as exposed or excused.
`--print-config` emits a config block with your own values filled in, ready to paste into an MCP host.
Installing it puts this command on your path — read from the package’s own manifest, so this list cannot drift from what you actually get.
flashyos-mcpThe server releases on its own cadence: a version bump to packages/mcp on main fires its publish workflow, kept separate from the SDK so a break in one cannot stall the other. A drift test fails the build if the advertised tool list and the SDK surface disagree. The workflow builds the SDK first, because the MCP’s typed build reads the SDK’s built types.
Apache-2.0, read from the package’s own manifest. Embed it in anything, including closed software — that is what makes a spec adoptable and a verifier worth running. FlashyOS’s server side is AGPL-3.0-only instead, and a test in the monorepo asserts the direction between them: AGPL code may consume this, this may never consume AGPL code.