Zuper MCP server

What the model can do

Zuper field service management: jobs (work orders) by status, category, priority, customer, technician, schedule and last update, one job with its status history and notes, job categories and their statuses, customers (by company and organisation), users and invoices; when you ask, can create a job, add a note to a job, move a job to a status, assign or unassign technicians, reschedule or delete a job, clock in or out of a job, and create a customer.

Reads

• zuper_list_jobsZuper jobs (work orders): number, title, category, priority, status, scheduled times, due date, organisation, the customer's uid…
• zuper_get_jobOne Zuper job with its description, status history (each status and when), and notes (who wrote what, when).
• zuper_list_job_categoriesZuper job categories (uid, name, estimated duration).
• zuper_list_customersZuper customers by uid, company, organisation, category, tags, number of jobs and whether active.
• zuper_list_usersZuper users (staff and technicians): uid, name, designation, role and whether active.
• zuper_list_invoicesZuper invoices: uid, number, invoice and due dates, status, total, whether paid, the customer's uid and the job.

Acts, when you ask

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

• zuper_create_jobCreates a Zuper job (work order) in a category, for an existing customer (customer_uid) or organisation, with a scheduled window or a due date…
• zuper_add_job_noteAdds a text note to a Zuper job.
• zuper_update_job_statusMoves a Zuper job to another status of its category (for example Scheduled, In Progress, Completed), with optional remarks.
• zuper_assign_jobAssigns technicians to a Zuper job, or unassigns them, each as a user in a team.
• zuper_reschedule_jobReschedules a Zuper job to a new start and end time (UTC), optionally taking it off its route and recording why.
• zuper_delete_jobDeletes a Zuper job; it disappears from schedules and lists and can be restored in Zuper for 90 days.
• zuper_clock_jobClocks the API key's user in to, or out of, a Zuper job at the time given (default now); this records worked time on the job.
• zuper_create_customerCreates a customer in Zuper with a name and, optionally, email, phone, company and organisation; nothing is sent to them.

Connect it

First connect Zuper on Dashboard → Connections, then add Memtro to your client once. The Zuper 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 Zuper 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

• › Which jobs are scheduled today, and who has them?
• › What is the status history of job 1042?
• › Which invoices are unpaid and past due?
• › Which high-priority jobs have no technician assigned?
• › Add a note to job 1042 saying the part arrives Thursday.

Questions

Is this an official Zuper MCP server?

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

Only when you ask, and only what it has been granted: create a job (work order) for a customer or organisation; add a note to a job; move a job to another status; assign or unassign technicians on a job; reschedule a job; delete a job (restorable for 90 days); clock in or out of a job as the key's user; create a customer. 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