Best for
- Developers maintaining a personal or team library of prompts and agent templates
- Users of Claude Desktop/Cursor who want prompt management exposed as an MCP tool
- Projects using claude CLI orchestration with specialized subagents
M
MCP Prompts
Community
Local MCP server for storing and serving reusable AI prompts and agent templates.
GitHub source repository ↗
51FMRS · D
README-only review: a straightforward, self-hosted MCP server for prompt CRUD and template expansion, plus a separate shell-script orchestration layer; no license, authentication, or hosted-service details are given beyond what's stated.
MCP Prompts is a Model Context Protocol server for managing, storing, and providing prompts and prompt templates for LLM interactions. It stores prompts as JSON files under data/prompts/ and exposes MCP tools for querying, creating, updating, and deleting them. The project also ships agent templates for project orchestration and an accompanying shell script that drives the local claude CLI to analyze entire projects. It is designed to work with Claude Desktop, Cursor, and other MCP clients.
Tools
list_prompts
Query stored prompts with filters such as tags, search text, or category.
get_prompt
Retrieve a specific prompt and expand its template.
create_prompt
Add a new prompt to the repository.
update_prompt
Modify an existing prompt.
delete_prompt
Remove a prompt from the repository.
apply_template
Apply variables to a template string.
get_stats
Return repository statistics.
Setup
- Run pnpm install to install dependencies. 2. Run pnpm build to compile the TypeScript project. 3. Run pnpm start to launch the MCP server. 4. Add an entry to ~/.claude/mcp.json with command set to node, args pointing to the absolute path of the built dist/mcp-server-standalone.js, and env.PROMPTS_DIR set to the absolute path of data/prompts.
claude_desktop_config.json
{"mcpServers":{"prompts":{"command":"node","args":["/absolute/path/to/mcp-prompts/dist/mcp-server-standalone.js"],"env":{"PROMPTS_DIR":"/absolute/path/to/mcp-prompts/data/prompts"}}}}
Fit and risk
Not for
- Teams needing a hosted/multi-tenant prompt service (enterprise AWS features live in a separate archived module)
- Users wanting database-backed prompt storage (prompts are plain JSON files)
- Non-technical users unfamiliar with configuring MCP client JSON files
Required permissions
- Local filesystem read/write access to the configured PROMPTS_DIR
- Ability to execute the Node.js server process
- The orchestration script additionally invokes the local claude CLI
Risks and side effects
- Prompts and agent templates are stored as plain JSON files with no access control described
- create_prompt/update_prompt/delete_prompt let a connected client modify or remove local files with no confirmation step described in the README
- No authentication mechanism is documented for the stdio server itself
- Enterprise/AWS deployment features exist but are only referenced as archived, without detail in the main README
Troubleshooting
- Confirm PROMPTS_DIR points to the absolute path of data/prompts
- Run pnpm build before pnpm start if dist/mcp-server-standalone.js is missing
- Verify the mcp.json entry uses an absolute path to the built server file
- Check pnpm test / pnpm dev output for build errors
Use cases
Storing and reusing prompt templates across projects
Querying prompts by tag or category from within an MCP client
Orchestrating multi-agent project analysis via the bundled shell script
Supported clients
Claude DesktopFull support
CursorPartial support