MCP server for managing Tempo worklogs in Jira
MCP server for managing Tempo worklogs in Jira
A Model Context Protocol (MCP) server for managing Tempo worklogs in Jira. This server provides tools for tracking time and managing worklogs through Tempo's API, making it accessible through Claude, Cursor and other MCP-compatible clients.
npm locally — only used for wrangler CLI; the Worker runtime itself doesn't run Node.Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| retrieveWorklogs | Fetches worklogs for the configured user (or other users via filters) between start and end dates. |
| createWorklog | |
| bulkCreateWorklogs | |
| editWorklog | |
| deleteWorklog | |
| getMissingWorklogDays | Reports working days in a date range where the user has logged less time than expected. Expected hours per day come from the user's Tempo schedule, so holidays, non-working days, and part-time schedules are honoured auto |
| getWorklogAnalytics | Aggregates worklogs in a date range and returns hours, worklog count, and percentage per group, sorted by hours descending. Combine groupBy: "user" with program / team / users for a per-person report. |
{
"mcpServers": {
"Jira_Tempo": {
"command": "npx",
"args": ["-y", "@ivelin-web/tempo-mcp-server"],
"env": {
"TEMPO_API_TOKEN": "your_tempo_api_token_here",
"JIRA_API_TOKEN": "your_jira_api_token_here",
"JIRA_EMAIL": "your_email@example.com",
"JIRA_BASE_URL": "https://your-org.atlassian.net"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
npm locally — only used for wrangler CLI; the Worker runtime itself doesn't run Node.| Variable | Description | Required |
|---|---|---|
| TEMPO_API_TOKEN | Credential the server authenticates with. | Yes |
| JIRA_API_TOKEN | Credential the server authenticates with. | Yes |
| JIRA_EMAIL | Configuration value read at startup. | Optional |
| JIRA_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| JIRA_AUTH_TYPE | Configuration value read at startup. | Optional |
| JIRA_OAUTH_CLIENT_ID | Configuration value read at startup. | Optional |
| JIRA_OAUTH_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| ENCRYPTION_KEY | Credential the server authenticates with. | Yes |
Store entities, relations and observations in a local knowledge graph with the reference Memory MCP server.
Connect the Notion MCP server to search workspace content and work with pages and databases through Notion’s hosted OAuth service.
SendPulse MCP Server implements the Model Context Protocol (MCP) as a remote server operating over Streamable HTTP Transport.
A Model Context Protocol (MCP) server implementation for the HubSpot API, providing a standardized interface for accessing and managing CRM data.
A powerful Model Context Protocol (MCP) server for natural language interaction with your Obsidian vault. Built with TypeScript and designed for seamless integration with Claude Code and other MCP…
AI-native task management platform with 52+ MCP tools for multi-agent collaboration.