Panaya MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PANAYA_TOKEN | Yes | The Panaya API token. | |
| PANAYA_BASE_URL | Yes | The base URL of the Panaya host. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| panaya_authB | Refresh the Panaya generated API token |
| panaya_operationsC | Discover and execute any Panaya Swagger operation by operationId |
| panaya_projectsD | Unified tool for projects operations |
| panaya_requirementsD | Unified tool for requirements operations |
| panaya_testsD | Unified tool for tests operations |
| panaya_defectsD | Unified tool for defects operations |
| panaya_releasesD | Unified tool for releases operations |
| panaya_cyclesD | Unified tool for cycles operations |
| panaya_businessProcessesD | Unified tool for businessProcesses operations |
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 9 tools
The generic panaya_operations tool overlaps with all resource-specific tools, as it can execute any operation. This makes it unclear whether to use a specific tool or the generic one, especially since the 'unified' tools likely wrap similar operations.
Most tools follow a consistent panaya_<resource> pattern with snake_case. However, panaya_businessProcesses uses camelCase, and panaya_operations is not a resource but a catch-all, so it deviates slightly from the naming convention.
With 9 tools, the count is reasonable for a domain-specific server. The inclusion of a generic operations tool alongside resource-specific tools is somewhat redundant but does not make the count inappropriate.
The resource-specific tools cover core entities, and panaya_operations fills any gaps by allowing arbitrary operations. Minor gaps may exist in the specific tools (e.g., no explicit update/delete exposed), but the generic tool provides a workaround.