Tempo Filler MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TEMPO_PAT | Yes | Personal Access Token for authentication | |
| TEMPO_BASE_URL | Yes | Your JIRA instance URL (e.g., https://jira.company.com) | |
| TEMPO_DEFAULT_HOURS | No | Default hours per workday (default: 8) |
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_worklogsB | Retrieve worklogs for authenticated user and date range |
| post_worklogA | Create a new worklog entry. For better results, consider using get_schedule first to verify working days and expected hours. |
| bulk_post_worklogsA | Create multiple worklog entries from a structured format. RECOMMENDED: Use get_schedule first to identify working days and avoid logging time on non-working days. |
| delete_worklogC | Delete an existing worklog entry |
| get_scheduleA | Retrieve work schedule for authenticated user and date range |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| worklog_summary | Generate a prompt for analyzing worklog data |
| schedule_aware_bulk_entry | Guide AI assistants through schedule-first bulk worklog creation |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Recent Issues | Recently used issue keys for quick reference |
| Schedule Calendar UI | Visual calendar view for get_schedule tool results |
| Worklogs Timesheet UI | Visual timesheet grid for get_worklogs tool results |
TDQS
Scored across 5 tools
Each tool serves a distinct purpose: get_schedule for schedule, get_worklogs for worklogs, post_worklog and bulk_post_worklogs for creation (single vs. batch), and delete_worklog for deletion. No overlap.
All tool names follow verb_noun pattern in lowercase snake_case (e.g., get_schedule, post_worklog). The naming is uniform and predictable across the set.
With 5 tools, the set is well-scoped for its purpose. It covers essential operations without being too sparse or overwhelming, fitting within the ideal 3-15 range.
The set covers create (single and bulk), read (worklogs and schedule), and delete. However, an update/modify tool is missing, which is a minor gap for full lifecycle management.