Tempo MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_EMAIL | Yes | Jira account email | |
| DEFAULT_ROLE | No | Default role for worklogs | Dev |
| JIRA_BASE_URL | Yes | Jira base URL (e.g., https://company.atlassian.net) | |
| JIRA_API_TOKEN | Yes | Jira API token (get from id.atlassian.com/manage-profile/security/api-tokens) | |
| TEMPO_API_TOKEN | Yes | Tempo API token (get from Tempo > Settings > API Integration) | |
| DEFAULT_PROJECTS_DIR | No | Default directory for git repos (e.g., C:/Users/you/Projects) | |
| JIRA_ACCOUNT_FIELD_ID | No | Custom field ID for Tempo account | 10026 |
| DEFAULT_MONDAY_MEETING_ISSUE | No | Jira issue for Monday team meeting | BS-14 |
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