Tempo MCP server

What the model can do

Tempo Timesheets and Planner for Jira Cloud: worklogs by date, project or issue with hours and totals, Tempo accounts, teams, and resource plans. Issues and people are named by Jira id only. Can log, edit and delete time, submit, approve, reject, reopen or recall a timesheet, and create, change or delete a plan.

Reads

• tempo_list_worklogsTempo worklogs between two dates (default the last 7 days): date, hours, billable hours, Jira issue id, author account id and description…
• tempo_list_accountsTempo accounts (what time is logged against for billing or cost tracking): key, name, status, category and customer.
• tempo_list_teamsTempo teams: id, name, summary, status and the lead's Atlassian account id.
• tempo_list_plansTempo Planner resource plans overlapping a date window (default today for 14 days): who or what generic resource is planned on which Jira issue or…

Acts, when you ask

These change something in Tempo. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• tempo_create_worklogLogs time in Tempo against one Jira issue (numeric issue id), for the named author on the given date.
• tempo_update_worklogChanges one Tempo worklog's date, start time, hours, billable hours or description; everything not given stays as it was…
• tempo_delete_worklogPermanently deletes one Tempo worklog, removing its time from the timesheet, billing and payroll.
• tempo_submit_timesheetSubmits one person's Tempo timesheet for the period to its reviewer for approval (status IN_REVIEW).
• tempo_recall_timesheetRecalls one person's submitted Tempo timesheet for the period from review (status OPEN).
• tempo_approve_timesheetApproves one person's submitted Tempo timesheet for the period (status APPROVED), which locks its hours for billing and payroll.
• tempo_reject_timesheetRejects one person's submitted Tempo timesheet for the period, sending it back to them (status OPEN) with the comment.
• tempo_reopen_timesheetReopens one person's approved Tempo timesheet for the period (status OPEN) so its hours can change again.
• tempo_create_planPlans a person (Atlassian account id) or a generic resource onto a Jira issue or project in Tempo Planner, between two dates…
• tempo_update_planChanges one Tempo plan's dates, hours or description; everything not given stays as it was (Memtro reads the plan and resends the rest…
• tempo_delete_planPermanently deletes one Tempo plan (resource allocation).

Connect it

First connect Tempo on Dashboard → Connections, then add Memtro to your client once. The Tempo tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Tempo connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › How many hours were logged on project 10000 last week?
• › Who logged billable hours on issue 10234 this month?
• › Which Tempo accounts are active, and which customer is each for?
• › What is planned on project 10000 over the next two weeks?
• › Log two hours on issue 10234 for me today for the client call.

Questions

Is this an official Tempo MCP server?

No. It is Memtro's MCP server with Memtro's Tempo connector behind it: the connector reads Tempo through its API with the credentials you connect on Dashboard → Connections, and Tempo publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Tempo?

Only when you ask, and only what it has been granted: log time against a Jira issue; change a worklog's date, time, hours or description; delete a worklog; submit or recall a timesheet for approval; approve, reject or reopen a timesheet; plan a person or generic resource onto an issue or project; change or delete a plan. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Work management

• Clio Manage MCP server
• Linear MCP server
• Jira MCP server
• Asana MCP server
• monday.com MCP server
• Airtable MCP server