The whole idea is one decision: publish prompts as tools, because that is the list a coding assistant reads. Adding your own is a text file in a folder, which makes it a reasonable place to keep the three or four prompts a team keeps pasting by hand.
A small server that reads prompt templates from a directory and exposes each one as a tool rather than as an MCP prompt - which is what makes them usable in editors like Cursor and Windsurf, where the tools list is the surface that gets used.
- Every YAML or JSON template in the prompts directory offered as a callable tool
- Placeholder substitution, so a template takes named arguments instead of being one fixed block of text
- Templates shipped for code review, API documentation, refactoring, test-case generation and project architecture
- Reloading the whole prompt set without restarting, and listing the names currently available
Node and npm. Clone, run npm install, then npm start; the server speaks over stdin and stdout, so the client launches it with node and the path to src/index.js. Adding a template is dropping a YAML file into src/prompts. The author has moved on to a hosted service and states this repository will not get further feature work.
One command — npx -y mcp-prompt-server