tempo-filler

Tempo Filler is an MCP server designed to help AI assistants interact with Tempo's time-tracking system within Jira. It exposes tools to get worklogs, fetch scheduling information, and create or bulk-create worklogs, enabling natural-language style prompts to be translated into precise Tempo API calls. The server is designed to render rich visual MCP Apps in compatible hosts (like Claude Desktop or VS Code) as well as provide structured data for CLI hosts. Typical workflows include retrieving worklogs for a date range, inspecting a schedule to identify working days, and automatically creating or updating worklogs on multiple days based on a pattern (for example, filling October hours to match September).

To use it, configure an MCP entry (for example in VS Code or Claude Desktop) with the tempo-filler server. You supply the Tempo Base URL and a Personal Access Token (PAT) as environment variables. Once set up, you can issue natural-language requests such as: get worklogs for a date range, get a schedule for a date range, or bulk-create worklogs for multiple days. The server will execute the appropriate tools (get_worklogs, get_schedule, bulk_post_worklogs) and return data or confirmations in a structured format suitable for AI formatting or visual MCP Apps.

Prerequisites:

• Node.js installed (for npx usage) or a capable runtime that can run npx commands
• Internet access to fetch the MCP server package

1. Install the MCP server via npx (recommended):

• Ensure you have a Tempo instance and PAT ready for environment variables TEMPO_BASE_URL and TEMPO_PAT
• Example install and run (in your MCP host configuration):

{
  "mcpServers": {
    "tempo-filler": {
      "command": "npx",
      "args": ["@tranzact/tempo-filler-mcp-server"],
      "env": {
        "TEMPO_BASE_URL": "https://your-jira-instance.atlassian.net",
        "TEMPO_PAT": "your-personal-access-token"
      }
    }
  }
}

2. Alternative: run locally if you prefer a direct npm install path (optional):

• Install package globally or in a project: npm i -g @tranzact/tempo-filler-mcp-server or npm i @tranzact/tempo-filler-mcp-server
• Run the server using the recommended MCP host tooling, providing the same environment variables as above.

3. Validate configuration:

• Confirm that TEMPO_BASE_URL points to your Tempo instance and TEMPO_PAT has sufficient permissions
• Start the MCP host and verify that the tempo-filler server registers and responds to tool calls (get_worklogs, get_schedule, bulk_post_worklogs)

Tips and caveats:

• TEMPO_BASE_URL should be the root URL of your Tempo/Jira API access point; TEMPO_PAT must have the required Tempo permissions to read and create worklogs.
• When using MCP Apps in Claude Desktop or VS Code, visual UIs render within supported hosts; CLI hosts will receive structured data suitable for conversational formatting.
• If you encounter authentication errors, re-check PAT scope and ensure the environment variables are properly propagated to the MCP host.
• The server supports get_worklogs (retrieve worklogs for a user/date range), get_schedule (determine working days and required hours), and bulk_post_worklogs (create multiple worklog entries in one operation).
• For production deployments, consider pinning the MCP server version and using a stable tempo-filler-mcp-server release to avoid breaking changes.