MCP Servers for QA and Release Coordination
by 1olegshev
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_EMAIL | No | Email for Jira authentication | |
| JIRA_BASE_URL | No | Base URL for Jira instance (e.g., https://yourorg.atlassian.net) | |
| JIRA_API_TOKEN | No | API token for Jira authentication | |
| CONFLUENCE_EMAIL | No | Email for Confluence authentication | |
| CONFLUENCE_BASE_URL | No | Base URL for Confluence instance | |
| CONFLUENCE_API_TOKEN | No | API token for Confluence authentication | |
| SLACK_MCP_XOXC_TOKEN | No | Slack session token (xoxc) from browser | |
| SLACK_MCP_XOXD_TOKEN | No | Slack cookie (xoxd) from browser |
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 |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityInactive
ResponsivenessNo issues