Workiz MCP server

What the model can do

Workiz field-service management: jobs and leads with status, type, source, schedule, service area, tags, assigned technicians and notes (never the client's personal contact details or any prices), and the team with roles, skills and service areas; when you ask, can create or update a job or lead, convert a lead to a job, mark a lead lost or reactivate it, assign or unassign a technician, and record a payment against a job.

Reads

• workiz_list_jobsWorkiz jobs scheduled from a date (default the last 14 days) until today, open ones unless include_closed: number, status, type, source…
• workiz_get_jobOne Workiz job by its id (e.g. XYZ56X): status, type, schedule, team, tags and notes.
• workiz_list_leadsWorkiz leads from a date (default the last 14 days) until today, open ones unless include_closed: status, type, source, business client, schedule…
• workiz_get_leadOne Workiz lead by its id.
• workiz_list_teamThe Workiz team: id, name, role, whether a field technician, service areas, skills and whether active.

Acts, when you ask

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

• workiz_create_jobCreates a job in Workiz for an existing client (client_id) or a new one (name and contact details), with its schedule, type, source…
• workiz_update_jobChanges one Workiz job's status, sub-status, schedule, type, source, service area, notes or tags.
• workiz_create_leadCreates a lead in Workiz for an existing client (client_id) or a new one (name and contact details), with its date, type, source…
• workiz_update_leadChanges one Workiz lead's status, date, type, source, service area, notes or tags.
• workiz_convert_leadConverts one Workiz lead into a job, which then follows the account's job workflow.
• workiz_mark_lead_lostMarks one Workiz lead as lost, taking it out of the open pipeline.
• workiz_activate_leadMakes a lost Workiz lead active again.
• workiz_assign_jobAssigns a team member, by name, to one Workiz job.
• workiz_unassign_jobRemoves a team member, by name, from one Workiz job.
• workiz_assign_leadAssigns a team member, by name, to one Workiz lead.
• workiz_unassign_leadRemoves a team member, by name, from one Workiz lead.
• workiz_add_job_paymentRecords a payment already received (cash, credit or check) against one Workiz job, with its amount, date and optional reference.

Connect it

First connect Workiz on Dashboard → Connections, then add Memtro to your client once. The Workiz 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 Workiz 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 open jobs are scheduled this week, and who has them?
• › Which leads came in from Google in the last two weeks?
• › What notes are on job XYZ56X?
• › Which technicians cover the North service area?
• › Mark lead 4471 as lost.

Questions

Is this an official Workiz MCP server?

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

Only when you ask, and only what it has been granted: create a job; update a job's status, schedule, type, notes or tags; create a lead; update a lead's status, schedule, type, notes or tags; convert a lead to a job; mark a lead as lost; reactivate a lost lead; assign a team member to a job; unassign a team member from a job; assign a team member to a lead; unassign a team member from a lead; record a payment against a job. 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