Labsco
MCP SERVER

Prompt MCP Server for Amazon Q

by peepeepopapapeepeepo ↗

Turn a folder of markdown files into prompts Amazon Q can list and use — with file changes detected live and the prompt list refreshed without a restart.

Prompts, Skills & Instruction Packs
Summary
Prompts as files, watched — so editing one is the whole workflow.

The live monitoring is what makes this more than a loader. Saving a markdown file and having it immediately available in the CLI turns prompt work into ordinary editing, and the notification means you are not restarting a session to pick up a fix. Because prompts are just files in directories you name, they version-control and share like anything else in a repository. It is built for Amazon Q's CLI specifically, and it exposes prompts rather than tools — which is the right shape for what it does.

What it is

A single-file MCP server for the Amazon Q Developer CLI that serves your `*.md` files as MCP prompts. It watches the configured directories, so adding, editing or deleting a prompt file updates what Q offers without restarting anything. It exposes prompts rather than tools — the prompt list and prompt fetch are the whole protocol surface.

What you get
  • Every `*.md` file in the configured directories offered as a prompt, listed in the CLI with `/prompts` and used by name
  • Placeholder substitution: write `{variable}` in the file and supply values when the prompt is fetched, so one file covers a family of requests
  • Live file monitoring with an MCP notification sent when the list changes, so Q refreshes on its own
  • Directories you choose, PATH-style: `PROMPTS_PATH` takes a colon-separated list on Unix and semicolons on Windows, defaulting to the Amazon Q prompts directory, which is created for you
  • Debug logging when you need it: `MCP_DEBUG_LOGGING` turns on full request and response tracing to a log file you can tail, with `MCP_LOG_FILE` choosing the path — off by default, and `MCP_LOG_LEVEL` sits at `WARNING` otherwise
Requirements

No account and no key — it reads local files. Pure Python with no external dependencies. Run it with `uvx prompt-mcp-server`, or point the client's command at the server script directly; the published configuration uses uvx with the package pinned to latest. The pyproject name is `prompt-mcp-server` (2.0.9). You can check it outside the CLI by piping a JSON-RPC request into the script — `prompts/list` returns the catalogue and `prompts/get` returns one prompt with its arguments filled in.

Setup effort

One command — uvx prompt-mcp-server