prompts.chat MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROMPTS_QUERY | No | Optional query string to filter prompts (e.g., users=a,b&categories=c,d&tags=e,f) | |
| PROMPTS_API_KEY | No | Optional API key for authenticated requests |
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 |
|---|---|
| search_promptsC | Search for AI prompts by keyword. Returns matching prompts with title, description, content, author, category, and tags. |
| get_promptB | Get a prompt by ID. If the prompt contains template variables (like ${variable} or ${variable:default}), you may need to provide values for them. |
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 2 tools
The two tools have clearly distinct purposes: get_prompt retrieves a specific prompt by ID with potential variable handling, while search_prompts finds multiple prompts by keyword with metadata. There is no overlap or ambiguity between these operations.
Both tools follow a consistent verb_noun pattern (get_prompt, search_prompts) with clear, descriptive names that align with their functions. The naming style is uniform and predictable.
With only two tools, the server feels thin for a prompt management domain. While get and search are fundamental, typical CRUD operations like create, update, or delete prompts are missing, making the set feel incomplete for full prompt lifecycle management.
The toolset is severely incomplete for prompt management. It lacks essential operations such as creating, updating, or deleting prompts, which are core to managing a prompt repository. Agents will hit dead ends when trying to modify or add prompts.