A Model Context Protocol server for managing prompts via stdio.
Promptregistry mcp mcp server lets Claude, Cursor and other MCP clients work with Promptregistry MCP directly. A Model Context Protocol server for managing prompts via stdio.
PROMPT_REGISTRY_PROJECT_DIR is set, prompts are stored in that directory. 2. If not set, prompts are stored in ~/.promptregistry/ in your home directory. On first startup, or if prompts are missing, the server will attempt to copy predefined prompts from a local default_prompts_data/ directory (if present) into ~/.promptregistry/.Once connected, the assistant can call this tool directly:
Args — * id, content, description (optional), tags (optional), variables (optional), metadata (optional)The server is distributed via npm as @smithery/cli, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.
The server reads one environment variable: PROMPT_REGISTRY_PROJECT_DIR. Keep credentials in your client's env block or a secrets manager rather than committing them.
Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Promptregistry MCP sits in that group, and the shape of its toolset — Args — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| Args | * id, content, description (optional), tags (optional), variables (optional), metadata (optional). |
{
"mcpServers": {
"promptregistry": {
"command": "npx",
"args": ["-y", "@smithery/cli"],
"env": {
"PROMPT_REGISTRY_PROJECT_DIR": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| PROMPT_REGISTRY_PROJECT_DIR | Filesystem location the server is allowed to use. | Optional |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.