Claude Prompts MCP Server
An MCP workflow server.
Craft reusable prompts with validation and reasoning guidance. Orchestrate agentic workflows with a composable operator syntax. Export as native skills.
Quick Start · What You Get · Compose Workflows · Run Anywhere · Docs
What your AI client gives you — and what this server adds
| Your client already does | This server adds |
|---|---|
| Run a prompt | Compose prompts with validation, reasoning guidance, and formatting in one expression |
| Single-shot skills | Multi-step workflows that thread context between steps |
| Execute subagents | Hand off mid-chain steps to agents with full workflow context |
| Client-native skill format | Author once as YAML, export to any client with skills:export |
| Manual prompt writing | Versioned templates with hot-reload, rollback, and history |
| Trust the output | Validate output between steps — self-evaluation and shell commands |
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
/commandsalready handle what you need, or you're looking for a no-code prompt library. - Works with Claude Code, Claude Desktop, Cursor, OpenCode, Gemini CLI, Codex, Windsurf, and Zed. Plugin installers add hooks (chain tracking, gate enforcement, state preservation) for Claude Code, OpenCode, and Gemini CLI; other clients run MCP-only.
How to write a chain
>>review target:'src/auth/' @ReACT :: 'cite sources'
--> security_scan :: verify:"npm test"
==> implementation
Read top-to-bottom:
>>review target:'src/auth/'runs thereviewprompt against your auth folder.@ReACToverlays the ReACT reasoning framework on this step.:: 'cite sources'adds a gate the AI must satisfy (cite sources, or retry).--> security_scan :: verify:"npm test"chains to step 2, which must passnpm testbefore producing output.==> implementationhands the final step off to a client-native agent (a subagent in Claude Code).
Validation runs between steps, not only at the end. For the full operator set including *, %, and #, see the Syntax Reference details block near the bottom.
Chain + gate validation in action (haiku model) — gates catch errors and guide self-correction, even on the cheapest model
Quick Start
Claude Code (Recommended)
# Add marketplace (first time only)
/plugin marketplace add minipuft/minipuft-plugins
# Install
/plugin install claude-prompts@minipuft
# Try it
>>tech_evaluation_chain library:'zod' context:'API validation'
Load plugin from local source for development:
git clone https://github.com/minipuft/claude-prompts ~/Applications/claude-prompts
cd ~/Applications/claude-prompts/server && npm install && npm run build
claude --plugin-dir ~/Applications/claude-prompts
Edit hooks/prompts → restart Claude Code. Edit TypeScript → rebuild first.
Claude Desktop
Option A: GitHub Release (recommended)
- Download
claude-prompts-{version}.mcpbfrom Releases - Drag into Claude Desktop Settings → MCP Servers
- Done
The .mcpb bundle is self-contained (~5MB); no npm required.
Option B: NPX (auto-updates)
Add 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'
One-click install:
Plugin installers (recommended, adds hooks):
# OpenCode (full hooks)
npm install -g opencode-prompts && opencode-prompts install
# Gemini CLI (partial hooks)
gemini extensions install https://github.com/minipuft/gemini-prompts
Manual config for VS Code, Cursor, OpenCode (no hooks), Gemini CLI (no hooks), Codex, Windsurf, Zed: see Client Integration Guide for per-client config locations, JSON examples, and --client preset matrix. Client Capabilities Reference covers profile mapping and limits.
From source (developers):
git clone https://github.com/minipuft/claude-prompts.git
cd claude-prompts/server && npm install && npm run build && npm test
Point your MCP config to server/dist/index.js. Transport: --transport=stdio (default) or --transport=streamable-http.
Custom resources: --init=~/my-prompts scaffolds a workspace of prompts, gates, frameworks, and styles. Edit the starter templates (YAML schema), or have your AI author new ones via resource_manager. Point MCP_RESOURCES_PATH at an existing workspace if you already have one in the right shape. See Custom Resources Guide.
What You Get
Four primitives you author, version, and compose. The bundled set ships 90+ prompts across 11 categories. All hot-reloadable, all versioned with rollback.
| Primitive | Symbol | What it is | Example |
|---|---|---|---|
| Prompt template | >> |
Versioned YAML with named arguments; hot-reload on save | >>code_review target:'src/auth/' |
| Gate | :: |
Validation criterion the AI checks its own output against; blocking or advisory; can shell-verify | :: 'cite sources' · :: verify:"npm test" |
| Framework | @ |
Reasoning framework that shapes how the AI works through the problem; plug in your own or use built-ins like @ReACT, @5W1H, or the project's own @CAGEERF scaffold (Frameworks Guide) |
@ReACT · @your_framework |
| Style | # |
Output formatting and tone | #analytical · #concise |
All four are managed through the resource_manager tool. Your AI creates, edits, versions, and rolls back resources through MCP; no file editing required. Failed gate checks can retry automatically or pause for your decision (Gates Guide). Build your first primitive: Prompt Authoring Tutorial.
Compose Workflows
The basic chain syntax is in How to write a chain at the top. Two patterns extend it. Chains also support conditional branching, context threading, and agent handoffs — see Chains Lifecycle and MCP Tools Reference.
<img src="assets/demos/chain-workflow-demo.gif" alt="T