Claude Prompts MCP Server

Root package for git hooks and workspace management

Local serverstdioTypeScript

What is the Claude Prompts MCP MCP server?

Most developer tooling work still happens through a UI a human drives. Claude Prompts MCP MCP server moves it into the conversation instead. Root package for git hooks and workspace management.

The short version

Craft reusable prompts with validation and reasoning guidance.

Getting it running

Installation goes through your MCP client rather than a global install: point it at opencode-prompts on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

The tools it exposes

The server publishes 14 tools. What each one is for:

  • macOS — ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows — %APPDATA%\Claude\claude_desktop_config.json
  • prompt — development/review
  • Primitive — Symbol
  • Gate — ::
  • Framework — @
  • Style — #
  • Preset — Tries
  • Hook — Unlocks
  • Auto-routing — >>analyze topic:'X' in chat fires the right MCP tool call without you naming it
  • Symbol — Name
  • prompt_engine — Execute prompts with frameworks and validation

What it needs from you

Configuration is passed through the environment: MCP_RESOURCES_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Claude Prompts MCP.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Claude Prompts MCP's toolset — macOS, Windows, prompt and 11 more — is a fair guide to whether it matches your workflow. It is maintained by minipuft; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Claude Prompts MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
macOS~/Library/Application Support/Claude/claude_desktop_config.json
Windows%APPDATA%\Claude\claude_desktop_config.json
promptdevelopment/review
PrimitiveSymbol
Gate::
Framework@
Style#
PresetTries
HookUnlocks
Auto-routing>>analyze topic:'X' in chat fires the right MCP tool call without you naming it
SymbolName
prompt_engineExecute prompts with frameworks and validation
resource_managerCreate, update, version, and export resources
system_controlStatus, analytics, framework switching

How to install the Claude Prompts MCP MCP server

{
  "mcpServers": {
    "claude-prompts": {
      "command": "npx",
      "args": ["-y", "opencode-prompts"],
      "env": {
        "MCP_RESOURCES_PATH": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
MCP_RESOURCES_PATHFilesystem location the server is allowed to use.Optional

Example prompts to try

  • Use Claude Prompts MCP to macOS.
  • Use Claude Prompts MCP to Windows.
  • Use Claude Prompts MCP to prompt.

Frequently asked questions

It connects Claude Prompts MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (macOS, Windows, prompt, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Claude Prompts MCP directly.