Service Autopilot MCP Server

Jobs, schedules, estimates and invoices in Service Autopilot.

Hosted MCP Server

npx add-mcp 'https://cotlet.dev/mcp/v1/service-autopilot'

Installs into Claude Code, Codex, Cursor and more

Documentation

Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up

Service Autopilot API and MCP server: Let your AI agent run the Service Autopilot office.

Service Autopilot has no open API and no MCP server (checked 27 Oct 2026). Its help center says it plainly, and the only Zapier link sends completed jobs out through a webhook. Cotlet runs 14 hosted tools in your own office login, over MCP for agents and REST for scripts.

Jobs, schedules, estimates and invoices in Service Autopilot. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.

MCP setup REST API guide

Free 7-day trial, no card
Unofficial, not affiliated with Service Autopilot or Xplor
Page: https://cotlet.dev/integrations/service-autopilot-api-mcp-server

What can you automate in Service Autopilot?

Move rained-out visits to an open day
Read each crew's route for the day
Add clients with repeating jobs
Turn site notes into estimates
Invoice jobs and list what is unpaid
Text clients the new visit day

Does Service Autopilot have an MCP server or an API?

The help center FAQ answers "Do you have an open API": "We do not have an open API". Integrations exist only for partners who "have worked with our engineering team", such as QuickBooks, SendJim and NextBillion.
Settings > Zapier Integrations has one event type, Job Completed, sent to a Zapier webhook. Zapier has no Service Autopilot app, so nothing writes back.
A two-way Zapier link was announced as "In Progress" in the 12 Dec 2025 release notes. The release of 16 Oct 2026 did not ship it.

What you need	QuickBooks sync	Zapier webhook	Cotlet
Read routes, jobs and estimates	Not synced	Completed jobs only	Yes
Create or move a job	No	Out only	Yes
Create and send an estimate	Estimates excluded	No	Yes, after your OK
See unpaid invoices	In QuickBooks	No	Yes
Allowed by Service Autopilot	Yes, official	Yes, official	Uses the web app

Checked 27 Oct 2026. Sources: Service Autopilot Help: FAQs, Service Autopilot Help: Integrations, Service Autopilot Help: Zapier Integration, Completed Jobs Trigger, Service Autopilot pricing and plan features

How does Cotlet connect to Service Autopilot?

Sign in to Service Autopilot. Use your own account in its Cotlet Cloud Browser.
Choose MCP or REST. Connect your agent or create a Cotlet API key.
Run your workflow. Ask your agent or send an HTTP request.

We never keep your Service Autopilot password, and no estimate, invoice or text reaches a client until you approve it.

Connect Service Autopilot to your agent or workflow

Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.

Enable Service Autopilot for agents. Create a Cotlet account, open Service Autopilot in the console, sign in at the Member Login in its Cloud Browser, then press Enable for agents.
Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 in your agent as a remote MCP server or a custom connector.
Allow the connection. Chat apps send you to a Cotlet sign-in page. Code editors, n8n and scripts take an API key from the console instead.

The shared address https://cotlet.dev/mcp/v1 carries Service Autopilot next to your other apps. Service Autopilot plans include one business user (Elite has two), so the agent usually works under the owner's or office manager's login. Refresh the connector after enabling Service Autopilot so its tools load.

Claude:

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

Claude Code:
claude mcp add --transport http cotlet-service-autopilot \
  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-service-autopilot": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}

Codex:

# ~/.codex/config.toml
[mcp_servers.cotlet-service-autopilot]
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: service_autopilot_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: service_autopilot_write

How to use the Service Autopilot REST API

Create your Cotlet API key

Create a Cotlet API key with access to Service Autopilot and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.

Connect Service Autopilot in Cotlet and enable it for agents. Account access: Your own Service Autopilot office user account.

Make your first Service Autopilot API request

REST:

curl https://cotlet.dev/api/v1/service-autopilot/estimates \
  -H "Authorization: Bearer $COTLET_API_KEY"

