Skip to content

Paymo MCP by usefulapi

by usefulapi.io · remote · no sign-in to list tools · v1.16.3 · published by io.usefulapi

Browse Paymo projects, tasks, timesheets and invoices, and create tasks, log time or run timers.

Deletes · 8
CompareRegistry entry

21 tools: 8 can delete or cancel things and 13 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http paymo https://paymo.usefulapi.io/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

21 tools

Deletes or cancels 8Claude Code: deny
  • paymo_add_task_commentAdd a comment to a task's discussion thread (content may contain basic HTML).No findings

    Why it is in this group

    • The name "paymo_add_task_comment" says "add": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Add a comment to a task's discussion thread (content may contain basic HTML). Read existing comments with paymo_get_task include=thread.comments. Paymo: POST /api/comments.

    Annotations the server declares

    • title: Comment on a task
    • destructiveHint: true
  • paymo_create_projectCreate a project.No findings

    Why it is in this group

    • The name "paymo_create_project" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Create a project. Note: if client_id is omitted Paymo auto-creates a 'Sample Client'. Free plans have an active-projects limit (403). Paymo: POST /api/projects.

    Annotations the server declares

    • title: Create a project
    • destructiveHint: true
  • paymo_create_taskCreate a task in a task list (tasklist_id) or a project (project_id — goes to its 'Default Task List').No findings

    Why it is in this group

    • The name "paymo_create_task" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Create a task in a task list (tasklist_id) or a project (project_id — goes to its 'Default Task List'). Paymo: POST /api/tasks.

    Annotations the server declares

    • title: Create a task
    • destructiveHint: true
  • paymo_create_time_entryLog a completed time entry on a task, EITHER as date + duration_seconds OR as start_time + end_time (min 1 minute).No findings

    Why it is in this group

    • The name "paymo_create_time_entry" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Log a completed time entry on a task, EITHER as date + duration_seconds OR as start_time + end_time (min 1 minute). To start a live timer use paymo_start_timer. Paymo: POST /api/entries.

    Annotations the server declares

    • title: Log time
    • destructiveHint: true
  • paymo_start_timerStart a running timer on a task (a time entry with a start_time and no end_time).No findings

    Why it is in this group

    • The name "paymo_start_timer" says "start": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Start a running timer on a task (a time entry with a start_time and no end_time). A user can have only one running timer; if one is running Paymo returns 409. Paymo: POST /api/entries.

    Annotations the server declares

    • title: Start a timer
    • destructiveHint: true
  • paymo_stop_timerStop a running timer by setting its end_time (default: now).No findings

    Why it is in this group

    • The name "paymo_stop_timer" says "stop": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Stop a running timer by setting its end_time (default: now). The final duration must be at least 1 minute. Find running timers with paymo_list_time_entries running_only=true. Paymo: PUT /api/entries/{id}.

    Annotations the server declares

    • title: Stop a timer
    • destructiveHint: true
  • paymo_update_taskUpdate a task — rename, re-describe, reassign (users replaces the whole list), set due date or priority, mark complete/incomplete, move to another task list or workflow status.No findings

    Why it is in this group

    • The name "paymo_update_task" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Update a task — rename, re-describe, reassign (users replaces the whole list), set due date or priority, mark complete/incomplete, move to another task list or workflow status. Only the fields given are changed. Paymo: PUT /api/tasks/{id}.

    Annotations the server declares

    • title: Update a task
    • destructiveHint: true
  • paymo_update_time_entryEdit a time entry: description, task, or its length.No findings

    Why it is in this group

    • The name "paymo_update_time_entry" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Edit a time entry: description, task, or its length. duration_seconds only applies to date+duration entries; for start/end entries change end_time instead. Paymo: PUT /api/entries/{id}.

    Annotations the server declares

    • title: Update a time entry
    • destructiveHint: true
