retro-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_EMAIL | Yes | Your Jira account email (required for live mode) | |
| SLACK_TOKEN | No | Slack read token to scan for blocker and incident language | |
| GITHUB_REPOS | No | Comma-separated list of GitHub repos (owner/name) | |
| GITHUB_TOKEN | No | GitHub read-only token for PR review latency and reverts | |
| JIRA_BASE_URL | Yes | Your Jira Cloud base URL (required for live mode) | |
| JIRA_BOARD_ID | No | Optional Jira board ID to pin when account has several | |
| JIRA_API_TOKEN | Yes | Your Jira API token (required for live mode) | |
| SLACK_CHANNELS | No | Comma-separated Slack channel IDs |
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 | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/sathvic-kollu/retro-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server