promptz.dev MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROMPTZ_API_KEY | Yes | Your API key from promptz.dev | |
| PROMPTZ_API_URL | Yes | Your API URL from promptz.dev |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_promptsC | List available prompts from promptz.dev |
| get_promptC | Get a specific prompt by ID or name |
| list_rulesB | List available project rules from promptz.dev |
| get_ruleC | Get a specific project rule by name |
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 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.