Read estimates and apply the operation limits

A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.

Illustrative response excerpt:

{
  "status": "success",
  "app": "service-autopilot",
  "tool": "list_estimates",
  "result": {
    "estimates": [
      {
        "estimate_id": "E-20418",
        "client": "Dana Henderson",
        "total": "450.00",
        "status": "sent",
        "sent_at": "2026-10-08"
      }
    ]
  }
}

Lists estimates, newest first, with client, total and whether the estimate was sent. Filter by client or creation date.

Pass estimate_id to send_estimate.

limit: 1 to 100. Default: 25.

Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.

Service Autopilot workflows for agents and automations

Tool	Connect through	Example workflow
n8n	HTTP Request	Scheduled and completed jobs in a date range, with client, address, crew and price. Use `list_jobs` in your configured business report.
Make	HTTP > Make a request	Invoices with client, amount, due date, paid or unpaid and days past due. Use `list_invoices` in your configured business report.
Python or Node.js	REST API	Client account history: contact details, jobs, estimates, invoices and notes. Use `get_client` in your configured business report.

Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.

Cotlet reads Service Autopilot; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.

Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.

The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.

Service Autopilot API endpoints and MCP tools

Clients and leads

Search covers clients and leads by address, email or phone, so a sign-up already on file as a lead is caught before a duplicate. A lead cannot get a scheduled job until you convert it in the app.

Search clients (search_clients, read): Find clients and leads by name, address, email or phone.
Get client (get_client, read): Client account history: contact details, jobs, estimates, invoices and notes.
Add client (add_client, write): New client or lead with contact details and a service address.

Jobs and routes

Service names must match your own price list. Moving one visit leaves the rest of a weekly schedule on its old weekday; routes are read, never reordered.

List jobs (list_jobs, read): Scheduled and completed jobs in a date range, with client, address, crew and price.
Get route (get_route, read): A crew or technician route for one day: stops in route order with client and address.
Create job (create_job, write): One-time or repeating job for a client, assigned to a crew.
Reschedule job (reschedule_job, write): Move a scheduled visit to another day or crew.
Add job note (add_job_note, write): Add a note to a job.

Estimates

A new estimate stays a draft. Sending emails the proposal link from your estimate template and asks first.

List estimates (list_estimates, read): Estimates with client, total, date sent and status.
Create estimate (create_estimate, write): Estimate for a client from line items. Nothing is sent until you call send_estimate.
Send estimate (send_estimate, write, asks first): Email an estimate to the client.

Invoices and texts

Unpaid invoices come back oldest due date first. Texts need the Two-Way Texting subscription and a client who opted in.

List invoices (list_invoices, read): Invoices with client, amount, due date, paid or unpaid and days past due.
Create invoice (create_invoice, write, asks first): Invoice a client for completed jobs, optionally emailing it right away.
Send text (send_text, write, asks first): Text message to a client with 2-Way Texting.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/service-autopilot-api-mcp-server#tools

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

What we store. The signed-in Service Autopilot browser profile, AES-256-GCM encrypted, in Finland. No password.
What your agent gets. The 14 Service Autopilot tools, never the session cookie.
What the session sees. What your login sees: clients, leads, jobs, routes, estimates, invoices.
What no tool touches. Card and ACH payments, payroll, QuickBooks sync settings, employees and deletes.
If Service Autopilot asks to verify. You type any sign-in code yourself. We never do.
How to cut access. Disable for agents, reset the browser, or change your Service Autopilot password.

Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results). We do not have a SOC 2 report or a third-party pentest yet.

Is it against Service Autopilot's terms? Account safety

with any robot, spider, crawler, scraper, or other manual or automated means or interface to access the Services, retrieve, index, scrape, "data mine" or otherwise gather content or extract user's information; to use or develop any third-party applications that interacts with the Services or users' content or information without Xplor's written consent

