keepmyprompts-mcp
Related Servers
Alternatives to keepmyprompts-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables users to search, browse, and retrieve AI prompts from the Tripleshot public API. Provides access to community prompts, trending content, and template rendering capabilities through a durable MCP server interface.-
- AlicenseNot gradedqualityCmaintenanceEnables AI applications to access and manage your saved Prompt Petal prompts, allowing you to list, use, add, and improve them from any MCP client.MIT
- AlicenseAqualityDmaintenanceEnables storage, versioning, and retrieval of prompts with rich metadata via MCP tools, supporting stdio and SSE transports.317 npm3ISC
- AlicenseNot gradedqualityCmaintenanceEnables users to organize, search, and manage a shared library of prompts across AI tools via the Model Context Protocol. It supports hierarchical folder organization, tagging, and template variable substitution for dynamic prompt generation.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to list, retrieve, compile, create, and update prompts, including managing versions, labels, tags, configuration, and production promotion.MIT
- AlicenseAqualityAmaintenanceYour team's prompt, rules, skills & docs library exposed over MCP (search_library + get_item); mark items "/" and they become slash commands. Free for individuals.258 npmMIT
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.