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.-
- AlicenseAqualityDmaintenanceEnables storage, versioning, and retrieval of prompts with rich metadata via MCP tools, supporting stdio and SSE transports.37 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
- 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.265 npmMIT
- AlicenseAqualityCmaintenanceLets MCP hosts search the public Image3 GPT Image 2 prompt gallery, fetch complete prompts, list categories, and turn rough ideas into structured prompt briefs.4MIT
- AlicenseNot gradedqualityCmaintenanceA lightweight, file-based server for managing and serving personal prompt templates with variable substitution support via the Model Context Protocol. It allows users to store, update, and organize prompts in a local directory through integrated MCP tools and CLI assistants.6 npm7MIT
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.