Paymo MCP server

What the model can do

Paymo project management and time tracking: projects with clients and budgets, tasks by project, list, assignee or completion with due dates and priority, time entries by date range, project, task or person with hours, running timers, a task's comments, clients, people and their roles, invoices by status with totals, and expenses; when you ask, can create, change, complete or delete tasks, log, edit or delete time, start or stop a timer, comment on a task, create or update and archive projects, add clients, create draft invoices, void an invoice and add expenses. Pay rates, contact details and invoice links are not read.

Reads

• paymo_projectsPaymo projects with client, active or archived, billable, budget hours, assigned users and managers (user ids).
• paymo_tasksPaymo tasks: name, code, project, task list, complete, status, priority, due date, assignees (user ids), budget hours and description.
• paymo_time_entriesPaymo time entries in a date range (default the last 7 days), by project, task, client or person: date or start and end, hours, description, billed…
• paymo_task_commentsThe comments on one Paymo task, oldest first: who (user id), when, and the text.
• paymo_clientsPaymo clients: name, active, website, city and country.
• paymo_usersPeople in the Paymo company: id, name, type (Admin, Employee, Guest) and position, active only unless include_inactive.
• paymo_invoicesPaymo invoices: number, client id, status (draft, sent, viewed, paid, void), currency, issue and due dates, subtotal and total, whether overdue…
• paymo_expensesPaymo expenses: date, amount, currency, client, project, who added it (user id), notes, tags and whether invoiced.

Acts, when you ask

These change something in Paymo. 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.

• paymo_create_taskCreates a task in Paymo on a task list, or on a project (then it goes into the project's "Default Task List", which Paymo creates if missing).
• paymo_update_taskChanges a Paymo task: its name, description, due date, priority, workflow status, task list, assignees (the new full list of user ids…
• paymo_delete_taskPermanently deletes a Paymo task, and with it every time entry logged on that task.
• paymo_log_timeLogs time on a Paymo task, for the API key's user unless user_id names someone else (that needs the access to).
• paymo_update_time_entryEdits a Paymo time entry: its description, task, hours (only on entries logged as a date and duration) or end time (on entries with a start and end).
• paymo_delete_time_entryPermanently deletes a Paymo time entry (or a running timer).
• paymo_start_timerStarts a Paymo timer on a task now (or at start_time), for the API key's user unless user_id names someone else.
• paymo_stop_timerStops a running Paymo timer now (or at end_time) by setting its end time; a timer under a minute cannot be stopped, only deleted.
• paymo_comment_on_taskAdds a comment to a Paymo task, posted as the API key's user and visible to everyone on the project; people on the task may be notified by Paymo.
• paymo_create_projectCreates a Paymo project for a client (give client_id: without one Paymo makes a 'Sample Client'), with optional users and managers…
• paymo_update_projectChanges a Paymo project: name, description, client, budget hours, users or managers (each the new full list of user ids, replacing the old)…
• paymo_create_clientAdds a client to Paymo by name (website optional).
• paymo_create_invoiceCreates a draft invoice in Paymo for a client, with line items (name, quantity, unit price) in the currency given…
• paymo_void_invoiceMarks a Paymo invoice as void (status void); the client is not told by this, and it no longer counts as owed.
• paymo_create_expenseAdds an expense in Paymo against a client (and optionally a project), in the currency given; uninvoiced expenses can be billed later.

Connect it

First connect Paymo on Dashboard → Connections, then add Memtro to your client once. The Paymo 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 Paymo 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 did we log on each project this week?
• › Which tasks are overdue on the website redesign?
• › Who has a timer running right now?
• › Which invoices are overdue, and for how much?
• › Log two hours on the Northwind discovery task for today.

Questions

Is this an official Paymo MCP server?

No. It is Memtro's MCP server with Memtro's Paymo connector behind it: the connector reads Paymo through its API with the credentials you connect on Dashboard → Connections, and Paymo 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 Paymo?

Only when you ask, and only what it has been granted: create a task on a project or task list; change, reassign, reprioritise or complete a task; delete a task and the time logged on it; log time on a task; edit a time entry; delete a time entry; start a timer on a task; stop a running timer; comment on a task; create a project; update or archive a project; add a client; create a draft invoice for a client; void an invoice; add an expense for a client. 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