This MCP server provides read-only access to your saved prompts from Keep My Prompts, allowing you to fetch prompts directly within MCP clients (e.g., Claude Desktop, Cursor, VS Code) without copy-pasting. It runs locally and communicates with the Keep My Prompts API over HTTPS, sending your API key as a bearer token (the key is never stored). You can:
List saved prompts (list_prompts): Retrieve titles, categories, and shortened notes for all prompts, with optional category filtering.
Read a specific prompt (get_prompt): Fetch the full text and full notes of a prompt by its ID.
List categories (list_categories): View all your prompt categories with the count of prompts in each.
Note: This server is read-only; it cannot create, edit, or delete prompts.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@keepmyprompts-mcp use my follow-up email prompt"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
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-petal
claude mcp add keepmyprompts -e KMP_API_KEY=kmp_live_... -- npx -y github:simopet/keepmyprompts-mcp#v0.2.0Always 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_..." }
}
}
}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.
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 scriptThen use "command": "node" with "args": ["/absolute/path/to/keepmyprompts-mcp/dist/index.js"].
Variable | Required | Default | Notes |
| yes | — | Your key, starting |
| no |
| Keep the |
The key is read from the environment and sent as a bearer token over HTTPS. It is never written to disk or logged.
Tool | Arguments | What it does |
|
| Titles, categories and your own notes for each saved prompt. Not the prompt text — that keeps the list cheap, and the notes are what let the model tell two similar prompts apart. Long notes are shortened here and shown in full by |
|
| Full text and full notes of one prompt. |
| — | Your categories with a count each, for narrowing a large library. |
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.
What you see | What it means |
| The client started the server without the variable. Check the |
API key is missing, invalid or revoked | The key was deleted or regenerated. Create a new one in Settings. |
plan does not include MCP access | The account is on Free, or a paid plan lapsed. MCP is on Pro, Ultimate and Team. |
Too many requests | More than 60 calls in a minute from one key. It clears within the minute. |
redirected the request (HTTP 301) |
|
bot-protection challenge | Our problem, not yours — please open an issue. |
The tools never appear in the client | Node is older than 20, or the client cached a failed start. Check |
Installation problems are worth reporting even when you work around them: open an issue.
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.
MIT — see LICENSE.
Retrieve the full text of one saved prompt by its id, including any notes. Call this after list_prompts, once you know which prompt you need.
Inputs: id (required).
List the user's prompt categories with how many prompts each contains. Useful for narrowing list_prompts on a large library.
Inputs: no named parameters.
List the titles of the user's saved prompts in Keep My Prompts, with their category. Call this when the user refers to a prompt of theirs, asks what is in their library, or asks you to reuse or adapt something they saved. Returns titles only — call get_prompt for the text of the one you need.
Inputs: category.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 3 tools
Each tool has a clearly distinct purpose: listing titles, fetching full text, and listing categories. There is no overlap in functionality, and the descriptions explicitly guide when to use each.
All tool names follow a consistent verb_noun pattern using snake_case (list_prompts, get_prompt, list_categories). The naming is predictable and readable.
Three tools is well-scoped for a read-only prompt retrieval server. Each tool covers a distinct need without redundancy or bloat.
The server fully covers retrieval and organization of saved prompts, but lacks write operations like create or delete. Given the focus on accessing existing prompts, this is a minor gap that doesn't hinder the core workflow.
Professional prompt library over remote MCP: 13 verticals, free discovery scope.
Read-only MCP server exposing a user ORANO library to their own AI agent.
Read-only search and Markdown access to liz's public docs, prompts, resources, and an MCP App.
Search your Glasp web and Kindle highlights, notes, and AI memories from any MCP client. Read-only.
