promethic-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROMETHIC_API_KEY | Yes | Your Promethic developer key, used as a Bearer token (starts with 'pmk_'). |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_connection_infoB | Return connection details for the hosted Promethic MCP server. |
| get_agents_docs_urlA | Return the Promethic agent setup and client configuration URL. |
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
Each tool has a clearly distinct purpose: one provides connection details, the other provides a documentation URL. There is no overlap or ambiguity between them.
Both tools follow the exact same 'get_' + noun pattern, making the naming perfectly consistent and predictable.
With only 2 tools, the server feels thin but the narrow scope (returning server info) is reasonable. The count sits at the borderline where it is acceptable but not substantial.
For the apparent purpose of providing connection and documentation information, the surface is complete. Minor additions like a status or configuration tool could be imagined, but no obvious gap exists for the stated domain.