promptz.dev MCP Server
Related Servers
Alternatives to promptz.dev MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceProvides access to thousands of AI prompts from prompts.chat, enabling users to search, browse, and use community-curated prompts with variable substitution directly in their AI coding assistant.2283 npm35ISC
- AlicenseBqualityDmaintenanceEnables AI assistants to manage, store, and retrieve prompts through the Model Context Protocol, with a web UI for prompt management and optional secure sharing via Dev Tunnels.1MIT
- AlicenseNot gradedqualityFmaintenanceConnects AI tools to your organization's Haiven prompts, allowing seamless access to expert-crafted prompts for user stories, code reviews, and more without switching apps.Apache 2.0
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI-native prompt management for Latitude.so with full CRUD operations, version control, file-based workflows, and direct prompt execution with streaming support.4 npm-
- AlicenseBqualityDmaintenanceEnables AI models like Claude to manage local prompt files with CRUD operations, fuzzy search, categorization, templates, version control, and favorites.325MIT
- AlicenseAqualityBmaintenanceExposes tools to list and save prompts from the Pretty Prompt library, enabling integration with AI editors like Cursor and Claude Desktop.524 npmMIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: get_prompt retrieves a specific prompt, get_rule retrieves a specific rule, list_prompts lists all prompts, and list_rules lists all rules. There is no overlap or ambiguity between these four operations.
All tool names follow a consistent verb_noun pattern with snake_case (get_prompt, get_rule, list_prompts, list_rules). The naming is perfectly predictable and readable throughout the set.
With 4 tools, the count is reasonable and well-scoped for a prompt management server, covering core retrieval and listing operations. It's slightly lean but appropriate for the apparent scope, lacking only minor gaps like update or delete operations.
The tool set provides good read/list coverage for prompts and rules, but there are notable gaps in CRUD operations. For example, there are no tools for creating, updating, or deleting prompts or rules, which limits full lifecycle management for the domain.