Xplor Acceptable Use Policy, section 4, last updated Feb 2022

The Service Autopilot Member Agreement (last modified 20 Feb 2024) binds you to that policy in 5.3.1. Under 5.4 Xplor may suspend access when it "reasonably suspects" a breach, and you keep paying fees while suspended. The policy calls any breach "a material breach of the master agreement". An agent in the web app is automated access, so the risk is real. We found no public case of a Service Autopilot account closed for automation (checked 27 Oct 2026).

How we keep your account looking like you:

Your own Service Autopilot login, signed in by you
One Cloud Browser with a fixed IP and cookies, not a new device per call
Estimates, invoices and texts wait for your OK
No tool deletes a client, job, estimate or invoice
If Xplor objects, we pause the Service Autopilot tools for everyone within 24 h

Texts go through your registered Two-Way Texting number. Send only to clients who opted in, and let a rain-day batch go out over a few minutes, not in one burst.

What happens when Service Autopilot changes?

12 h between tests of the Service Autopilot reads and drafts
24 h between tests of sends a client sees
$0 for a call to a Service Autopilot tool paused for repair

Service Autopilot ships release notes about once a month and runs two estimate screens side by side (the Beta toggle in CRM > Estimates). When a screen moves, we fix the tool and your prompts keep working. status.cotlet.dev checks the site, console and API every 3 minutes.

Approvals, undo and mistakes

Reads both days. list_jobs for the rained-out day and the target day, per crew.
Sorts the visits. Contract clients are listed for a skip; pay-as-you-go visits move.
Moves, then waits. reschedule_job per visit; each text waits in your Cotlet console.
Reports the run. Moved, skipped, full days, and clients with no cell number.

Action	Undo
Add a client or lead	Edit or remove it in Service Autopilot
Create a job	Reschedule it, or remove it in the app
Move a visit	One more reschedule_job moves it back
Create an estimate	Still a draft; edit it before sending
Create an invoice	Edit or delete it in the app while unpaid
Send an estimate, invoice or text	No, the client has it

3 of 14 tools ask first: send_estimate, create_invoice and send_text, the ones a client sees or your books carry. Reads, new clients, jobs, moves, notes and estimate drafts run at once. Switch the wait off per tool for a scheduled run.

A moved visit does not shift the repeating schedule: next week's visit stays on the old weekday, so a client moved to Friday may get two visits a few days apart. The run report flags those pairs.

MCP call:

{
  "name": "create_job",
  "arguments": {
    "client_id": "4410382",
    "service": "Mowing",
    "start_date": "2026-10-13",
    "recurrence": "weekly",
    "crew": "Crew 2",
    "price": "45.00",
    "instructions": "Side gate code 1234, back yard first."
  }
}

REST:

curl -X POST https://cotlet.dev/api/v1/service-autopilot/clients/4410382/jobs \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"service":"Mowing","start_date":"2026-10-13","recurrence":"weekly","crew":"Crew 2","price":"45.00","instructions":"Side gate code 1234, back yard first."}'

Response:

{
  "job_id": "9827514",
  "client_id": "4410382",
  "service": "Mowing",
  "recurrence": "weekly",
  "next_visit": "2026-10-13",
  "crew": "Crew 2",
  "price": "45.00",
  "status": "scheduled"
}

A script or an evening weather check reaches the same tools over REST at /api/v1/service-autopilot, with the same key and price. A call that fails, such as a service name your price list does not have, costs nothing. The tools table gives the REST path of each tool.

How much does the Service Autopilot MCP server cost?

About $24 a month for a lawn company with three crews, 4,210 credits. Service Autopilot still bills your plan as before.

Job	Calls	Credits
Read each crew's route, every workday	1 × 66	660
Rain day: move visits, text clients	25 × 3	750
New client with weekly mowing	3 × 12	360
Estimate from site notes, emailed	4 × 15	600
Invoice a finished one-time job	2 × 15	300
Unpaid invoices over 30 days, weekly	1 × 4	40
Cloud Browser, 30 days		1,500
Total		4,210

