Prism MCP: work with Prismatic from your agent
Prism MCP
Local Prismatic MCP server: the agent scaffolds integrations and components, tests flows and publishes via the Prism CLI
- 27 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The agent creates and publishes components and imports integrations into your Prismatic account
- The server runs the Prism CLI in the working folder with the rights of your login
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/prism-mcpDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The agent creates and publishes components and imports integrations into your Prismatic account
- The server runs the Prism CLI in the working folder with the rights of your login
This is third-party code. Review the repository files before installing.
What it does
Prism MCP runs locally and works with Prismatic, a platform for embedded integrations aimed at B2B SaaS teams. The server calls the Prism CLI in the working folder you give it, so the agent acts as the same account you signed in with via prism login. Tools come in toolsets. General ones are always on: prism_me shows the profile and prism_components_list lists available components. The integration toolset creates a code-native integration (prism_integrations_init), converts a low-code integration to code-native, lists and tests flows, puts a flow into listening mode to capture a webhook payload, and generates scaffolding for a flow, a config page and config variables. The component toolset creates a component (including from WSDL or OpenAPI), builds its manifest and publishes it. If no toolset is passed, every tool is registered. Picking a single toolset, such as integration, shortens the tool list and, the authors note, helps performance.
Who it is for. Developers building integrations on Prismatic who write code-native integrations and custom components in Claude Code or Cursor.
Good fit when
- The integration starts from scratch and the agent should create the project skeleton and a first flow
- You are converting a low-code Prismatic integration to code-native and want to begin with the automatic conversion
- A flow waits for a webhook and its payload has to be captured in listening mode for later tests
- An internal API needs its own component, easier to generate from an OpenAPI or WSDL spec
- The component catalog is large and the agent needs a quick list with versions
Not a fit when
- You are starting fresh with Prismatic and want no separate package: since Prism 11 the server is built in and starts with prism --mcp, while the standalone package is deprecated
- You need guidance on integration architecture: the authors keep a separate agent-skills repository with guides for the agent
- You need access without signing in to Prismatic: the tools work only after prism login or with a refresh token
Example request
Create a code-native integration in this folder, add a webhook flow and capture its payload for testsMCP
- Transport
- stdio
- Authentication
- key is optional
Environment variables
PRISMATIC_URL- Prismatic URL, https://app.prismatic.io by default; change it for another region or a private stack.
PRISM_REFRESH_TOKENsecret- Refresh token for CI and headless environments instead of prism login.
Limitations
The standalone @prismatic-io/prism-mcp package is deprecated in favor of built-in support in Prism 11 and later, so new features are likely to land there.
It needs a Prismatic login: prism login writes credentials to a shared config, and CI sets PRISM_REFRESH_TOKEN instead. The first argument with the working folder is required, otherwise the server does not know where to run commands. For another region or a private stack, change PRISMATIC_URL, which defaults to https://app.prismatic.io. Generating a component manifest requires spectral 10.6.0 or newer.
How to disable. Remove the prism entry from .mcp.json or run claude mcp remove prism. The Prismatic login stays in the Prism CLI config, so sign out in the CLI if you no longer need it.
FAQ
How is the standalone prism-mcp different from the built-in prism --mcp?
The purpose is the same, but the built-in variant ships with Prism 11 and later and starts with prism --mcp. The standalone package is still available and the authors have deprecated it.
How do I install Prism MCP in Claude Code?
Run prism login, then claude mcp add-json prism with the README JSON: type stdio, command npx, arguments -y, @prismatic-io/prism-mcp and a dot. Or put the same block into .mcp.json in the working folder.
Can I enable only some tools?
Yes. After the folder path, list toolsets: integration or component. The general tools prism_me and prism_components_list stay on whatever you choose.
Does the server work in CI without a browser?
Yes, if you set PRISM_REFRESH_TOKEN instead of running an interactive prism login.
Do I need to install the Prism CLI separately?
Not for the server itself: it bundles its own pinned copy of the CLI. You need the global prism only to run prism login and store credentials.
Discussion
No questions or reviews yet.
Related
MCP serversThe Apideck MCP server: an agent works with over 200 business systems: accounting, HRIS, CRM and files through one unified API
SDKs, a CLI and MCP access to over a thousand prebuilt SaaS integrations for agents, with auth and per-user sessions
Microsoft Power Platform MCP server with 312 tools for flows, apps, Dataverse and Power Pages, driven in plain language.
Zapier's official MCP plugin: the agent gets actions across thousands of apps through your Zapier account
An MCP server for driving Windows: the agent opens apps, clicks and types, reads window and UI state, and works with files and PowerShell
SeldonFrame MCP server and plugin: an agent builds a client site, booking flow, CRM and AI agent from one request
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Prism MCP: work with Prismatic from your agent (this card) | yes | key is optional | 27 | |
| n8n-MCP | no | key is optional | 23,252 | builds n8n workflows, while this one works with Prismatic integrations for B2B SaaS |
| Composio | no | 31,051 | a ready set of third-party connections for the agent, with no building of customer-facing integrations |
README in short
The README covers setup for Claude Desktop, Claude Code, Cursor and VS Code with GitHub Copilot, links one-click installs for Cursor and VS Code, and introduces the Prismatic platform. The repository is MIT licensed.