Service Fusion MCP Server

Emplois, clients, devis et factures dans votre compte Service Fusion.

Serveur MCP hébergé

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

S’installe dans Claude Code, Codex, Cursor et plus

Documentation

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

Service Fusion API and MCP server: Let your AI agent bill your finished Service Fusion jobs.

Service Fusion has an official REST API on the Pro plan and no official MCP server (checked 27 Oct 2026). The API lists, reads and creates customers, jobs and estimates; it cannot change a job status, convert an estimate, create an invoice or send anything. Cotlet runs 15 tools hosted on any plan, over MCP for agents and REST for scripts.

Jobs, customers, estimates and invoices in your Service Fusion account. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.

MCP setup REST API guide

What can you automate in Service Fusion?

  • Invoice completed jobs
  • Text or email invoices with a pay link
  • Turn tech notes into an estimate
  • Convert accepted estimates to jobs
  • Book web-form leads as jobs
  • Move jobs to Completed

Does Service Fusion have an MCP server or an API?

  • The API guide names three operations: get a list, get one record, create a record. Its model has no PUT, PATCH or DELETE, and invoices are read only.
  • Only Pro ($627 a month, or $533 billed yearly) lists "Open API Integration". Starter at $245 and Plus at $382 have no API and no Zapier connection.
  • Zapier has 6 triggers and 3 actions: Create Job, Create Customer and Create Calendar Task. There is no n8n node.
What you needOfficial APIZapierCotlet
Works on Starter and PlusPro onlyPro onlyYes, any plan
Find customers, jobs and estimatesYesTriggers on new recordsYes
Change a job statusNo update callsTrigger onlyYes, after your OK
Create and send an invoiceInvoices read onlyNo actionYes, after your OK
Allowed by Service FusionYes, officialYes, officialUses the web app

Checked 27 Oct 2026. Sources: Service Fusion API reference (v1), Service Fusion Help: Zapier, Service Fusion pricing, Zapier: Service Fusion integrations

How does Cotlet connect to Service Fusion?

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

We never keep your Service Fusion password, and no invoice, estimate or status change reaches a customer until you approve it.

Connect Service Fusion 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.

  1. Enable Service Fusion for agents. Create a Cotlet account, sign in to Service Fusion in its Cloud Browser with an office user, then press Enable for agents.
  2. Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 in your agent as a remote MCP server or a custom connector.
  3. Allow the connection. Chat apps open a Cotlet sign-in page. Code editors, n8n and scripts use an API key from the console instead.

The shared address https://cotlet.dev/mcp/v1 serves Service Fusion together with your other apps. Every Service Fusion plan has unlimited users, so you can give the agent its own office user and see its changes under that name. Refresh the connector after enabling Service Fusion so the new tools load.

Claude:

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

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

Codex:

# ~/.codex/config.toml
[mcp_servers.cotlet-service-fusion]
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_fusion_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_fusion_write

How to use the Service Fusion REST API

Create your Cotlet API key

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

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

Make your first Service Fusion API request

REST:

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

Read customers 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-fusion",
  "tool": "list_customers",
  "result": {
    "customers": [
      {
        "customer_id": "22814",
        "customer_name": "Jane Doe",
        "contact": {
          "first_name": "Jane",
          "last_name": "Doe",
          "phone": "555-0142",
          "email": "jane.doe@example.com"
        },
        "location": {
          "street_1": "48 Maple Court",
          "city": "Plano",
          "state_prov": "TX",
          "postal_code": "75024"
        },
        "tags": [
          "Residential"
        ],
        "last_serviced": "2026-04-18"
      }
    ],
    "page": 1
  }
}

Returns customers with their contacts, service location and last serviced date. Use it before create_customer to find a repeat caller by phone or email. create_job and create_estimate take the customer name exactly as shown here.

page: Page number. Default: 1.

The response includes a page number without a total or termination flag. Use the operation reference rather than inventing a cursor.

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

Service Fusion workflows for agents and automations

ToolConnect throughExample workflow
n8nHTTP RequestThe job statuses your account uses, with their type. Use list_job_statuses in your configured business report.
MakeHTTP > Make a requestJobs with number, status, customer, assigned techs and start date. Use list_jobs in your configured business report.
Python or Node.jsREST APIInvoices with number, customer, total, date, paid flag and pay-online link. Use list_invoices 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 Fusion; 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 Fusion API endpoints and MCP tools

Customers and leads

Search by phone or email before adding anyone: a second account under the same name breaks the QuickBooks sync. A new customer reaches nobody, so it runs at once.

  • List customers (list_customers, read): Customers matching a name, phone, email, address or tag, with last serviced date.
  • Create customer (create_customer, write): New customer with a primary contact and service location.

