Reusable prompt templates, multi-step workflow chains, and quality gates for any MCP client.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag β we're steadily working through the catalog.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
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
| 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 |
/commands already handle what you need, or you're looking for a no-code prompt library.Load plugin from local source for development:
Edit hooks/prompts β restart Claude Code. Edit TypeScript β rebuild first.
Codex hooks require Codex CLI 0.117 or later and are unavailable on Windows. See the codex-prompts requirements for Python and Node.js prerequisites.
Enable hooks in ~/.codex/config.toml:
Then install the plugin:
Restart Codex, run /hooks to review the plugin hooks, then try >>tech_evaluation_chain library:'zod' context:'API validation'.
Option A: GitHub Release (recommended)
claude-prompts-{version}.mcpb from ReleasesThe .mcpb bundle is self-contained (~5MB); no npm required.
Option B: NPX (auto-updates)
Add to your config file:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonRestart Claude Desktop and test: >>research_chain topic:'remote team policies'
Client setup: VS Code, Cursor, and other MCP-only clients use the manual configuration guide below.
Plugin installers (recommended where available; adds hooks):
Manual config for VS Code, Cursor, OpenCode (no hooks), Gemini CLI (no hooks), Codex (no plugin hooks), Windsurf, and 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):
Point your MCP config to server/dist/index.js. Transport: --transport=stdio (default) or --transport=streamable-http.
Custom resources: --init=~/my-prompts scaffolds a starter workspace: three example prompts plus config.json. 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. See Custom Resources Guide.
Four primitives you author, version, and compose. The bundled set ships 39 prompts across 8 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.
| 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 Β· #procedural |
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.
Everything above reaches your client through three MCP tools:
| Tool | Purpose |
|---|---|
prompt_engine | Execute prompts with frameworks and validation |
resource_manager | Create, update, version, and roll back resources |
system_control | Status, analytics, framework switching |
Factual signals from GitHub, npm, and our automated checks β not a rating.
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/claude-prompts-mcp)<a href="https://allmcps.com/mcp/claude-prompts-mcp"><img src="https://allmcps.com/api/badge/claude-prompts-mcp?style=directory" alt="Claude Prompts MCP on AllMCPs" /></a>