MCP.Market

Prism MCP server

by prismatic-io·io.github.prismatic-io/prism-mcp·v1.5.0·26 stars

MCP server that wraps Prismatic's Prism CLI tool

A94/100grade A
What users say
No reviews yet
Be the first
Safety scan
A94/100

full report

Adoption
Growing

26 stars105 downloads/wk

Reviews

Write one

Nobody has reviewed Prism yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Prism tools (19, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • prism_components_generate_manifest

    Generate the type manifest for a Prismatic component to enable its usage within a Code-Native Integration. The component is built with `npm run build` first, and outputDir gets a `<component dir name>-manifest` subfolder appended.

  • prism_components_init

    Initialize a new Prismatic custom component. Passing a WSDL or OpenAPI spec scaffolds the component from that definition.

  • prism_components_list

    List the components available in your organization. Searching for 'http' short-circuits with guidance to build a client via @prismatic-io/spectral's createClient instead of using the HTTP component.

  • prism_components_publishwrite action

    Publish a custom Prismatic component from a specific directory. The directory is built with `npm run build` first and published non-interactively.

  • prism_install_component_manifest

    If using spectral@10.6.0 or greater, generate a manifest in CNI src.

  • prism_install_legacy_component_manifest

    Fallback for when prism_install_component_manifest fails. Generates the devDependencies entry that installs a legacy component manifest.

  • prism_integrations_add_connection_config_var

    Returns the path to a file that contains a connection wrapper function. If not available, generates boilerplate code for a connection config variable.

  • prism_integrations_add_datasource_config_var

    Returns the path to a file that contains a data source wrapper function. If not available, generates boilerplate code for a data source config variable.

  • prism_integrations_convert

    Convert an existing Low-Code Integration into a Code Native Integration, scaffolding the generated code in the working directory

  • prism_integrations_flows_list

    List flows for an integration

  • prism_integrations_flows_listen

    Set a flow to 'Listening Mode,' allowing you to capture webhook payloads or polling trigger responses and save them as payloads to be used by the integrations:flows:test command. For flows using polling triggers, the user should create the events before invoking this tool. For flows using webhook triggers, the user creates the event while you listen. Listening runs non-interactively (quiet, no pro

  • prism_integrations_flows_test

    Test a flow in a Prismatic integration. Output is always returned quietly, as JSONL when tailing logs or results.

  • prism_integrations_generate_config_page

    Generate boilerplate code for a CNI config page. The result should be included in the CNI's configPages object.

  • prism_integrations_generate_config_var

    Generate boilerplate code for a config variable. The result should be included in a CNI's existing config page.

  • prism_integrations_generate_flow

    Generate boilerplate file for a CNI flow. The result should be included in the CNI's list of available flows.

  • prism_integrations_import

    Import a Prismatic code-native integration from a specific directory. The directory is built with `npm run build` before importing.

  • prism_integrations_init

    Initialize a new Prismatic Code Native Integration (CNI)

  • prism_integrations_list

    List all integrations in your organization

  • prism_me

    Check Prismatic login status and display current user profile information

Public scan report

scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it

no findings
  • Code scan15 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 5 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 94/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Prism compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
94/100
higher than 96% of 48,255 servers
Tools
19
the typical server has 7
Tools that change things
5%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
26
more than 91% of 28,688 servers
Downloads a week
105
more than 64% of 12,191 servers with a package

What its tools let an agent do: 18 read · 1 change

Install Prism in Claude Code, Cursor or VS Code

Runs npx -y @prismatic-io/prism-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add prism-mcp -- npx -y @prismatic-io/prism-mcp
Add to Cursor

What the publisher says

From the Prism repository's README, as published. We do not edit it. Read it on GitHub

@prismatic-io/prism-mcp

Prism MCP Server is a local Model Context Protocol (MCP) server that helps AI assistants work with the Prismatic API for code-native integration and custom component development.

Agent Skills Also Available

If you're interested in AI-assisted coding, also check out our Claude Plugin, which helps your AI assistant understand the Prismatic ecosystem and provides tools for integration development, component development, and more.

Features

This MCP server provides several tools, organized into categories. You may register whatever set of tools are most relevant to your use case.

General Tools (Always Available)

  • prismme**: Check login status and display current user profile information
  • prismcomponentslist: List all available components with version options

Integration Tools (Toolset: "integration")

Utilities

  • prismintegrationslist: List all integrations
  • prismintegrationsinit: Initialize a new Code Native Integration
  • prismintegrationsconvert: Convert an existing Low-Code Integration to Code Native
  • prismintegrationsflowslist**: List flows for an integration
  • prismintegrationsflowstest**: Test a flow in an integration
  • prismintegrationsflowslisten: Set a flow to "Listening Mode" to capture webhook payloads or polling trigger responses, saving them as payloads for prismintegrationsflowstest
  • prismintegrationsimport: Import an integration from a specific directory

Codegen

  • prisminstallcomponentmanifest**: Generate component manifest in CNI src directory (requires spectral@10.6.0 or greater)
  • prisminstalllegacycomponentmanifest: Generate line to add to a CNI's devDependencies for legacy component manifest installation
  • prismintegrationsgenerateflow**: Generate boilerplate file for a CNI flow
  • prismintegrationsgenerateconfigpage: Generate boilerplate code for a CNI config page
  • prismintegrationsgenerateconfigvar: Generate boilerplate code for a config variable
  • prismintegrationsaddconnectionconfigvar**: Returns path to connection wrapper function if available, otherwise generates boilerplate code for a connection config variable
  • prismintegrationsadddatasourceconfigvar**: Returns path to datasource wrapper function if available, otherwise generates boilerplate code for a datasource config variable

Component Tools (Toolset: "component")

  • prismcomponentsinit: Initialize a new Component (supports WSDL/OpenAPI generation)
  • prismcomponentspublish: Publish a component from a specific directory
  • prismcomponentsgeneratemanifest**: Generate the manifest for a Prismatic component

Toolset Configuration

Tools are organized into toolsets, selected by passing their names as arguments after the working directory (see Command-line arguments):

  • integration - Enables all integration-related tools
  • component - Enables all component-related tools
  • General tools are always available regardless of toolset configuration

If no toolset arguments are passed, all tools are registered by default. Naming an unrecognized toolset is a startup error.

Prerequisites

Authenticate with Prismatic. The server bundles its own pinned copy of the Prism CLI, so you don't need to install one for the server to use — but you do need to be logged in. Install the CLI to run the login command (it writes credentials to a shared config file the server reads automatically), or in headless/CI environments set PRISMREFRESHTOKEN instead.

npm install --global @prismatic-io/prism
prism login

Usage

Configuration

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Prism: common questions

Is Prism MCP server safe?
Yes, by our scan: it is graded A (94/100). Read the Prism safety report
How do I install Prism?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Prism need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Prism maintained?
The last commit was 44 days ago (2026-09-21). The latest release is v1.5.0.
How does Prism compare with other MCP servers?
safety score 94/100 (higher than 96% of 48,255 servers); tools 19 (the typical server has 7); tools that change things 5% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.