prismatic-skills MCP — Use Cases, Install & Live Demo

Why use it

Key features

First-party — published by Prismatic.io
Covers code-native integrations (TypeScript)
Connector scaffolding and action patterns
Local dev loop with Prismatic SDK
Deploy to Prismatic platform

Live Demo

What it looks like in practice

prismatic-skill.replay ▶ ready

0/0

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "prismatic-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/prismatic-io/prismatic-skills",
        "~/.claude/skills/prismatic-skills"
      ],
      "_inferred": true
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "prismatic-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/prismatic-io/prismatic-skills",
        "~/.claude/skills/prismatic-skills"
      ],
      "_inferred": true
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "prismatic-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/prismatic-io/prismatic-skills",
        "~/.claude/skills/prismatic-skills"
      ],
      "_inferred": true
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "prismatic-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/prismatic-io/prismatic-skills",
        "~/.claude/skills/prismatic-skills"
      ],
      "_inferred": true
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "prismatic-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/prismatic-io/prismatic-skills",
        "~/.claude/skills/prismatic-skills"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json

{
  "context_servers": {
    "prismatic-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/prismatic-io/prismatic-skills",
          "~/.claude/skills/prismatic-skills"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add prismatic-skill -- git clone https://github.com/prismatic-io/prismatic-skills ~/.claude/skills/prismatic-skills

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use prismatic-skills

Build a custom Prismatic connector for an internal API

👤 Integration engineers on teams using Prismatic ⏱ ~90 min advanced

When to use: You have an internal API that your Prismatic flows need to talk to.

Prerequisites

Prismatic account + SDK — npm i -g @prismatic-io/prism; prism login
Skill installed — git clone https://github.com/prismatic-io/prismatic-skills ~/.claude/skills/prismatic-skills

Flow

Scaffold the connector

Use prismatic-skills. Scaffold a connector for our Orders API — base URL, bearer auth, actions for list, get, create.✓ Copied

→ Connector directory with TS entry points, manifest, test files
Implement actions

Fill in the listOrders action with pagination and error handling.✓ Copied

→ TS implementation with types and Prismatic input/output conventions
Test locally

Run the test harness with a mock response.✓ Copied

→ prism tests output; green

Outcome: A deployable connector with actions your flows can use.

Pitfalls

Missing input validation — Prismatic validates at the platform boundary; still use Zod or similar for runtime safety

Combine with: filesystem

Add a new action to an existing Prismatic connector

👤 Maintainers of deployed connectors ⏱ ~30 min intermediate

When to use: Business needs a new action (e.g., refund flow) on an existing integration.

Flow

Identify the pattern

Use prismatic-skills. Look at the existing actions/ and mimic the pattern for a new 'refundOrder' action.✓ Copied

→ Action file consistent with existing style
Publish

Bump the connector version and deploy.✓ Copied

→ prism integrations:publish succeeded

Outcome: Connector updated without breaking existing flows.

Pitfalls

Breaking input schema without version bump — Version the connector; old flows pin to old version until migrated

Combinations

Pair with other MCPs for X10 leverage

prismatic-skill + filesystem

Manage a multi-connector monorepo

Add connectors/widgets-api/ following the same pattern as connectors/users-api/.✓ Copied

prismatic-skill + github

Review connector PRs with skill context

Review this PR against Prismatic connector conventions.✓ Copied

Tools

What this MCP exposes

Tool	Inputs	When to call	Cost
scaffold_connector	name, auth type, actions	New connector	0
write_action	action spec	Per-action implementation	0
run_tests	connector path	Before publish	local
publish_connector	connector path	Deploy	Prismatic deploy

Cost & Limits

What this costs to run

API quota: None in skill
Tokens per call: Moderate
Monetary: Prismatic plan applies; skill is free
Tip: Test locally with the SDK before pushing to reduce deploy churn.

Security

Permissions, secrets, blast radius

Credential storage: Prismatic credentials via prism CLI (not stored in skill)

Data egress: Prismatic platform + whatever APIs your connectors talk to

Connector code runs on the Prismatic platform — don't embed secrets; use Prismatic's credential store.

Troubleshooting

Common errors and fixes

prism login fails

Token scope or expiry; re-login via browser flow

Verify: prism me

Connector publishes but flows can't see new action

Customers may need to upgrade connector version in their flow settings

Input schema rejected

Prismatic enforces specific input shapes; consult their docs or the skill's action templates

Alternatives

prismatic-skills vs others

Alternative	When to use it instead	Tradeoff
Prismatic low-code UI	Simple integrations, no custom code needed	Less flexibility; not versioned in git
Raw Prismatic SDK without skill	You already know the SDK well	Less guided scaffolding

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills