[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup) # Workever MCP server: Let your AI agent run the Workever office. > 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. 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 - Page: https://cotlet.dev/integrations/workever-api-mcp-server ## What can your AI agent do in Workever? - Turn calls into jobs - Schedule fieldworkers - Find unscheduled jobs - Draft quotes with VAT - Chase unpaid invoices - Find customers and sites ## Does Workever have an MCP server or an API? - 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. | What you need | Workever API | Zapier app | Cotlet | |---|---|---|---| | 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](https://workever.com/features/integrations/), [Workever pricing](https://workever.com/pricing), [Workever on Zapier](https://zapier.com/apps/workever/integrations) ## How does the Workever MCP server work? 1. **Sign in to Workever.** Once, in a browser we host for you. 2. **Connect your AI agent.** One address in its settings. 3. **Hand 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. ## How to connect Workever to your AI agent 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. **Add the Cotlet address.** Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent. 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, 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: Tool: workever_write ``` ## All 6 Workever MCP tools ### Customers and jobs New jobs are unscheduled and reach no one, so they run at once. - **List customers** (`list_customers`, read): Customers and sites, searchable by name or postcode. - **List jobs** (`list_jobs`, read): Jobs by date, fieldworker or status. - **Create job** (`create_job`, write): Creates a job for a customer site, unscheduled. ### Schedule Scheduling a job waits for your OK. - **Schedule job** (`schedule_job`, write, asks first): Schedules a job with a fieldworker. ### Quotes and invoices Draft quotes run at once; sending stays in Workever. - **Create quote** (`create_quote`, write): Drafts a quote with lines and VAT. - **List unpaid invoices** (`list_unpaid_invoices`, read): Invoices not yet paid, oldest first. Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/workever-api-mcp-server#tools ## 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](https://cotlet.dev/security.md)). ## What happens when Workever changes? - **12 h** between tests of the Workever reads - **24 h** between tests of sends a customer would notice - **$0** for a call to a Workever tool paused for repair 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](https://status.cotlet.dev) checks the site, console and API every 3 minutes. ## Approvals, undo and mistakes 1. **Reads the request.** Customer and fault. 2. **Creates the job.** On the right site. 3. **Proposes a slot.** With a fieldworker. 4. **Waits, then schedules.** The booking shows up in your Cotlet console first. | Action | Undo | |---|---| | Create a job or draft a quote | Yes, edit or delete it in Workever | | Schedule a job | Yes, 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. ## How much does the Workever MCP server cost? **About $28 a month** for an electrical contractor with 5 fieldworkers, 4,860 credits. Your Workever plan stays as it is. | Job | Calls | Credits | |---|---|---| | Job from a call or email | 2 × 90 | 1,800 | | Job scheduled | 1 × 90 | 900 | | Unscheduled jobs, daily | 1 × 22 | 220 | | Quote drafted | 2 × 20 | 400 | | Unpaid invoices, weekly | 1 × 4 | 40 | | Cloud Browser, 30 days | | 1,500 | | Total | | 4,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. ## Workever MCP server on GitHub, Zapier or hosted: which to use | Option | What it does | Where it stops | |---|---|---| | Zapier app | New jobs, completed jobs and paid invoices to other apps. | Ultimate plan; mostly events out. | | Workever AI | An in-app assistant Workever lists as coming soon. | Inside Workever; not your ChatGPT or Claude. | | By hand | Every 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. ## Who runs Cotlet 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. --- Give your AI agents your signed-in browser. **Product:** [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) **Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet) **Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) **Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md) **Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors) **Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet) Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md) Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.