PromStack MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROMPTSTACK_API_KEY | Yes | Your PromStack API Key (can be obtained from Settings > API Keys) |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_promptsD | – |
| get_promptD | – |
| select_promptD | – |
| export_skillD | – |
| query_contextD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| prompts-list | |
| projects-list |
TDQS
Scored across 5 tools
The tools have distinct names but their purposes are unclear due to missing descriptions, making it hard to assess true overlap. 'list_prompts' and 'select_prompt' might overlap in functionality, while 'query_context' and 'get_prompt' could be ambiguous without context. The lack of descriptions forces reliance on naming alone, which introduces uncertainty.
All tool names follow a consistent verb_noun pattern with snake_case, such as 'export_skill', 'get_prompt', and 'list_prompts'. There are no deviations in naming conventions, making the set predictable and easy to parse for an agent.
With 5 tools, the count is reasonable for a server focused on prompts and skills, as inferred from the names. It's slightly lean but not overly sparse, suggesting a well-scoped set that could cover core operations without being overwhelming.
Inferred domain involves managing prompts and skills, but the tool set lacks clear CRUD coverage—there's no 'create_prompt', 'update_prompt', or 'delete_prompt', and 'export_skill' stands alone without complementary tools. The missing descriptions exacerbate gaps, making it likely agents will encounter dead ends in workflows.