That warning is the most useful line in the README: prompts with zero or one argument work in almost every client, but two or more are not universally supported — Cherry Studio and Claude Desktop are named as ones that do. Design around that and this stays a very small, very portable way to keep a prompt library under version control instead of pasted into a dozen settings screens.
A lightweight MCP server that turns a directory of `.md` files into MCP prompts. Each file is a prompt; optional YAML front matter gives it a name, title, description and arguments. Because they are just files in a repository, prompts are versioned, shareable and easy to update across machines and teammates.
- Every `.md` file in the configured directory exposed as a prompt, named by its filename unless front matter overrides it
- Front matter fields — `name`, `title`, `description` and `arguments` — controlling how the prompt is presented to the client
- Arguments declared either as a bare name or as a full object with `description` and `required`
- Placeholders substituted at request time — write `{{arg_name}}` in the body and the value provided by the caller replaces it
- Prebuilt binaries for your platform from GitHub Releases
No account and no key. Download the binary for your platform from the project's GitHub Releases, then add a stdio entry to your client that runs it with `--path=/path/to/prompts`. Claude Desktop and Cherry Studio configurations are both documented. Released under the BSD License.