tempo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_EMAIL | Yes | Your Jira email address used to resolve issue keys to numeric issue IDs. | |
| JIRA_BASE_URL | Yes | The base URL of your Jira instance, e.g. https://your-domain.atlassian.net | |
| JIRA_API_TOKEN | Yes | Jira API token used with JIRA_EMAIL to resolve issue keys. Generate at https://id.atlassian.com/manage-profile/security/api-tokens. | |
| TEMPO_API_TOKEN | Yes | Generated in Jira under Tempo → Settings → API Integration, scoped to Manage Worklogs. |
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 |
|---|---|
| get_worklogsA | Fetch Tempo worklogs, optionally filtered by Jira issue key, author account ID, and/or date range. |
| post_worklogB | Log time in Tempo against a Jira issue on behalf of a given Jira account. |
| delete_worklogA | Delete a Tempo worklog by its Tempo worklog ID. |
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 3 tools
Each tool targets a distinct operation on worklogs: create (post), read (get), and delete. There is no overlap or ambiguity between them.
All tool names follow the verb_noun pattern with clear verbs (post, get, delete) and the same noun base (worklog(s)). The plural in get_worklogs is semantically appropriate for fetching multiple records.
Three tools is a well-scoped set for a focused worklog integration. Each tool covers an essential action without unnecessary bloat.
The set covers create, read, and delete but lacks an update operation, which is a notable gap for worklog management. Agents must work around this by deleting and recreating worklogs, which is not always desirable.