Claude Prompts

Download the `.mcpb` bundle from the GitHub Releases page and drag it into Claude Desktop under Settings → MCP Servers. This is the fastest way to get started with no CLI required.

Add the server to your `claude_desktop_config.json` to use the auto-updating npm package. The `--client` flag tells the server which client is calling it.

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

Create your own workspace where you can write and version-control YAML prompt templates. This command scaffolds the directory structure.

npx -y claude-prompts@latest --init=~/my-prompts

Configure the server to use your custom prompts directory by setting MCP_RESOURCES_PATH or MCP_WORKSPACE in the env block of your MCP config.

export MCP_RESOURCES_PATH=/path/to/your/resources
export MCP_WORKSPACE=/path/to/my-prompts

Create a `.yaml` file in your prompts directory. The file is picked up automatically without restarting the server — hot-reload is built in.

# ~/my-prompts/prompts/code_review.yaml
name: code_review
description: Review code for quality and security issues
template: |
  Review the following code for {{target}}:
  - Check for security vulnerabilities
  - Identify performance issues
  - Suggest improvements

In Claude, trigger a prompt template using the `>>` operator followed by the template name and parameters. Chain multiple steps with `-->` or add validation gates with `::`.

>>code_review target:'src/auth.ts' :: 'flag all SQL injection risks'