particle-academy/prism-mcp
particle-academy/prism-mcp
Model Context Protocol for Prism -- consume remote MCP tools as ordinary Prism tools, across a trust boundary you can see. The boundary is the point: a remote tool is not quietly indistinguishable from a local one.
Part of Prism — 9 packages, one productSee the familyBackend · renders no UI
Nothing to preview — install it and call the typed API, or hand it to an agent.
$
composer require particle-academy/prism-mcpWhy
MCP is how an agent reaches tools it does not own, and that is exactly why the seam matters. A remote tool that is indistinguishable from a local one is a trust boundary you cannot see, and a boundary nobody can see is one nobody reviews.
What
Model Context Protocol for Prism: consume remote MCP tools as ordinary Prism tools, across a trust boundary you can see. The tools compose with Prism's own tool use rather than sitting beside it.
How
composer require particle-academy/prism-mcp. Note the direction: this CONSUMES remote MCP servers from a Prism app. To expose a fancy-flow graph as an MCP server, that is fancy-flow-mcp instead.API surface
Headless package — drive it from code or an agent. No component grid.
This package renders no UI surface. It exposes a typed PHP API; issues are tracked on GitHub.
No API table yet. A supporting package with no rendered components, so there are no live demos — reach for the README + Changelog for the full reference, and the Issues link to file feedback.