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) |
Capabilities
Features and capabilities supported by this server
| 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 |
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/TRANZACT/tempo-filler-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server