LABSCO SUMMARY

Tells you which clients can actually use multi-argument prompts.

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.

What it is

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.

What you get

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

Requirements

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.

Setup effort

Follow the published steps — Download the binary for your platform from GitHub Releases.

See installation options

USE CASES

Getting your prompt library off your clipboard

Put the .md files in a repository and point the server at the directory, so the same prompts follow you between machines.

Sharing prompts with a team

Commit them to a shared repo; everyone points their client at their checkout and pulls to update.

Making one prompt cover several cases

Declare a required argument in front matter and reference it as a placeholder in the body.

Keeping a prompt usable in every client

Keep it to one argument, since prompts with two or more are not supported everywhere.

INSTALLATION

Connect your client

Server setup

Download the binary for your platform from GitHub Releases.

Create a .md file in your prompts directory, for example greet.md, with optional YAML front matter between --- lines (such as description and arguments) followed by the prompt text, with <YOUR_NAME> where an argument's value should go.

Add the following to your MCP client configuration (stdio transport): the mcpServers JSON block, pointing command at the downloaded binary and --path at the prompts directory.

Claude Desktop only: Edit the claude_desktop_config.json file, add the block from the Claude Desktop tab below to the file, then restart Claude Desktop.

MCP Clients

Claude Desktop, Cherry Studio

JSON

{
  "mcpServers": {
    "my-prompts-mcp": {
      "command": "<YOUR_PATH_TO_PROMPTS_MCP>",
      "args": [
        "--path=<YOUR_PATH_TO_PROMPTS>"
      ]
    }
  }
}

My Prompts MCP