Only reads 13Claude Code: allow
  • paymo_get_companyFetch the company (account) info and settings: name, default currency, timezone, working days, invoice numbering.No findings

    Why it is in this group

    • The name "paymo_get_company" says "get": a word for reading.
    Description, as the server wrote it
    Fetch the company (account) info and settings: name, default currency, timezone, working days, invoice numbering. Paymo: GET /api/company.

    Annotations the server declares

    • title: Get company info
    • readOnlyHint: true
  • paymo_get_invoiceFetch one invoice with totals, and (by default) its line items and payments.No findings

    Why it is in this group

    • The name "paymo_get_invoice" says "get": a word for reading.
    Description, as the server wrote it
    Fetch one invoice with totals, and (by default) its line items and payments. Paymo: GET /api/invoices/{id}?include=invoiceitems,invoicepayments.

    Annotations the server declares

    • title: Get an invoice
    • readOnlyHint: true
  • paymo_get_meFetch the Paymo user the API key belongs to (id, name, type, timezone).No findings

    Why it is in this group

    • The name "paymo_get_me" says "get": a word for reading.
    Description, as the server wrote it
    Fetch the Paymo user the API key belongs to (id, name, type, timezone). Use the id as user_id for 'my' time entries and timers. A cheap way to confirm the key works. Paymo: GET /api/me.

    Annotations the server declares

    • title: Get the current user
    • readOnlyHint: true
  • paymo_get_projectFetch one project, optionally with related objects inline, e.g.No findings

    Why it is in this group

    • The name "paymo_get_project" says "get": a word for reading.
    Description, as the server wrote it
    Fetch one project, optionally with related objects inline, e.g. include=tasklists.tasks for the whole task tree or include=client. Paymo: GET /api/projects/{id}.

    Annotations the server declares

    • title: Get a project
    • readOnlyHint: true
  • paymo_get_taskFetch one task, optionally with related objects: include=thread.comments for its comments, subtasks, entries (time logged), files, project.No findings

    Why it is in this group

    • The name "paymo_get_task" says "get": a word for reading.
    Description, as the server wrote it
    Fetch one task, optionally with related objects: include=thread.comments for its comments, subtasks, entries (time logged), files, project. Paymo: GET /api/tasks/{id}.

    Annotations the server declares

    • title: Get a task
    • readOnlyHint: true
  • paymo_list_clientsList clients (id, name, contact details, active flag).No findings

    Why it is in this group

    • The name "paymo_list_clients" says "list": a word for reading.
    Description, as the server wrote it
    List clients (id, name, contact details, active flag). Paymo: GET /api/clients.

    Annotations the server declares

    • title: List clients
    • readOnlyHint: true
  • paymo_list_expensesList expenses (id, client_id, project_id, user_id, amount, currency, date, notes, invoiced, tags).No findings

    Why it is in this group

    • The name "paymo_list_expenses" says "list": a word for reading.
    Description, as the server wrote it
    List expenses (id, client_id, project_id, user_id, amount, currency, date, notes, invoiced, tags). Paymo: GET /api/expenses.

    Annotations the server declares

    • title: List expenses
    • readOnlyHint: true
  • paymo_list_invoicesList invoices (id, number, client_id, status, currency, date, due_date, subtotal, total).No findings

    Why it is in this group

    • The name "paymo_list_invoices" says "list": a word for reading.
    Description, as the server wrote it
    List invoices (id, number, client_id, status, currency, date, due_date, subtotal, total). Paymo: GET /api/invoices.

    Annotations the server declares

    • title: List invoices
    • readOnlyHint: true
  • paymo_list_projectsList projects (id, name, code, client_id, active, billable, budget_hours, users, managers), optionally filtered.No findings

    Why it is in this group

    • The name "paymo_list_projects" says "list": a word for reading.
    Description, as the server wrote it
    List projects (id, name, code, client_id, active, billable, budget_hours, users, managers), optionally filtered. Paymo: GET /api/projects.

    Annotations the server declares

    • title: List projects
    • readOnlyHint: true
  • paymo_list_tasklistsList task lists (id, name, project_id, milestone_id), e.g.No findings

    Why it is in this group

    • The name "paymo_list_tasklists" says "list": a word for reading.
    Description, as the server wrote it
    List task lists (id, name, project_id, milestone_id), e.g. to pick a tasklist_id when creating a task. Paymo: GET /api/tasklists.

    Annotations the server declares

    • title: List task lists
    • readOnlyHint: true
  • paymo_list_tasksList tasks (id, name, code, project_id, tasklist_id, complete, due_date, users, priority), filtered by project, task list, assignee or completion.No findings

    Why it is in this group

    • The name "paymo_list_tasks" says "list": a word for reading.
    Description, as the server wrote it
    List tasks (id, name, code, project_id, tasklist_id, complete, due_date, users, priority), filtered by project, task list, assignee or completion. my_tasks=true returns the caller's 'My Tasks'. Paymo: GET /api/tasks.

    Annotations the server declares

    • title: List tasks
    • readOnlyHint: true
  • paymo_list_time_entriesList time entries (id, task_id, user_id, project_id, start_time/end_time or date, duration in seconds, description, billed).No findings

    Why it is in this group

    • The name "paymo_list_time_entries" says "list": a word for reading.
    Description, as the server wrote it
    List time entries (id, task_id, user_id, project_id, start_time/end_time or date, duration in seconds, description, billed). At least one filter is required. from/to filter by the entry's time interval; running_only=true returns running timers. Paymo: GET /api/entries.

    Annotations the server declares

    • title: List time entries
    • readOnlyHint: true
  • paymo_list_usersList users in the company (id, name, email, type, hourly rate, assigned/managed projects).No findings

    Why it is in this group

    • The name "paymo_list_users" says "list": a word for reading.
    Description, as the server wrote it
    List users in the company (id, name, email, type, hourly rate, assigned/managed projects). Paymo: GET /api/users.

    Annotations the server declares

    • title: List users
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.16.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http paymo https://paymo.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__paymo__paymo_get_me",
      "mcp__paymo__paymo_get_company",
      "mcp__paymo__paymo_list_users",
      "mcp__paymo__paymo_list_clients",
      "mcp__paymo__paymo_list_projects",
      "mcp__paymo__paymo_get_project",
      "mcp__paymo__paymo_list_tasklists",
      "mcp__paymo__paymo_list_tasks",
      "mcp__paymo__paymo_get_task",
      "mcp__paymo__paymo_list_time_entries",
      "mcp__paymo__paymo_list_invoices",
      "mcp__paymo__paymo_get_invoice",
      "mcp__paymo__paymo_list_expenses"
    ],
    "ask": [],
    "deny": [
      "mcp__paymo__paymo_create_project",
      "mcp__paymo__paymo_create_task",
      "mcp__paymo__paymo_update_task",
      "mcp__paymo__paymo_create_time_entry",
      "mcp__paymo__paymo_update_time_entry",
      "mcp__paymo__paymo_start_timer",
      "mcp__paymo__paymo_stop_timer",
      "mcp__paymo__paymo_add_task_comment"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as paymo. Review it before you use it.