Workever MCP server Let your AI agent run the Workever office.

Your AI agent turns calls into jobs, schedules fieldworkers, drafts quotes and chases unpaid invoices. Sign in to Workever once in your own Cloud Browser. No API, any plan.

  • Free 7-day trial, no card
  • Unofficial, not affiliated with Workever
Workever logo Workever Cloud Browser

6 tools Read and write

Call to schedule

What can your AI agent do in Workever? The office work between the call and the invoice.

  • Turn calls into jobs

  • Schedule fieldworkers

  • Find unscheduled jobs

  • Draft quotes with VAT

  • Chase unpaid invoices

  • Find customers and sites

Zapier on Ultimate

Does Workever have an MCP server or an API? No public API, and no MCP server.

Workever has no MCP server, no ChatGPT or Claude app and no public API. Its Zapier app is on the Ultimate plan and mostly sends events such as new or completed jobs (Workever integrations, checked 9 Nov 2026). Cotlet runs 6 Workever tools hosted, over MCP for agents and REST for scripts, in your own Workever login on any plan.

  • Workever publishes no API or developer page.
  • Its Zapier app needs the Ultimate plan.
  • Workever has no connector in the ChatGPT apps directory or in Claude.
The Workever API, other options and Cotlet compared
What you need Workever APIZapier appCotlet
Create jobs No API Ultimate Yes
Schedule fieldworkers No API No Yes, after your OK
Quotes and unpaid invoices No API Events only Yes
Ask in ChatGPT or Claude No No Yes
Plan needed None Ultimate Any

Checked 8 Nov 2026. Sources: Workever integrations · Workever pricing · Workever on Zapier

Set up once

How does the Workever MCP server work? Your agent works in your own Workever login.

  1. 1Sign in to Workever

    Once, in a browser we host for you.

  2. 2Connect your AI agent

    One address in its settings.

  3. 3Hand it the busywork

    It drafts the work, you OK what customers get.

We never keep your Workever password, and no job is scheduled until you approve it. Who can see your session

Any MCP client

How to connect Workever to your AI agent

  1. 1

    Sign in to Workever in a Cloud Browser. Create a Cotlet account, open Workever in its Cloud Browser, sign in with your Workever login and press Enable for agents.

  2. 2

    Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.

  3. 3

    Let the agent in. Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the console.

Workever shares the address https://cotlet.dev/mcp/v1 with every other app you enable, so one connector covers them all. Turned Workever on after connecting? Refresh the connector and the 6 tools appear.

Claude
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

Claude Code:
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
ChatGPT
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Cursor
// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}
Codex
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
n8n
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: workever_read
Make, Zapier
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: workever_write
3 read, 3 write

All 6 Workever MCP tools

Customers and jobs3

New jobs are unscheduled and reach no one, so they run at once.

  • list_customers Customers and sites, searchable by name or postcode. read

    Returns customers with ID, sites, open jobs and balance.

    MCP callworkever_read → list_customers

    REST endpointGET https://cotlet.dev/api/v1/workever/customers

    Parameters

    Parameters: list_customers
    NameTypeDescription
    query string string Name or postcode.
    page integer integer Page number. Default: 1.

    Example response

    {
      "customers": [
        {
          "customer_id": "WC-2210",
          "name": "Sophie Hargreaves",
          "site": "18 Burton Rd, Manchester",
          "open_jobs": 1
        }
      ],
      "page": 1
    }
  • list_jobs Jobs by date, fieldworker or status. read

    Returns jobs with customer, site, fieldworker, time and status.

    MCP callworkever_read → list_jobs

    REST endpointGET https://cotlet.dev/api/v1/workever/jobs

    Parameters

    Parameters: list_jobs
    NameTypeDescription
    date_from string string ISO date.
    date_to string string ISO date.
    status string string Unscheduled, Scheduled, Completed.
    page integer integer Page number. Default: 1.

    Example response

    {
      "jobs": [
        {
          "job_id": "WJ-5512",
          "customer": "Sophie Hargreaves",
          "title": "EICR",
          "fieldworker": "Tom",
          "start": "2026-11-10T09:00",
          "status": "Scheduled"
        }
      ]
    }
  • create_job Creates a job for a customer site, unscheduled. write

    Adds the job with title and description. Reaches no one, so it runs at once.

    MCP callworkever_write → create_job

    REST endpointPOST https://cotlet.dev/api/v1/workever/customers/{customer_id}/jobs

    Parameters

    Parameters: create_job
    NameTypeDescription
    customer_id string required string Customer ID from list_customers.
    title string required string Job title.
    description string string Details.

    Example input

    {
      "customer_id": "customer_8c41d2",
      "title": "title"
    }

    Example response

    {
      "job_id": "WJ-5560",
      "customer": "Aisha Rahman",
      "title": "Socket not working",
      "status": "Unscheduled"
    }

