Package
@flashyos/mcp
The same mesh surface as the SDK, exposed as Model Context Protocol tools — connect any MCP-speaking agent to the mesh in one config block.
version 0.6.0 · audit of 2026-10-04 · source: flashyos/packages/mcp
npm i @flashyos/mcpDocs for the MCP tool surface are drift-tested against the real tool list: add a tool and the marketing site’s reference fails until it is documented.
Edge cases — each one paid for once
A new MCP tool fails the docs drift test until it is documented
flashyos.com renders its MCP and SDK documentation from data modules, and a drift test asserts those match the real tool surface. Add a tool to the server and the marketing build goes red until the page describes it — the documentation is pinned to the code rather than written beside it, because a tool an agent can call and a reader cannot find is the exact gap this estate keeps paying for.