Retrieve a list of Tempo worklogs matching the given search parameters. Supports filtering by project, issue, date range, and more.

Retrieve a single Tempo worklog by its id.

Create a new Tempo worklog. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).

Update an existing Tempo worklog by id. Supply only the fields to change. Fields you omit keep their current values: the tool reads the current resource and merges your fields over it (Tempo's PUT replaces the whole resource, so an update built from only the changed fields would wipe the rest). That read runs on every call, so the preview shows the full merged body, and a resource that changes between the preview and the confirmed call is refused rather than overwritten. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).

Delete a Tempo worklog by id. bypassPeriodClosuresAndApprovals can rip a worklog out of an already-approved timesheet, so the preview surfaces the bypass flag. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).

Search Tempo worklogs using a POST body with advanced filters (author ids, issue ids, project ids, date range). For team or Tempo-account filters use tempo_get_worklogs_by_team / tempo_get_worklogs_by_account.

Retrieve all Tempo worklogs for a specific user (Atlassian account id).

Retrieve all Tempo worklogs for a specific Jira project.

Retrieve all Tempo worklogs for a specific Jira issue.

Retrieve all Tempo worklogs for a specific Tempo team.

Retrieve all Tempo worklogs associated to a Tempo account key.

Retrieve a list of Tempo plans (resource allocations) matching the given parameters. Requires from and to dates.

Retrieve a single Tempo plan (resource allocation) by id.

Create a new Tempo plan (resource allocation) for a user or generic resource against an issue or project. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).

Update an existing Tempo plan (resource allocation) by id. Supply only the fields to change. Fields you omit keep their current values: the tool reads the current resource and merges your fields over it (Tempo's PUT replaces the whole resource, so an update built from only the changed fields would wipe the rest). That read runs on every call, so the preview shows the full merged body, and a resource that changes between the preview and the confirmed call is refused rather than overwritten. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).

Delete a Tempo plan (resource allocation) by id. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).

Retrieve a list of Tempo teams. Can filter by name, member account ids, or specific team ids.

Retrieve a single Tempo team by id.

Create a new Tempo team. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).

Update an existing Tempo team by id. Supply only the fields to change. Fields you omit keep their current values: the tool reads the current resource and merges your fields over it (Tempo's PUT replaces the whole resource, so an update built from only the changed fields would wipe the rest). That read runs on every call, so the preview shows the full merged body, and a resource that changes between the preview and the confirmed call is refused rather than overwritten. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).

Delete a Tempo team by id. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).

Retrieve all memberships for a single Tempo team. To filter across teams — or by account or role — use tempo_search_team_memberships.

Search Tempo team memberships across teams, accounts, and roles via POST. Inactive memberships are included.

Retrieve a list of all Tempo accounts (OPEN and CLOSED).

Retrieve a single Tempo account by its numeric id. Only update/delete address an account by key — to go from a key to an id, use tempo_search_accounts with keys: ["ACCOUNT-123"].

Search Tempo accounts by id, key, status, or global flag. This is also how you resolve an account key to the numeric id that tempo_get_account needs.

Create a new Tempo account. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).

Update an existing Tempo account by its key. Supply only the fields to change. Fields you omit keep their current values: the tool reads the current resource and merges your fields over it (Tempo's PUT replaces the whole resource, so an update built from only the changed fields would wipe the rest). That read runs on every call, so the preview shows the full merged body, and a resource that changes between the preview and the confirmed call is refused rather than overwritten. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).

Delete a Tempo account by its key. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).

Retrieve all Tempo account categories, or a single category when id is given. This endpoint is not paginated.

Retrieve a paginated list of all Tempo Financial Manager projects.

Retrieve a single Tempo Financial Manager project by id.

Retrieve the current timesheet approval status for a user in the given period.

Retrieve all timesheets that are currently waiting for approval.

Retrieve every team member's timesheet approval for the given period — the reviewer's view of who has submitted, who is still open, and who has been approved.

Retrieve the users who can review a given user's timesheet. Use this to source reviewerAccountId for tempo_submit_timesheet and the other approval actions.

Search timesheet approval audit logs. Requires appropriate Tempo permissions; results may contain PII (account ids, reviewer actions). Paginated via nextPageToken from the previous response.

Submit a user's timesheet for the given period for approval, moving it from OPEN to WAITING_FOR_APPROVAL. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).

Approve a user's submitted timesheet for the given period. Reviewer action — approving locks the period's worklogs against further edits. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).

Reject a user's submitted timesheet for the given period, sending it back to the user for changes. Reviewer action — supply a comment explaining why. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).

Reopen a user's already-approved timesheet for the given period, returning it to OPEN so worklogs can be edited again. Reviewer action — this undoes an approval. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).

Recall a user's own timesheet that was submitted but not yet approved, returning it to OPEN so it can be corrected and resubmitted. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).

Retrieve Tempo period definitions (used for timesheet approval cycles).

Retrieve the work schedule for a user, including planned working hours per day.

Retrieve the global Tempo configuration settings.

Retrieve all Tempo work attributes (custom fields on worklogs).

Retrieve all Tempo roles.

Resolves the credential the way real tools do, then makes one authenticated request to api.tempo.io. Reports which source supplied the credential, whether api.tempo.io accepted it, the round-trip time, and a plain-English hint distinguishing 'no credential' from 'credential rejected' from 'a api.tempo.io-side problem'. Read-only; never returns the credential itself. Call this when a real tool fails and you want to know which hop broke.