Schedule1

Scheduling a job waits for your OK.

  • schedule_job Schedules a job with a fieldworker. writeasks first

    Puts the job in the schedule; the fieldworker gets it in the app and your settings decide whether the customer is told. By default you confirm each call; you can switch that off for this tool.

    MCP callworkever_write → schedule_job

    REST endpointPOST https://cotlet.dev/api/v1/workever/jobs/{job_id}/schedule

    Parameters

    Parameters: schedule_job
    NameTypeDescription
    job_id string required string Job ID from list_jobs.
    fieldworker string required string Fieldworker name.
    start string required string ISO date and time.

    Example input

    {
      "job_id": "WJ-5560",
      "fieldworker": "Tom",
      "start": "2026-11-11T14:00"
    }

    Example response

    {
      "job_id": "WJ-5560",
      "fieldworker": "Tom",
      "start": "2026-11-11T14:00",
      "status": "Scheduled"
    }

Quotes and invoices2

Draft quotes run at once; sending stays in Workever.

  • create_quote Drafts a quote with lines and VAT. write

    Creates the quote for the customer; sending it stays in Workever. Reaches no one, so it runs at once.

    MCP callworkever_write → create_quote

    REST endpointPOST https://cotlet.dev/api/v1/workever/customers/{customer_id}/quotes

    Parameters

    Parameters: create_quote
    NameTypeDescription
    customer_id string required string Customer ID from list_customers.
    items array required array Description, quantity, price, VAT rate.

    Example input

    {
      "customer_id": "customer_8c41d2",
      "items": "items"
    }

    Example response

    {
      "quote_id": "WQ-1180",
      "customer": "Aisha Rahman",
      "total": "540.00",
      "status": "Draft"
    }
  • list_unpaid_invoices Invoices not yet paid, oldest first. read

    Returns unpaid invoices with customer, total and days overdue.

    MCP callworkever_read → list_unpaid_invoices

    REST endpointGET https://cotlet.dev/api/v1/workever/unpaid-invoices

    Parameters

    Parameters: list_unpaid_invoices
    NameTypeDescription
    min_days_overdue integer integer Only invoices overdue at least this many days.

    Example response

    {
      "invoices": [
        {
          "invoice_id": "WI-3021",
          "customer": "Sophie Hargreaves",
          "total": "186.00",
          "days_overdue": 12
        }
      ]
    }
Encrypted, revocable

Who can see my Workever session, and how do I revoke it?

  • What we store

    Your signed-in Workever profile, AES-256-GCM encrypted, in Finland. No password.

  • What your agent gets

    The 6 Workever tools, never the session cookie.

  • What the session sees

    What your login sees: customers, sites, jobs, schedule, quotes, invoices.

  • What no tool touches

    Payments, timesheets, stock, contracts, settings, deletes.

  • If Workever signs you out

    You sign in again yourself, in the same Cloud Browser.

  • How to cut access

    Disable for agents, reset the browser, or change your Workever password.

Cotlet never types your password: you sign in yourself, and the agent only uses the session. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).

Tested every 12 h

What happens when Workever changes? We repair the tool; your prompts stay the same.

between tests of the Workever reads
12 h
between tests of sends a customer would notice
24 h
for a call to a Workever tool paused for repair
$0

When Workever moves a button on a job or renames a schedule view, we fix the tool and your agent calls it the same way. status.cotlet.dev checks the site, console and API every 3 minutes.

1 tool asks first

Approvals, undo and mistakes Customers get nothing until you say so.

  1. 01 Reads the request Customer and fault.
  2. 02 Creates the job On the right site.
  3. 03 Proposes a slot With a fieldworker.
  4. 04 Waits, then schedules The booking shows up in your Cotlet console first.
Which Workever actions can be undone
ActionUndo
Create a job or draft a quoteYes, edit or delete it in Workever
Schedule a jobYes, move or unschedule it

