The portable workflow layer beside your AI coding harness.
Quick Start · What You Get · Compose Workflows · Run Anywhere · Docs
에이전트 강화
게시자의 자체 명령입니다. PlugMCP 엔드포인트가 아닙니다.
Host a copy with our keys and logs.
npx -y [email protected]Claude Code에는 로컬 명령용 설치 링크가 없습니다. 아래 명령을 복사해 터미널에서 실행합니다.
claude mcp add minipuft-claude-prompts-mcp -- npx -y claude-prompts@4.0.1터미널에서 실행합니다.
{ "mcpServers": { "minipuft-claude-prompts-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
원격 URL인가요, 내 컴퓨터에서 실행하는 명령인가요? 두 설치 방식의 차이
PlugMCP에서 실행
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
실행게시자 제공
The portable workflow layer beside your AI coding harness.
Quick Start · What You Get · Compose Workflows · Run Anywhere · Docs
MCP server for reusable prompt templates, multi-step workflow chains, and quality gates. Compose agentic workflows with an operator syntax; export as native skills to Claude Code, Cursor, OpenCode, and Gemini CLI.
/commands already handle what you need, or you're looking for a no-code prompt library.# 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-mcp ~/Applications/claude-prompts-mcp
cd ~/Applications/claude-prompts-mcp/server && npm install && npm run build
claude --plugin-dir ~/Applications/claude-prompts-mcp
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:
[features]
hooks = true
Then install the plugin:
codex plugin marketplace add https://github.com/minipuft/minipuft-plugins.git
codex plugin add codex-prompts@minipuft
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.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'
Client setup: VS Code, Cursor, and other MCP-only clients use the manual configuration guide below.
Plugin installers (recommended where available; 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 (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):
git clone https://github.com/minipuft/claude-prompts-mcp.git
cd claude-prompts-mcp/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 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. See Custom Resources Guide.
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.
Everything above reaches your client through three MCP tools:
Most users invoke these via >> syntax in conversation; hooks construct the actual calls. For programmatic MCP clients calling tools directly, see MCP Tools Reference.
>>review target:'src/auth/' @ReACT :: 'cite sources'
--> security_scan :: verify:"npm test"
==> implementation
Read top-to-bottom:
>>review target:'src/auth/' runs the review prompt against your auth folder.@ReACT overlays 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 pass npm test before producing output.==> implementation hands the final step off to a client-native agent (a subagent in Claude Code).review ships with the server; security_scan and implementation stand in for prompts you write.
Validation runs between steps, not only at the end. For the full operator grammar and examples, see MCP Tools Reference.
A gate catches a missing field, the model corrects itself, and the chain passes. Recorded on haiku, the cheapest model.
Two patterns extend the basic syntax. Chains also support context threading between steps and agent handoffs. See Chains Lifecycle and MCP Tools Reference.
Context7 fetches live library docs mid-chain. The final output is a structured assessment with sources.
Ground-truth validation via shell commands. The AI keeps iterating until tests pass:
>>implement-feature :: verify:"npm test" loop:true
Implements, runs the test, reads failures, fixes, retries. Spawns a fresh context after repeated failures to avoid context rot.
implement-feature stands for your own prompt: :: verify attaches to any of them.
For autonomous test-fix cycles with context-rot prevention: Ralph Loops Guide.
Let the AI pick the right resources for the task:
%judge Help me refactor this authentication module
Analyzes available templates, reasoning frameworks, validation rules, and styles, then recommends the best combination. You confirm before it runs. For scoring and overrides see Judge Mode Guide.
Author workflows as YAML templates. Export as native skills to your client.
# skills-sync.yaml — choose what to export
registrations:
claude-code:
user:
- prompt:development/review
- prompt:development/validate_work
npm run skills:export
The review prompt becomes a /review Claude Code skill. validate_work becomes /validate_work. Same source, native experience; no MCP call required at runtime.
Compiles to native skill packages for Claude Code, Cursor, Codex and OpenCode. npm run skills:diff flags when exports drift from source. Configuration, supported clients, and drift detection: Skills Sync Guide.
Without hooks, you're calling the three MCP tools explicitly (the LLM constructs each call). With hooks, the operators work in conversation: >>, -->, ==>, :: feel native rather than mediated, and workflow state survives across LLM turns and context compaction.
What hooks unlock:
Hooks ship with the plugin install. Full support on Claude Code (this repo) and OpenCode; partial on Gemini CLI; experimental on Codex, where Codex hooks are off by default and each install requires a one-time /hooks trust review. Other clients get the three MCP tools but no hook-driven behaviors. Detail: hooks/README.md.
Command with operators → server parses and injects resources (framework, gates, style) → client executes the rendered prompt and self-evaluates against the gates → router decides: next step on pass, retry on fail, return on done.
Full request lifecycle, pipeline stages, and subsystem diagrams: Architecture Overview.
Choose a guide based on what you want to do: learn by building, complete a task, look up syntax, or understand the design.
Quick jumps: Build your first prompt · Chains lifecycle · MCP Tools reference · Architecture overview · Troubleshooting
cd server
npm install
npm run build # esbuild bundles to dist/index.js
npm test # Run test suite
npm run validate:all # Full CI validation
The build produces a self-contained bundle. server/dist/ is gitignored, and CI builds fresh from source.
See CONTRIBUTING.md for workflow details.
MCP server for reusable prompt templates, multi-step workflow chains, and quality gates. Compose agentic workflows with an operator syntax; export as native skills to Claude Code, Cursor, OpenCode, an
{ "mcpServers": { "minipuft-claude-prompts-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}개요
MCP server for reusable prompt templates, multi-step workflow chains, and quality gates. Compose agentic workflows with an operator syntax; export as native skills to Claude Code, Cursor, OpenCode, and Gemini CLI.
도구
아직 도구 목록이 없습니다. 원격 서버는 첫 상태 확인 후에 도구 목록이 생깁니다.
FAQ
이 페이지에서 Cursor, Claude Desktop, Claude Code 또는 VS Code용 stdio 설정을 복사합니다. PlugMCP 프록시가 아니라 게시자의 설치 방식을 사용합니다.
이 레코드에는 필수 환경 변수가 등록되어 있지 않습니다.
Claude Prompts은(는) stdio를 통해 로컬에서 실행됩니다.
마지막 확인: 2026-11-17. MCP server for reusable prompt templates, multi-step workflow chains, and quality gates. Compose agentic workflows with an operator syntax; export as native skills to Claude Code, Cursor, OpenCode, and Gemini CLI.