Free 7-day trial, no card
10 credits per successful call, MCP or REST
50 credits a day for the Cloud Browser
Works on Startup, Pro, Pro Plus and Elite

Service Autopilot plans run $49 (Startup), $199 (Pro) and $499 (Pro Plus) a month on annual terms, plus a sign-up fee (pricing page, 27 Oct 2026). The three crews, three rain days and the sign-up mix are our example. Dollars at the $29 pack rate.

Service Autopilot MCP server: GitHub, Zapier or hosted

Option	What it does	Where it stops
GitHub	No Service Autopilot MCP server, client or CLI. Searches return only Windows Autopilot projects.	Nothing to install.
Service Autopilot Automations	Built-in emails, texts and tasks on estimate, invoice and visit triggers.	Pro Plus; fixed rules, no requests in plain words.
Zapier webhook (Job Completed)	Sends each completed job to a spreadsheet or another app.	One event, out only; no reads of routes, estimates or invoices.
Supergood	Builds a private API or MCP server for an app without one, as a managed project.	Custom build per customer, no public price.

If you only need finished jobs in a spreadsheet, the Zapier webhook is free on Service Autopilot's side and official. For moving visits, building estimates and chasing invoices from an agent, there is no other ready option today.

Also listed on: Odel, mcpbeat

Who runs Cotlet

Cotlet is run by Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273). It has worked since 2019 and was founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Service Autopilot tools go to contact@cotlet.dev.

Service Autopilot API and MCP: questions

How do I get access?

Sign up free at https://cotlet.dev, open Service Autopilot under Integrations in the console and sign in at the Member Login in its Cloud Browser. The trial starts when you sign up, and no card is asked.

How do I connect Service Autopilot to ChatGPT or Claude?

Sign up at cotlet.dev, log in to Service Autopilot 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 Service Autopilot account through Cotlet, in their phone apps too.

What can ChatGPT do in Service Autopilot?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Service Autopilot: add a new client and set up recurring mowing; reschedule jobs after rain; create and send estimates from site visit notes. 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 Service Autopilot?

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

Can ChatGPT schedule a job in Service Autopilot?

Yes, with Cotlet. ChatGPT adds the client, creates the job and moves visits to a new day after rain, in your Service Autopilot account. You ask in plain words.

Can ChatGPT send an estimate in Service Autopilot?

Yes, with Cotlet. ChatGPT creates the estimate from your site visit notes and sends it to the client. Sending waits for your OK by default.

Which Service Autopilot plan do I need?

Cotlet works in your own office account, so it needs no API plan. Some features follow your plan: the vendor lists estimates and proposals on Pro, and Two-Way Texting is a paid add-on for Pro and Pro Plus members and included in Elite, so send_estimate and send_text work only where your account has them.

Does Service Autopilot have webhooks?

One: under Settings > Zapier Integrations you can send a Job Completed event to a webhook URL. There are no events for new clients, estimates or invoices. For anything else, run your agent on a schedule, for example a list_invoices pass every Monday.

Will the two-way Zapier link replace this?

Service Autopilot announced it as in progress in December 2025 with no date. If it ships, it will cover what Zapier actions cover; check it against the jobs you need, such as moving visits and building estimates.

Is the MCP server different from the REST API?

Only the way in differs. Both carry the same 14 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and HTTP steps use REST.

Is Cotlet affiliated with Service Autopilot?

No. Cotlet is independent and not affiliated with Service Autopilot, BACKTELL LLC or Xplor Technologies.

Can I use the Service Autopilot API without an AI agent?

Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.

Give your AI agents your signed-in browser.

Product: Integrations · How it works · Pricing · Security

Resources: Blog · API docs · Help center · Changelog · GitHub

Solutions: For developers · For automation agencies

Company: About · AI info: company facts · Contact

Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors

Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub

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

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.