Tempo Filler

You can use this MCP server to interact with Tempo worklogs in JIRA through AI-assisted workflows. It enables retrieving, creating, bulk posting, and managing worklogs, along with scheduling information and rich MCP Apps views for visualizing timesheets and calendars.

How to use

To use the Tempo Filler MCP Server with an MCP client, configure a standard MCP server connection that runs locally and communicates with Tempo via a Personal Access Token. You can retrieve existing worklogs, create single or multiple worklogs, delete entries, and fetch scheduling information to plan time entries. When used with MCP Apps-enabled hosts, you gain visual components like a timesheet grid and a schedule calendar that render inline in your assistant interface.

How to install

Prerequisites you need before installation: Node.js version 18 or higher, and a JIRA instance with the Tempo Timesheets plugin enabled. You also need a Personal Access Token (PAT) for authentication.

Option 1: NPX (recommended for quick start)

npx @tranzact/tempo-filler-mcp-server

Option 2: Manual MCP server configuration for your AI assistant

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

Additional setup notes

If you plan to use visuals in MCP Apps-enabled hosts, ensure the Tempo base URL and PAT are provided in the environment variables as shown above. The server supports both a quick NPX approach and a fully defined MCP configuration for your AI client.

Configuration and security

Environment variables are required for authentication and default behavior. The essential values are the Tempo base URL and your personal access token (PAT). You can also set a default number of hours per workday to tailor the planner to your work pattern.

Usage examples and scenarios

Common workflows include logging a single day’s work, bulk-creating multiple days, and checking schedules before populating entries. Visual MCP Apps views provide a calendar and a timesheet grid to help you verify days, hours, and project associations before committing worklogs.

Troubleshooting and notes

If you encounter authentication failures, verify that TEMPO_BASE_URL points to your JIRA instance and TEMPO_PAT has the necessary permissions. Ensure your Tempo Timesheets plugin is installed and accessible from your JIRA instance. For UI issues in MCP Apps components, confirm that your host supports MCP Apps visuals and that the app extensions are enabled.

Available tools

get_worklogs

Retrieve worklogs for a date range with optional filtering. In MCP Apps-compatible hosts, displays an interactive timesheet grid.

post_worklog

Log a single worklog entry for a specific issue and date with optional description and billable flag.

bulk_post_worklogs

Create multiple worklog entries efficiently with concurrent processing and optional billable flag.

delete_worklog

Remove an existing worklog entry by its ID.

get_schedule

Retrieve the work schedule showing working days, non-working days, and expected hours per day, with an interactive calendar view in MCP Apps hosts.