Claude Prompts MCP

Claude Prompts

The portable workflow layer beside your AI coding harness.

Your client executes with its own tools, agents, and context.

Claude Prompts adds reusable prompt resources, composable chains, validation gates, and client-native skill export.

Quick Start · What You Get · Compose Workflows · Run Anywhere · Docs

What your AI client gives you — and what this server adds

Is this for me?

• Use this if you write the same prompts repeatedly, run multi-step workflows, or want to share reusable prompts with a team.
• Skip if your client's built-in /commands already handle what you need, or you're looking for a no-code prompt library.
• Works with Claude Code, Claude Desktop, Cursor, VS Code, OpenCode, Gemini CLI, Codex, and Windsurf. Hook coverage differs by client; the client list shows it.

---

Quick Start

Claude Code (Recommended)

/plugin marketplace add minipuft/minipuft-plugins  # first time only

/plugin install claude-prompts@minipuft

>tech_evaluation_chain library:'zod' context:'API validation'

Codex (Experimental)

Turn on hooks in ~/.codex/config.toml, then install the plugin:

[features]

hooks = true

codex plugin marketplace add https://github.com/minipuft/minipuft-plugins.git

codex plugin add codex-prompts@minipuft

Restart Codex, run /hooks to review and trust the plugin hooks, then try the same >>tech_evaluation_chain command. Needs Codex CLI 0.117 or later; not available on Windows (requirements).

---

Every Client

All 8 clients: setup and hook coverage 2 full · 1 experimental · 1 partial · 4 MCP tools only

Hooks are what make >>, -->, and :: work in conversation; "MCP tools only" means the three MCP tools without them. See With Hooks. Config locations and --client presets: Client Capabilities Reference.

Claude Code Plugin

Steps in Quick Start.

OpenCode npm installer

npm install -g opencode-prompts && opencode-prompts install

For MCP tools without hooks, use the manual config in the Client Integration Guide.

Codex Plugin

Steps in Quick Start. Hooks are off by default and need a one-time /hooks trust review.

Gemini CLI Extension

gemini extensions install https://github.com/minipuft/gemini-prompts

For MCP tools without hooks, use the manual config in the Client Integration Guide.

Claude Desktop Desktop bundle or npx config

Option A: GitHub Release (recommended): download claude-prompts-{version}.mcpb from Releases and drag it into Claude Desktop Settings → MCP Servers. The .mcpb bundle is self-contained (~5MB); no npm required.

Option B: NPX (auto-updates): add this to your config file (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json, Windows: %APPDATA%\Claude\claude_desktop_config.json):

{

"mcpServers": { "claude-prompts": { "command": "npx", "args": ["-y", "claude-prompts@latest", "--client", "claude-code"] } } }

Restart Claude Desktop and test: >>research_chain topic:'remote team policies'

Cursor, VS Code, Windsurf MCP config

Cursor and Windsurf (now Devin Desktop) use the same block. Add it to ~/.cursor/mcp.json for Cursor, or to ~/.config/devin/mcp_config.json for Windsurf (Windows: %APPDATA%\devin\mcp_config.json):

{

"mcpServers": { "claude-prompts": { "command": "npx", "args": ["-y", "claude-prompts@latest", "--client=cursor"] } } }

VS Code uses a different shape. Add this to .vscode/mcp.json in your project, or to your user profile's mcp.json:

{

"servers": { "claude-prompts": { "type": "stdio", "command": "npx", "args": ["-y", "claude-prompts@latest", "--client=unknown"] } } }

Restart the client after saving. Presets and verification: Client Integration Guide.

---

What You Get

Four primitives you author, version, and compose. The bundled set ships 52 prompts across 9 categories — a starting library, not the ceiling: your AI writes new prompts and chains through resource_manager as it works, so the set grows around what you actually do. All hot-reloadable, all versioned with rollback.

Prompts, gates, and frameworks are managed through the resource_manager tool. Your AI creates, edits, versions, and rolls them back through MCP, no file editing required. Styles are managed with the bundled cpm CLI. Failed gate checks can retry automatically or pause for your decision (Gates Guide). Build your first primitive: Prompt Authoring Tutorial.

Your own prompts

Your own prompts, gates and frameworks live in a workspace you choose. --init=~/my-prompts scaffolds a starter workspace: three example prompts plus config.jsonc. Edit them (YAML schema), or have your AI author new prompts, gates, and frameworks via resource_manager. Point MCP_RESOURCES_PATH at an existing workspace if you already have one in the right shape. Resources that belong to one repository go in .claude-prompts/ at its root (cpm init --project scaffolds it) and load above your workspace over STDIO. See Custom Resources Guide.

The Three Tools

Everything above reaches your client through three MCP tools:

Most users invoke these via >> syntax in co