[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.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)

# Simpro API and MCP server

> Simpro has a full REST API with OAuth 2.0 for quotes, jobs, schedules, customers and catalogue items, but no official MCP server (checked 17 Oct 2026). Your administrator creates the API credentials in your build, partner apps need approval from Simpro, and all calls share a limit of 10 per second per build.

Field service and job management software for trade businesses: quotes, jobs, scheduling, timesheets, a materials catalogue and invoicing in one system, with the Simpro Mobile and Connect apps for the field.

## What is the Simpro API?

Cotlet's Simpro API exposes 12 endpoints for your own Simpro account: search customers, get customer, list quotes, get quote, list jobs, get job, get schedule, search catalogue items, create quote, convert quote to job, update job status and add schedule entry. The search_customers endpoint returns find customers by name, email or phone. Each endpoint takes simple JSON inputs like page, customer_id or status and works both as an operation of the simpro_read or simpro_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Local services & SaaS](https://cotlet.dev/integrations/category/local-services-saas.md)
- **Endpoints:** 12 (8 read, 4 write)
- **Updated:** 2026-10-16

Simpro has a full REST API with OAuth 2.0 for quotes, jobs, schedules, customers and catalogue items, but no official MCP server (checked 17 Oct 2026). Cotlet is a hosted MCP server and REST API for Simpro with 12 endpoints (8 read, 4 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Simpro have an official API?

Simpro has a full REST API with OAuth 2.0 for quotes, jobs, schedules, customers and catalogue items, but no official MCP server (checked 17 Oct 2026). Your administrator creates the API credentials in your build, partner apps need approval from Simpro, and all calls share a limit of 10 per second per build.

| Task | Simpro official | Cotlet |
|---|---|---|
| List and read jobs | Yes: REST API; you handle paging, 30 results by default and 250 at most | Yes |
| Look up customers | Yes: REST API; company and individual customers | Yes |
| Create a quote | Yes: REST API; no MCP server for agents | Yes |
| Convert a quote to a job | Yes: REST API convert call with no body; the job links back to the quote | Yes |
| Update a job status | Yes: REST API status codes; your workflow settings decide what the app does next | Yes |
| Check the schedule | Yes: REST API schedules; you combine jobs, quotes and employees yourself | Yes |
| Add a schedule entry for an employee | Yes: REST API job cost centre schedules | Yes |
| Search catalogue items | Yes: REST API catalogs; you handle paging and rate limit | Yes |

Sources: [Simpro API forum: API Rate Limiting Update](https://apiforum.simprogroup.com/viewtopic.php?t=2902), [Simpro API forum: Converting Quotes to Jobs via API](https://apiforum.simprogroup.com/viewtopic.php?t=3606), [Simpro: Zapier Integration](https://www.simprogroup.com/partners/integration-partners/zapier), [Simpro developer portal](https://developer.simprogroup.com)

## For AI agents

```text
Simpro has a full REST API with OAuth 2.0 for quotes, jobs, schedules, customers and catalogue items, but no official MCP server (checked 17 Oct 2026). Your administrator creates the API credentials in your build, partner apps need approval from Simpro, and all calls share a limit of 10 per second per build.
Cotlet provides a hosted MCP server and REST API for Simpro: 12 tools (8 read, 4 write).
Access       Sign up at https://cotlet.dev/app/signup?app=simpro, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    simpro_read, simpro_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/simpro, each operation at its own route, e.g. POST /api/v1/simpro/quotes/{quote_id}/to-job/convert
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   search_customers, get_customer, list_quotes, get_quote, list_jobs, get_job, get_schedule, search_catalogue_items, create_quote, convert_quote_to_job, update_job_status, add_schedule_entry
Confirm      create_quote, convert_quote_to_job, update_job_status, add_schedule_entry (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/simpro-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=simpro, requests Simpro in the Cotlet console and creates an API key there.
2. The user signs in to Simpro once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Simpro for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Simpro server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Simpro MCP server instead.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to Simpro in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Simpro only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no Simpro login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following Simpro's terms; Cotlet is not affiliated with Simpro.
```

## What can an AI agent do in Simpro?

Cotlet is best for trade business owners and office managers who want an AI agent to convert quotes, draft new ones and log time in Simpro without running or fixing a server, or building an API application.

- **[Convert accepted quotes to jobs](https://cotlet.dev/integrations/simpro-api-mcp-server/convert-accepted-quotes-to-jobs.md)** (runs: daily): "Look at the Simpro quotes I sent this month. For each one the customer has accepted, convert it to a job and tell me the new job number. Leave any quote that is not clearly accepted." → `list_quotes`, `get_quote`, `convert_quote_to_job`, `get_job`
- **[Draft quotes from customer requests](https://cotlet.dev/integrations/simpro-api-mcp-server/draft-quotes-from-customer-requests.md)**: "A customer, Harbour Dental, asked for a quote to replace the hot water unit at 12 Pier Rd. Find them in Simpro, find the site, and create a draft quote with that description due Friday. Show me before you create it." → `search_customers`, `get_customer`, `search_catalogue_items`, `create_quote`
- **[Log technician time on jobs](https://cotlet.dev/integrations/simpro-api-mcp-server/log-technician-time-on-jobs.md)**: "Add yesterday's time to Simpro: Sam worked 8:00 to 11:30 on job 20871, the plumbing cost centre. Check the job first, and show me the entry before you add it." → `get_job`, `get_schedule`, `add_schedule_entry`
- **Brief the team on tomorrow's schedule** (runs: daily): "Check tomorrow's schedule in Simpro. For each employee list their jobs with the site and customer, and flag anyone with nothing booked." → `get_schedule`, `get_job`, `get_customer`
- **Find catalogue items for a job**: "Search the Simpro catalogue for 20 mm copper pipe fittings and show the item names with their IDs, so I can use them on a quote." → `search_catalogue_items`

## Can Simpro automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Simpro connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to convert accepted quotes to jobs, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/simpro/quotes. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/simpro/quotes with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 12 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Simpro.

### search_customers

Find customers by name, email or phone. Access: read. REST: `GET /api/v1/simpro/customers/search`. MCP: `simpro_read → search_customers`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | yes | Name, email address or phone number. |
| `page` | integer | no | Page number, starting at 1. |

Returns matching company and individual customers with ID, name and the sites on record, best match first. Pages through the result. A customer is found only if it exists in your Simpro build. Your Simpro permissions decide which customers appear.

Example response:

```json
{
  "results": [
    {
      "customer_id": 3318,
      "type": "company",
      "name": "Harbour Dental",
      "sites": [
        {
          "site_id": 5107,
          "name": "12 Pier Rd"
        }
      ]
    }
  ],
  "page": 1,
  "has_more": false
}
```

### get_customer

Read one customer with contacts and sites. Access: read. REST: `GET /api/v1/simpro/customers/{customer_id}`. MCP: `simpro_read → get_customer`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `customer_id` | integer | yes | Customer ID from search_customers. |

Returns the customer record with contacts and every site, so a quote can be put on the right address. Read only.

Example response:

```json
{
  "customer_id": 3318,
  "type": "company",
  "name": "Harbour Dental",
  "contacts": [
    {
      "name": "Priya Nair",
      "email": "priya@harbourdental.example"
    }
  ],
  "sites": [
    {
      "site_id": 5107,
      "name": "12 Pier Rd"
    },
    {
      "site_id": 5120,
      "name": "40 Dock St"
    }
  ]
}
```

### list_quotes

List quotes, optionally by status or customer. Access: read. REST: `GET /api/v1/simpro/quotes`. MCP: `simpro_read → list_quotes`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | string | no | A quote status name from your build. |
| `customer_id` | integer | no | Only quotes for this customer. |
| `page` | integer | no | Page number, starting at 1. |

Returns quotes with number, customer, site, status and total, newest first. Pages until the list ends. The status filter uses the status names set up in your build.

Example response:

```json
{
  "quotes": [
    {
      "quote_id": 10442,
      "customer": "Harbour Dental",
      "site": "12 Pier Rd",
      "status": "Accepted",
      "total": 4180
    }
  ],
  "page": 1,
  "has_more": true
}
```

### get_quote

Read one quote with status, totals and linked job. Access: read. REST: `GET /api/v1/simpro/quotes/{quote_id}`. MCP: `simpro_read → get_quote`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `quote_id` | integer | yes | Quote ID from list_quotes. |

Returns the customer, site, description, status, total and, if the quote was converted, the job it became. Read only.

Example response:

```json
{
  "quote_id": 10442,
  "customer": "Harbour Dental",
  "site": "12 Pier Rd",
  "description": "Replace hot water unit",
  "status": "Accepted",
  "total": 4180,
  "converted_job_id": null
}
```

### list_jobs

List jobs, optionally by status, customer or date. Access: read. REST: `GET /api/v1/simpro/jobs`. MCP: `simpro_read → list_jobs`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | string | no | A job status name from your build. |
| `customer_id` | integer | no | Only jobs for this customer. |
| `date_from` | string | no | ISO date; only jobs created on or after it. |
| `page` | integer | no | Page number, starting at 1. |

Returns jobs with number, customer, site, status and stage, newest first. Pages until the list ends. Stage and status are separate fields in Simpro, and the status filter uses your own status names.

Example response:

```json
{
  "jobs": [
    {
      "job_id": 20871,
      "customer": "Harbour Dental",
      "site": "12 Pier Rd",
      "status": "Pending",
      "stage": "Pending"
    }
  ],
  "page": 1,
  "has_more": false
}
```

### get_job

Read one job with its sections and cost centres. Access: read. REST: `GET /api/v1/simpro/jobs/{job_id}`. MCP: `simpro_read → get_job`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | integer | yes | Job ID from list_jobs. |

Returns the customer, site, status, stage and the sections with their cost centres, which add_schedule_entry needs. If the job came from a quote, the quote ID is included. Read only.

Example response:

```json
{
  "job_id": 20871,
  "customer": "Harbour Dental",
  "site": "12 Pier Rd",
  "status": "Pending",
  "stage": "Pending",
  "converted_from_quote_id": 10442,
  "sections": [
    {
      "section_id": 1,
      "cost_centres": [
        {
          "cost_centre_id": 2,
          "name": "Plumbing"
        }
      ]
    }
  ]
}
```

### get_schedule

Read scheduled time for a day, by employee. Access: read. REST: `GET /api/v1/simpro/schedule`. MCP: `simpro_read → get_schedule`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `date` | string | yes | ISO date. |
| `employee_id` | integer | no | Only this employee. |

Returns the schedule blocks for one day with employee, job or quote, cost centre and start and end times. Pass an employee to read one person. Read only.

Example response:

```json
{
  "date": "2026-10-17",
  "blocks": [
    {
      "schedule_id": 66101,
      "employee": "Sam Ortiz",
      "job_id": 20871,
      "cost_centre": "Plumbing",
      "start": "08:00",
      "end": "11:30"
    }
  ]
}
```

### search_catalogue_items

Find items in your materials catalogue by name or part number. Access: read. REST: `GET /api/v1/simpro/catalogue-items/search`. MCP: `simpro_read → search_catalogue_items`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | yes | Item name or part number. |
| `page` | integer | no | Page number, starting at 1. |

Returns matching items with ID, name and part number. Pages through the result. Your catalogue is the one in your build, so only items you have set up appear. Read only.

Example response:

```json
{
  "items": [
    {
      "item_id": 7712,
      "name": "Copper pipe fitting 20 mm",
      "part_number": "CPF-20"
    }
  ],
  "page": 1,
  "has_more": false
}
```

### create_quote

Create a draft quote for a customer and site. Access: write, asks the user first. REST: `POST /api/v1/simpro/customers/{customer_id}/quotes`. MCP: `simpro_write → create_quote`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `customer_id` | integer | yes | Customer ID from search_customers. |
| `site_id` | integer | yes | Site ID from get_customer. |
| `description` | string | yes | What the quote is for. |
| `due_date` | string | no | ISO date the quote is due. |
| `order_no` | string | no | The customer's order or request number. |

Creates a quote on an existing customer and site and returns its number. Pricing is not added; you finish it in Simpro. The customer and site must already exist. The quote shows in your Simpro quote list for your office. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "quote_id": 10451,
  "customer": "Harbour Dental",
  "site": "12 Pier Rd",
  "description": "Replace hot water unit",
  "due_date": "2026-10-23",
  "status": "New"
}
```

### convert_quote_to_job

Turn a quote into a job. Access: write, asks the user first. REST: `POST /api/v1/simpro/quotes/{quote_id}/to-job/convert`. MCP: `simpro_write → convert_quote_to_job`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `quote_id` | integer | yes | Quote ID from list_quotes. |

Converts the quote and returns the new job, which links back to the quote. A quote that was converted already is refused. The job then appears for scheduling in your build. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "quote_id": 10442,
  "job_id": 20871,
  "converted_from_quote_id": 10442,
  "status": "Pending"
}
```

### update_job_status

Set the status of a job. Access: write, asks the user first. REST: `PATCH /api/v1/simpro/jobs/{job_id}/status`. MCP: `simpro_write → update_job_status`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | integer | yes | Job ID from list_jobs. |
| `status` | string | yes | A status name from your build. |

Sets the status to one of the status names in your build and returns the job. What Simpro does next follows your own status settings, and some statuses may be changed again by your workflow. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "job_id": 20871,
  "status": "In Progress",
  "previous_status": "Pending"
}
```

### add_schedule_entry

Schedule an employee on a job cost centre for a time block. Access: write, asks the user first. REST: `POST /api/v1/simpro/jobs/{job_id}/schedule-entries`. MCP: `simpro_write → add_schedule_entry`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | integer | yes | Job ID from list_jobs. |
| `section_id` | integer | yes | Section ID from get_job. |
| `cost_centre_id` | integer | yes | Cost centre ID from get_job. |
| `employee_id` | integer | yes | Employee ID from get_schedule. |
| `date` | string | yes | ISO date. |
| `start_time` | string | yes | HH:MM, 24 hour. |
| `end_time` | string | yes | HH:MM, 24 hour. |

Creates a schedule block for one employee on a job, section and cost centre and returns it. If timesheets are locked for that date, Simpro refuses it. The block shows in that employee's schedule. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "schedule_id": 66120,
  "job_id": 20871,
  "cost_centre": "Plumbing",
  "employee": "Sam Ortiz",
  "date": "2026-10-16",
  "start": "08:00",
  "end": "11:30"
}
```

## How do I connect Simpro to Claude Code, Codex or Cursor?

Connecting Simpro takes three steps: sign up, sign in to Simpro once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect Simpro to your agent.

1. **Create an account** Sign up and add Simpro in the console. Your API key is there too.

2. **Sign in to Simpro in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Simpro there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Simpro tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Look at the Simpro quotes I sent this month. For each one the customer has accepted, convert it to a job and tell me the new job number. Leave any quote that is not clearly accepted.
```

### Call Simpro from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/simpro with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X POST https://cotlet.dev/api/v1/simpro/quotes/10442/to-job/convert \
  -H "Authorization: Bearer $COTLET_API_KEY"
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "quote_id": 10442,
  "job_id": 20871,
  "converted_from_quote_id": 10442,
  "status": "Pending"
}
```

## Why use Cotlet for Simpro?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Simpro yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When Simpro changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Simpro to Cotlet?

Yes. You sign in to Simpro yourself, in your own Cloud Browser, and we never save your password. Your agents only get Simpro once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official Simpro integration?**

No, Cotlet is independent of Simpro. Simpro's own API is too limited for this work. Cotlet works through your own Simpro account, the way you use Simpro in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to Simpro in your console: your agents lose access at once and you stay signed in. Signing out of Simpro in the browser works too, and Reset browser deletes the whole profile.

## Is there a Simpro MCP server on GitHub?

Yes. Community Simpro MCP servers exist on GitHub, usually maintained by one person. You install one yourself, create API credentials in your build, and fix it when the API changes. Cotlet hosts the same kind of server for you, signs in as you, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, create an API application and credentials in Simpro, store the secret, add the server to each MCP client | Sign up, sign in to Simpro once, add one MCP server or API key |
| When Simpro changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your Simpro access | Client secret or token in a file on your computer, readable by any program you run | Signed in inside your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When access expires | Tools fail until you renew the token or sign in again by hand | Your Cloud Browser keeps you signed in; if Simpro logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself, including the rate limit | Nothing to host or update |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Simpro changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Simpro API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Simpro API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $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. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Simpro account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to Simpro yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Simpro only after you enable it. When Simpro signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to Simpro, sign out of Simpro in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Simpro's terms:** You use your own Simpro account and stay responsible for following Simpro's terms. Cotlet is independent and not affiliated with Simpro. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open Simpro in the console and press Request access. Then you create your API key and connect Simpro there.

**Do I need to be technical?**

No. You sign in to Simpro once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect Simpro to Cotlet?**

Yes. You sign in to Simpro yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Simpro once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My Simpro sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Simpro cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through Simpro's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Simpro sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no Simpro login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

Simpro offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Do I need to create an API application in Simpro for Cotlet?**

No. Cotlet works through your own Simpro login, so you do not create API credentials in your build and do not apply as a partner. The official API needs credentials created by an administrator, and partner apps need approval from Simpro (Simpro developer portal, checked 17 Oct 2026).

**Does the Simpro rate limit apply to my agent?**

Simpro limits its API to 10 calls per second per build and answers HTTP 429 above it (Simpro API forum, 2025). Cotlet works through your signed-in session, not through the API application.

**Can my agent post or send messages in Simpro without asking me?**

No. Every call to create_quote, convert_quote_to_job, update_job_status or add_schedule_entry waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals.

**Can I use the Simpro API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/simpro from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.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 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.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.