keepmyprompts-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KMP_API_KEY | Yes | Your Keep My Prompts API key, starting with kmp_live_. Required; the server exits immediately without it. | |
| KMP_API_URL | No | The base URL of the Keep My Prompts API. Defaults to https://www.keepmyprompts.com. Keep the www.; the bare domain redirects and the request is refused. | https://www.keepmyprompts.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_promptsA | 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. |
| get_promptA | 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. |
| list_categoriesA | List the user's prompt categories with how many prompts each contains. Useful for narrowing list_prompts on a large library. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
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.