1 of 6 tools ask first: schedule_job. New jobs and draft quotes reach no customer, so they run at once. You can turn the wait off per tool once you trust a routine.

MCP call
{
  "name": "schedule_job",
  "arguments": {
    "job_id": "WJ-5560",
    "fieldworker": "Tom",
    "start": "2026-11-11T14:00"
  }
}
REST
curl -X POST https://cotlet.dev/api/v1/workever/jobs/WJ-5560/schedule \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"fieldworker":"Tom","start":"2026-11-11T14:00"}'
Response
{
  "job_id": "WJ-5560",
  "fieldworker": "Tom",
  "start": "2026-11-11T14:00",
  "status": "Scheduled"
}

A cron job or n8n flow can call the same tools over REST at /api/v1/workever with the same key and price, in JSON. Failed calls are free. Each tool row above shows its REST path.

Pay per call

How much does the Workever MCP server cost?

About $28 a monthfor an electrical contractor with 5 fieldworkers, 4,860 credits. Your Workever plan stays as it is.

A month of Workever office work for a 5-fieldworker contractor, in credits
JobCallsCredits
Job from a call or email2 × 901,800
Job scheduled1 × 90900
Unscheduled jobs, daily1 × 22220
Quote drafted2 × 20400
Unpaid invoices, weekly1 × 440
Cloud Browser, 30 days1,500
Total4,860
  • Free 7-day trial, no card
  • 10 credits per successful call, MCP or REST
  • 50 credits a day for the Cloud Browser
  • Works on Base and Ultimate

Workever publishes no job counts, so the month is our example. Dollars at the $29 pack rate.

Cotlet credit packs: price, credits and calls at 10 credits each
Credits Price, one time Calls at 10 credits Per 1,000 credits
5,000 $29 500 $5.80
15,000 $79 1,500 $5.27
32,000 $149 3,200 $4.66
60,000 $249 6,000 $4.15

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.

Other options

Workever MCP server on GitHub, Zapier or hosted: which to use No API; Zapier only on Ultimate.

Other ways to connect Workever, checked 8 Nov 2026
OptionWhat it doesWhere it stops
Zapier appNew jobs, completed jobs and paid invoices to other apps.Ultimate plan; mostly events out.
Workever AIAn in-app assistant Workever lists as coming soon.Inside Workever; not your ChatGPT or Claude.
By handEvery screen of Workever, one job at a time.Your office's time.

If you are on Ultimate and only need job events in another app, the Zapier app does that. To create, schedule and quote from ChatGPT or Claude this week, Cotlet works in the Workever account you already have.

EU company, since 2019

Who runs Cotlet A company you can look up.

Take Group sp. z o.o. runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), in business since 2019, led by its founders Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Workever tools go to contact@cotlet.dev.

Workever MCP server: questions

How do I get access?

Sign up free at https://cotlet.dev, open Workever under Integrations in the console and sign in to Workever in its Cloud Browser. The trial starts with your first app and asks for no card.

How do I connect Workever to ChatGPT or Claude?

Sign up at cotlet.dev, log in to Workever once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Workever account through Cotlet, in their phone apps too.

What can ChatGPT do in Workever?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Workever: turn calls into jobs; fill the schedule; see what is unscheduled. You ask in plain words, and anything that reaches other people waits for your OK first.

Is there an official ChatGPT or Claude app for Workever?

No. Workever has no ChatGPT or Claude connector of its own and Workever has no official MCP server (checked 9 Nov 2026). Cotlet is an independent one that works in ChatGPT, Claude, Cursor and any MCP client, on your signed-in account.

Can ChatGPT create jobs in Workever?

Yes, with Cotlet. ChatGPT turns calls and emails into jobs for the right customer and site.

Can ChatGPT schedule jobs in Workever?

Yes, with Cotlet. ChatGPT schedules jobs with the fieldworker and time you name, after your OK, and lists what is still unscheduled.

Can ChatGPT create quotes in Workever?

Yes, with Cotlet. ChatGPT drafts quotes with VAT, ready to send from Workever.

Is the MCP server different from the REST API?

Only in how it is called. Both carry the same 6 tools, inputs, answers, API key and price. Agents use MCP; scripts and HTTP steps use REST.

Is Cotlet affiliated with Workever?

No. Cotlet is independent and not affiliated with Workever.

Hand the Workever office to your agent.

Free 7-day trial with 2,000 credits, no card needed.