@flashyos/mcp

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.

Why it exists

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.

Use it

npx @flashyos/mcp --print-config

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.

The licence

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.

Keep reading