Jobs and statuses

Status names are your own, read from list_job_statuses. A new job can email the customer when your Outbound Email Settings say so, and Completed stops the labor clock, so both ask first.

  • List job statuses (list_job_statuses, read): The job statuses your account uses, with their type.
  • List jobs (list_jobs, read): Jobs with number, status, customer, assigned techs and start date.
  • Get job (get_job, read): Full job: description, location, techs, products, services, notes and charges.
  • Create job (create_job, write, asks first): New job for a customer, scheduled or unscheduled, optionally with technicians assigned.
  • Update job status (update_job_status, write, asks first): Move a job to another status, e.g. On The Way, Completed or Cancelled.

Estimates

Up to five options per estimate. A draft reaches nobody; sending and converting ask first, and each converted option becomes its own job.

  • List estimates (list_estimates, read): Estimates with number, status, customer, requested date and options.
  • Get estimate (get_estimate, read): Estimate with each option, its line items and total.
  • Create estimate (create_estimate, write): New estimate for a customer with products and services. Nothing is sent until send_estimate.
  • Send estimate (send_estimate, write, asks first): Email or text an estimate with a link to view and accept it online.
  • Convert estimate to job (convert_estimate_to_job, write, asks first): Turn one estimate option into a job, the way Convert to Job does in the app.

Invoices

One job per invoice. By default only Completed or closed jobs can be invoiced. Sends carry the pay-online link.

  • List invoices (list_invoices, read): Invoices with number, customer, total, date, paid flag and pay-online link.
  • Create invoice (create_invoice, write, asks first): Invoice a job from its products, services and charges. Nothing is sent or charged.
  • Send invoice (send_invoice, write, asks first): Email or text an invoice with a link to view and pay it online.

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

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

  • What we store. The signed-in Service Fusion browser profile, AES-256-GCM encrypted, in Finland. No password.
  • What your agent gets. The 15 Service Fusion tools, never the session cookie.
  • What the session sees. What your office user sees: customers, jobs, estimates, invoices.
  • What no tool touches. Payments, refunds, QuickBooks sync, user permissions and deletes.
  • If Service Fusion asks to verify. You type any sign-in code yourself. We never do.
  • How to cut access. Disable for agents, reset the browser, or deactivate the agent's user in Service Fusion.

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 Fusion's terms? Account safety

apply systems to extract or modify information in the Services using technology or method such as those commonly referred to as "web scraping," "data scraping," or "screen scraping"

Service Fusion Subscription Agreement, 2.5(c), last modified 23 Mar 2026

Section 2.9 lets Service Fusion suspend the service at once for "unauthorized or non-compliant use", and section 5 bars "the extraction of data from the Services" without written consent. Clause 2.5(j) does allow access by "contractors who are acting on your behalf". An agent working in the web app could still be read as scraping, and on Pro the official API is the sanctioned route for reads and creates. We found no public case of a Service Fusion account closed for automation (checked 27 Oct 2026).

How we keep your account looking like you:

  • Your own Service Fusion user, signed in by you
  • One Cloud Browser with a fixed IP and cookies, not a new device per call
  • Status changes, invoices and every send wait for your OK
  • No tool deletes a customer, job, estimate or invoice
  • If Service Fusion objects, we pause the Service Fusion tools for everyone within 24 h

Texts to customers follow Service Fusion's messaging consent. Send to customers who opted in, and spread a big invoice run over the day.

What happens when Service Fusion changes?

  • 12 h between tests of the Service Fusion reads and drafts
  • 24 h between tests of sends and status changes a customer sees
  • $0 for a call to a Service Fusion tool paused for repair

Service Fusion lets each account rename its job and estimate statuses, so the tools read your names from list_job_statuses instead of guessing. 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

  1. Collects finished jobs. list_jobs with Completed, skipping Invoiced and Paid In Full.
  2. Checks each one. get_job: a job with an invoice number or a zero total is set aside.
  3. Waits for your OK. Each invoice and send shows up in your Cotlet console first.
  4. Reports the run. Invoice numbers, totals, channel, and the jobs left for the office.
ActionUndo
Create a customer, job or estimateEdit or delete it in Service Fusion
Change a job statusSet it back; a text sent on On The Way is out
Convert an estimateCancel or delete the new job in Service Fusion
Create an invoiceEdit or remove it in Service Fusion while unsent and unpaid
Send an estimate or invoiceNo, the customer has the link

6 of 15 tools ask first: create_job, update_job_status, convert_estimate_to_job, create_invoice, send_estimate and send_invoice, the ones a customer or your books feel. Reads, new customers and estimate drafts run at once. Switch the wait off per tool for a scheduled run.

