Keep My Prompts — MCP server

Read your saved Keep My Prompts library from Claude Code, Claude Desktop, Cursor, or any other MCP client. Ask for a prompt by name and the model fetches it; no copy-pasting from a browser tab.

Read-only: this server can list and read your prompts. It cannot create, edit or delete anything.

Requirements

• Node.js 20 or newer (node --version)

• A Keep My Prompts account on a plan that includes MCP access: Pro, Ultimate, or any Team plan

• An API key from Keep My Prompts → Settings → MCP

Related MCP server: Prompt Registry MCP

Install

claude mcp add keepmyprompts -e KMP_API_KEY=kmp_live_... -- npx -y github:simopet/keepmyprompts-mcp#v0.2.0

Always install from a version tag (#v0.2.0), never from the bare repo name. Without a tag your client silently picks up whatever landed on the default branch since you installed, with no way to go back.

For Claude Desktop or Cursor, add this to the MCP servers section of the client's config file instead:

{
  "mcpServers": {
    "keepmyprompts": {
      "command": "npx",
      "args": ["-y", "github:simopet/keepmyprompts-mcp#v0.2.0"],
      "env": { "KMP_API_KEY": "kmp_live_..." }
    }
  }
}

Other MCP clients

Any client that can run local (stdio) MCP servers works: VS Code with GitHub Copilot, Windsurf, Zed, Cline, Continue, Gemini CLI, Codex CLI, and others. The configuration is the same three values everywhere — command: "npx", the args above, and KMP_API_KEY in the environment; only the name and location of the config file differ, so check your client's MCP documentation.

What does not work: browser-only hosts, such as claude.ai on the web or ChatGPT on the web, connect only to remote MCP servers. This server is local by design — it runs on your machine and nowhere else.

Install from a local clone

npx re-resolves the package each time your client starts a session. If you'd rather pay that cost once, clone and point the client at the built file:

git clone https://github.com/simopet/keepmyprompts-mcp.git
cd keepmyprompts-mcp
npm install          # also builds, via the prepare script

Then use "command": "node" with "args": ["/absolute/path/to/keepmyprompts-mcp/dist/index.js"].

Configuration

The key is read from the environment and sent as a bearer token over HTTPS. It is never written to disk or logged.

Tools

Write useful notes. The notes field is what the model reads when deciding which of your prompts fits the task. "For cold outreach to agencies, keep it under 120 words" earns its keep; an empty notes field leaves the model guessing from the title alone.

Ask in plain language — "use my follow-up email prompt", "what prompts do I have for code review" — and the model picks the tool.

Troubleshooting

Installation problems are worth reporting even when you work around them: open an issue.

How it works

Your prompts are encrypted at rest. This server never holds the encryption key — it makes authenticated HTTPS requests to /api/mcp/v1/*, and the Keep My Prompts API decrypts server-side exactly as it does for the web app. The server runs locally on your machine over stdio and talks to nothing except the API.

Licence

MIT — see LICENSE.