A texted estimate stays at Estimate Requested; Service Fusion moves it to Estimate Provided only after an email. Go by the run report for follow-up calls.

MCP call:

{
  "name": "create_job",
  "arguments": {
    "customer_name": "Jane Doe",
    "description": "AC tune-up, upstairs unit",
    "category": "Maintenance",
    "start": "2026-10-15T09:00:00-05:00",
    "duration_minutes": 90
  }
}

REST:

curl -X POST https://cotlet.dev/api/v1/service-fusion/jobs \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"customer_name":"Jane Doe","description":"AC tune-up, upstairs unit","category":"Maintenance","start":"2026-10-15T09:00:00-05:00","duration_minutes":90}'

Response:

{
  "job_id": "1048213",
  "number": "10482",
  "status": "Scheduled",
  "customer_name": "Jane Doe",
  "description": "AC tune-up, upstairs unit",
  "category": "Maintenance",
  "start": "2026-10-15T09:00:00-05:00",
  "duration_minutes": 90,
  "techs_assigned": []
}

A script or a nightly job reaches the same tools over REST at /api/v1/service-fusion, with the same key and price. A call that fails, such as invoicing a job that is not Completed yet, costs nothing. The tools table gives the REST path of each tool.

How much does the Service Fusion MCP server cost?

About $30 a month for a shop billing about 60 jobs a month, 5,210 credits. Service Fusion still bills your plan as before.

JobCallsCredits
Invoice a completed job and send it3 × 601,800
List jobs ready to bill, each workday1 × 22220
New lead to customer and job3 × 30900
Estimate from tech notes, texted3 × 15450
Convert an accepted estimate2 × 12240
Mark a named job Completed1 × 10100
Cloud Browser, 30 days1,500
Total5,210
  • Free 7-day trial, no card
  • 10 credits per successful call, MCP or REST
  • 50 credits a day for the Cloud Browser
  • No Pro upgrade, any plan you can sign in to

Service Fusion counts 5M+ jobs a year across 6,500+ customers, about 64 jobs a month per account; the lead and estimate mix is our example. The step from Plus to Pro alone is $245 a month. Dollars at the $29 pack rate.

Service Fusion MCP server: official API, GitHub or hosted

OptionWhat it doesWhere it stops
SinthetikIndustries/Service-Fusion-MCPCommunity MCP server on npm, MIT, 0 stars, last commit 2 Sep 2026. Wraps every documented API resource."Read/create operations only". Needs API credentials, so Pro, and runs on your own computer.
Zapier MCPCreate Job, Create Customer and Create Calendar Task as MCP tools.Pro plan, three actions, no reads, estimates or invoices.
rashidazarang/servicefusion-adapterTypeScript client for the REST API, 1 star.A library, no MCP; last commit 9 Sep 2025.
Apify Service Fusion actorReads jobs, customers, estimates and invoices.Read only, one user.

On Pro, if your agent only needs to look things up and add records, the community server on the official API is free and you run it. Status changes, invoices, conversions and sends are in no API, and Starter and Plus have none at all: that is where Cotlet fits.

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). Send questions about the Service Fusion tools to contact@cotlet.dev.

Service Fusion API and MCP: questions

How do I get access?

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

How do I connect Service Fusion to ChatGPT or Claude?

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

What can ChatGPT do in Service Fusion?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Service Fusion: create customers and jobs from new leads; list unscheduled jobs; invoice completed jobs. You ask in plain words, and anything that reaches other people waits for your OK first.

Do I need the Pro plan to use Service Fusion with Cotlet?

No. The Open API is included only in Pro (checked 11 Oct 2026), but Cotlet signs in to your account in a browser the way you do, so Starter and Plus accounts work too. What it can do is what your user can do in the app.

Why can an invoice not be created for my job?

By default Service Fusion only invoices a job that is Completed or closed. The Allow Invoicing Prior To Job Completion setting in My Office > Company Preferences changes that.

Does Service Fusion have webhooks?

Not in its API. The only event feeds are Zapier triggers such as Job Status Updated and New Invoice, on Pro. Without them, run your agent on a schedule, for example a list_jobs pass each evening.

Can I use the official API and Cotlet together?

Yes. On Pro, keep the API or Zapier for record sync and connect Cotlet to the same agent for status changes, invoices and sends.

Is the MCP server different from the REST API?

Only the way in differs. Both carry the same 15 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 Fusion?

No. Cotlet is independent and not affiliated with Service Fusion (FSM Technologies, LLC) or EverCommerce.

Can I use the Service Fusion 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.