[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)

# SuiteCRM API and MCP server

> Yes, SuiteCRM has a full REST API (v8) for records and relationships, but no official MCP server, and an admin must first create an OAuth2 client on your server (checked 23 Oct 2026).

Open-source CRM for sales, marketing and support: leads, accounts, contacts, opportunities, cases, tasks, calls and notes, mostly run on the company's own server.

## What is the SuiteCRM API?

Cotlet's SuiteCRM API exposes 12 endpoints for your own SuiteCRM account: list records, get a record, list related records, list case updates, create a lead, update a record, convert a lead, create a task, close a task, log a call, create a note and add a case update. The list_records endpoint returns list records of one module, filtered by text, status, owner or change date. Each endpoint takes simple JSON inputs like module, status or cursor and works both as an operation of the suitecrm_read or suitecrm_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Invoicing & freelance CRM](https://cotlet.dev/integrations/category/invoicing-freelance-crm.md)
- **Endpoints:** 12 (4 read, 8 write)
- **Updated:** 2026-10-20

Yes, SuiteCRM has a full REST API (v8) for records and relationships, but no official MCP server, and an admin must first create an OAuth2 client on your server (checked 23 Oct 2026). Cotlet is a hosted MCP server and REST API for SuiteCRM with 12 endpoints (4 read, 8 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does SuiteCRM have an official API?

Yes, SuiteCRM has a full REST API (v8) for records and relationships, but no official MCP server, and an admin must first create an OAuth2 client on your server (checked 23 Oct 2026).

| Task | SuiteCRM official | Cotlet |
|---|---|---|
| List and filter records in any module | Yes: Needs an OAuth2 client from an admin | Yes |
| Read one record and its related records | Yes: Relationship endpoints per link field | Yes |
| Create and update leads, accounts and opportunities | Yes | Yes |
| Convert a lead into contact, account and opportunity | Partly: The documented endpoints have no Convert Lead call; each record is created and linked separately | Yes |
| Create tasks, log calls and add notes | Yes | Yes |
| Post a case update that emails the contacts | Partly: The docs describe generic module calls, not the Case Updates thread or its email | Yes |
| Use it without an admin or a developer | No: An admin creates the OAuth2 client, and someone must write code against the API | Yes |
| Connect an AI agent over MCP | No | Yes |

Sources: [SuiteCRM Docs: API v8 endpoints](https://docs.suitecrm.com/developer/integration-api/v8/endpoints/), [SuiteCRM Docs: API v8 authentication](https://docs.suitecrm.com/developer/integration-api/v8/authentication/), [Zapier: SuiteCRM integrations](https://zapier.com/apps/suitecrm/integrations), [SuiteCRM Community: MCP integration request](https://community.suitecrm.com/t/mcp-integration/99298)

## Quick reference

```text
Yes, SuiteCRM has a full REST API (v8) for records and relationships, but no official MCP server, and an admin must first create an OAuth2 client on your server (checked 23 Oct 2026).
Cotlet provides a hosted MCP server and REST API for SuiteCRM: 12 tools (4 read, 8 write).
Access       Sign up at https://cotlet.dev/app/signup?app=suitecrm, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    suitecrm_read, suitecrm_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/suitecrm, each operation at its own route, e.g. POST /api/v1/suitecrm/leads
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   list_records, get_record, list_related, list_case_updates, create_lead, update_record, convert_lead, create_task, close_task, log_call, create_note, add_case_update
Confirm      convert_lead, add_case_update (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/suitecrm-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=suitecrm, requests SuiteCRM in the Cotlet console and creates an API key there.
2. The user signs in to SuiteCRM once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables SuiteCRM 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 SuiteCRM 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 SuiteCRM 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 SuiteCRM 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 SuiteCRM 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 SuiteCRM 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 SuiteCRM's terms; Cotlet is not affiliated with SuiteCRM.
```

## What can an AI agent do in SuiteCRM?

Cotlet is best for sales and support teams on a SuiteCRM instance who want an AI agent to convert leads, log calls and answer cases without running or fixing a server.

- **[Qualify and convert new leads](https://cotlet.dev/integrations/suitecrm-api-mcp-server/convert-qualified-leads.md)** (runs: daily): "Go through leads in SuiteCRM with status New. Convert the ones whose company has a website and a real contact email, create an opportunity for each, and mark obvious junk as Dead. Leave the rest for me." → `list_records`, `get_record`, `list_related`, `convert_lead`, `update_record`
- **[Log a call and set the follow-up](https://cotlet.dev/integrations/suitecrm-api-mcp-server/log-call-and-follow-up.md)** (runs: daily): "I just spoke to Tom Becker about the Northwind Dental deal for 25 minutes. Log the call on the opportunity with these notes, and add a High priority task to send the revised quote by Wednesday." → `get_record`, `log_call`, `create_note`, `create_task`
- **[Answer open support cases](https://cotlet.dev/integrations/suitecrm-api-mcp-server/answer-open-cases.md)** (runs: daily): "List open SuiteCRM cases assigned to me where the last update came from the customer. Draft a reply to each, and post the ones that only need a status answer. Keep the rest for me." → `list_records`, `list_case_updates`, `add_case_update`
- **[Review stale opportunities](https://cotlet.dev/integrations/suitecrm-api-mcp-server/review-stale-opportunities.md)** (runs: weekly): "Every Monday, list open opportunities with no activity in the last 14 days and a close date this month. Create a follow-up task on each one for its owner and show me the total amount at risk." → `list_records`, `list_related`, `create_task`, `update_record`
- **Daily to-do list from open tasks** (runs: daily): "Show my SuiteCRM tasks due today or overdue, by priority, and close the ones I tell you are done." → `list_records`, `close_task`

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

Yes. Cotlet does not replace your automation platform: it gives it a SuiteCRM 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 qualify and convert new leads, 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/suitecrm/records. | 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/suitecrm/records 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 SuiteCRM.

### list_records

List records of one module, filtered by text, status, owner or change date. Access: read. REST: `GET /api/v1/suitecrm/records`. MCP: `suitecrm_read → list_records`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `module` | string | yes | Module: Leads, Contacts, Accounts, Opportunities, Cases, Tasks, Calls, Meetings or Notes. |
| `query` | string | no | Text to match in the name or subject of the record. |
| `status` | string | no | Status or Sales Stage as shown in the module, for example New for Leads or Closed Won for Opportunities. |
| `assigned_to_me` | boolean | no | Only records assigned to you, the My Items filter. |
| `modified_since` | string | no | ISO date; only records changed on or after it. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns one page of records with record_id, the module's key fields and next_cursor. Records you cannot see under your role and Security Groups are not returned. Follow next_cursor until it is empty to read a whole queue.

Example response:

```json
{
  "module": "Leads",
  "records": [
    {
      "record_id": "5c1e7d0a-3b42-8f19-a6d4-2e7b90c1f3a8",
      "name": "Ana Lopez",
      "status": "New",
      "account_name": "Northwind Dental",
      "lead_source": "Website",
      "assigned_to": "Maya Chen"
    },
    {
      "record_id": "e91d3a77-0c5b-4d28-b6f1-7a2c8e4d9013",
      "name": "Sam Okafor",
      "status": "New",
      "account_name": "Birch Studio",
      "lead_source": "Trade Show",
      "assigned_to": "Maya Chen"
    }
  ],
  "next_cursor": null
}
```

### get_record

Read one record with all fields of its Detail View. Access: read. REST: `GET /api/v1/suitecrm/records/{record_id}`. MCP: `suitecrm_read → get_record`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `module` | string | yes | Module: Leads, Contacts, Accounts, Opportunities, Cases, Tasks, Calls, Meetings or Notes. |
| `record_id` | string | yes | Record ID from list_records. |

Returns the fields shown in the Detail View plus the IDs of the Account and Contact it links to. Fails with a not-found error if the record is deleted or hidden from your role.

Example response:

```json
{
  "module": "Opportunities",
  "record_id": "8f2a41c7-6d3e-90b5-17ac-4e5d0b9a2c61",
  "name": "Northwind Dental: onboarding",
  "account_id": "3d6b0f92-a1e4-47c8-8b25-c9e17f40a6d2",
  "sales_stage": "Proposal/Price Quote",
  "amount": 4800,
  "currency": "USD",
  "close_date": "2026-10-30",
  "probability": 65,
  "next_step": "Send revised quote",
  "contact_ids": [
    "d4a8e1b6-72c3-4f09-9a15-0b6e3c8f2d71"
  ]
}
```

### list_related

List what is linked to a record: activities, history, documents or contacts. Access: read. REST: `GET /api/v1/suitecrm/records/{record_id}/relateds`. MCP: `suitecrm_read → list_related`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `module` | string | yes | Module: Leads, Contacts, Accounts, Opportunities, Cases, Tasks, Calls, Meetings or Notes. |
| `record_id` | string | yes | Record ID from list_records. |
| `subpanel` | string | yes | One of: activities (open Calls, Meetings, Tasks, Emails), history (archived emails and completed activities), documents, contacts. |
| `cursor` | string | no | Next page cursor from the previous call. |

Reads the same tiles as the Relationships section of the record. Contacts exist on Opportunities and Cases, Documents on Leads, Opportunities and Cases, Activities and History on Leads, Opportunities and Cases. A tile the module does not have returns an error naming the valid ones.

Example response:

```json
{
  "record_id": "8f2a41c7-6d3e-90b5-17ac-4e5d0b9a2c61",
  "subpanel": "history",
  "items": [
    {
      "type": "Call",
      "subject": "Intro call with Tom Becker",
      "status": "Held",
      "date": "2026-10-08"
    },
    {
      "type": "Email",
      "subject": "Quote v1",
      "status": "Archived",
      "date": "2026-10-12"
    }
  ],
  "next_cursor": null
}
```

### list_case_updates

Read the Case Updates thread of one case. Access: read. REST: `GET /api/v1/suitecrm/case-updates`. MCP: `suitecrm_read → list_case_updates`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `case_id` | string | yes | Case ID from list_records. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the thread in chronological order with the author, whether it is a user or a contact, the text and whether it is internal. Internal updates are included, because you can see them in SuiteCRM.

Example response:

```json
{
  "case_id": "2b7e9c14-5a30-d8f6-41e2-9c0a7b3d5e18",
  "updates": [
    {
      "author": "Maria Silva",
      "author_type": "contact",
      "internal": false,
      "text": "The app still shows the old plan after the upgrade.",
      "created_at": "2026-10-22T21:14:00"
    },
    {
      "author": "Maya Chen",
      "author_type": "user",
      "internal": true,
      "text": "Checked billing, plan is correct, cache issue.",
      "created_at": "2026-10-23T08:02:00"
    }
  ],
  "next_cursor": null
}
```

### create_lead

Create a lead with its source and company. Access: write. REST: `POST /api/v1/suitecrm/leads`. MCP: `suitecrm_write → create_lead`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `last_name` | string | yes | Last name of the lead. |
| `first_name` | string | no | First name. |
| `account_name` | string | no | Company name, plain text until the lead is converted. |
| `email` | string | no | Email address. |
| `lead_source` | string | no | How the lead was acquired, for example Website, Trade Show or Cold Call. |
| `description` | string | no | Free text notes. |

Creates the lead with Status New, owned by your user. It reaches no one outside your team and is undone in one call with update_record setting Status to Dead, so it does not wait for your OK.

Example response:

```json
{
  "record_id": "5c1e7d0a-3b42-8f19-a6d4-2e7b90c1f3a8",
  "name": "Ana Lopez",
  "status": "New",
  "lead_source": "Website",
  "url": "https://crm.example.com/#/leads/record/5c1e7d0a-3b42-8f19-a6d4-2e7b90c1f3a8"
}
```

### update_record

Change fields of one record, for example Status, Sales Stage or Next Step. Access: write. REST: `PATCH /api/v1/suitecrm/records/{record_id}`. MCP: `suitecrm_write → update_record`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `module` | string | yes | Module: Leads, Contacts, Accounts, Opportunities, Cases, Tasks, Calls, Meetings or Notes. |
| `record_id` | string | yes | Record ID from list_records. |
| `fields` | object | yes | Field names and new values as in the record's Edit View, for example {"status": "Dead"}. |

Changes only the fields you pass and returns the record afterwards. It does not message anyone itself, but workflows your admin set up in SuiteCRM still run on the change. It is undone by changing the field back, so it does not wait for your OK.

Example response:

```json
{
  "module": "Leads",
  "record_id": "e91d3a77-0c5b-4d28-b6f1-7a2c8e4d9013",
  "changed": {
    "status": "Dead"
  },
  "updated_at": "2026-10-23T09:12:00"
}
```

### convert_lead

Convert a lead into a contact, an account and optionally an opportunity. Access: write, asks the user first. REST: `POST /api/v1/suitecrm/leads/{lead_id}/convert`. MCP: `suitecrm_write → convert_lead`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `lead_id` | string | yes | Lead ID from list_records. |
| `account_id` | string | no | Link to this existing Account instead of creating one. |
| `contact_id` | string | no | Link to this existing Contact instead of creating one. |
| `create_opportunity` | boolean | no | Also create an Opportunity. |
| `opportunity_name` | string | no | Name of the Opportunity. |
| `amount` | number | no | Expected value of the deal. |
| `close_date` | string | no | Expected close date, ISO date. Required by SuiteCRM when an opportunity is created. |
| `sales_stage` | string | no | Sales Stage, for example Prospecting or Qualification. |

Runs Convert Lead from the lead's Actions menu, with the sections pre-filled from the lead. If SuiteCRM shows a duplicate warning, nothing is created and the matching record is returned so you can pass its ID. The lead's Status becomes Converted, and several records are created, so this is not undone in one call. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "lead_id": "5c1e7d0a-3b42-8f19-a6d4-2e7b90c1f3a8",
  "status": "Converted",
  "contact_id": "d4a8e1b6-72c3-4f09-9a15-0b6e3c8f2d71",
  "account_id": "3d6b0f92-a1e4-47c8-8b25-c9e17f40a6d2",
  "opportunity_id": "8f2a41c7-6d3e-90b5-17ac-4e5d0b9a2c61",
  "duplicate_check": "no match"
}
```

### create_task

Create a task related to a record, with priority and due date. Access: write. REST: `POST /api/v1/suitecrm/tasks`. MCP: `suitecrm_write → create_task`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `subject` | string | yes | Name of the task. |
| `status` | string | no | One of: Not Started, In Progress, Completed, Pending Input, Deferred. |
| `priority` | string | no | One of: High, Medium, Low. |
| `due_date` | string | no | ISO date. |
| `related_to_module` | string | no | Module of the record it belongs to: Accounts, Contacts, Leads, Opportunities or Cases. |
| `related_to_id` | string | no | Record ID of the record it belongs to. |

Creates the task assigned to your user, shown in the Activities tile of the record it relates to. It reaches no one else and is undone in one call with close_task, so it does not wait for your OK.

Example response:

```json
{
  "task_id": "b6f3a290-1d84-4c7e-8e5a-2f9d0c71a4b3",
  "subject": "Send revised quote to Northwind Dental",
  "status": "Not Started",
  "priority": "High",
  "due_date": "2026-10-28",
  "related_to": {
    "module": "Opportunities",
    "id": "8f2a41c7-6d3e-90b5-17ac-4e5d0b9a2c61",
    "name": "Northwind Dental: onboarding"
  }
}
```

### close_task

Mark a task as done, like Close in the Actions menu. Access: write. REST: `POST /api/v1/suitecrm/tasks/{task_id}/close`. MCP: `suitecrm_write → close_task`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `task_id` | string | yes | Task ID from list_records. |

Runs Close from the task's Actions drop-down; the task moves to the History tile of its record. It reaches no one and can be reopened by update_record, so it does not wait for your OK.

Example response:

```json
{
  "task_id": "b6f3a290-1d84-4c7e-8e5a-2f9d0c71a4b3",
  "status": "Completed",
  "closed_at": "2026-10-23T09:40:00"
}
```

### log_call

Log a call on a record with direction, status, time and notes. Access: write. REST: `POST /api/v1/suitecrm/calls`. MCP: `suitecrm_write → log_call`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `subject` | string | yes | Subject of the call. |
| `direction` | string | yes | Inbound or Outbound. |
| `status` | string | yes | Planned, Held or Not Held. |
| `start` | string | yes | Start date and time, ISO 8601. |
| `duration_hours` | integer | no | Hours of duration. |
| `duration_minutes` | integer | no | Minutes of duration. |
| `related_to_module` | string | no | Module of the record it belongs to: Accounts, Contacts, Leads, Opportunities or Cases. |
| `related_to_id` | string | no | Record ID of the record it belongs to. |
| `description` | string | no | Notes of the call. |

Creates the call on the record you name, and it shows in its Activities or History tile by Status. It adds no invitees and sends no invitations, so it reaches no one and does not wait for your OK.

Example response:

```json
{
  "call_id": "f0c52d18-93ab-4e67-b1d4-6a8e2c5f7903",
  "subject": "Pricing questions with Tom Becker",
  "direction": "Outbound",
  "status": "Held",
  "start": "2026-10-22T14:30:00",
  "duration": "0h 25m",
  "related_to": {
    "module": "Opportunities",
    "id": "8f2a41c7-6d3e-90b5-17ac-4e5d0b9a2c61",
    "name": "Northwind Dental: onboarding"
  }
}
```

### create_note

Add a note to a record. Access: write. REST: `POST /api/v1/suitecrm/notes`. MCP: `suitecrm_write → create_note`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `subject` | string | yes | Subject of the note. |
| `note` | string | no | Note content. |
| `related_to_module` | string | no | Module of the record it belongs to: Accounts, Contacts, Leads, Opportunities or Cases. |
| `related_to_id` | string | no | Record ID of the record it belongs to. |

Creates a Note related to the record, visible to everyone who can see that record. It reaches no one by message and is undone by editing it, so it does not wait for your OK. Attachments are not uploaded.

Example response:

```json
{
  "note_id": "7a3c91e5-d2f8-4b06-a4c7-1e9b5d0f6c28",
  "subject": "Call notes: Tom Becker",
  "related_to": {
    "module": "Opportunities",
    "id": "8f2a41c7-6d3e-90b5-17ac-4e5d0b9a2c61"
  },
  "created_at": "2026-10-22T15:01:00"
}
```

### add_case_update

Post an update to a case thread, to the customer or as an internal note. Access: write, asks the user first. REST: `POST /api/v1/suitecrm/cases/{case_id}/update`. MCP: `suitecrm_write → add_case_update`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `case_id` | string | yes | Case ID from list_records. |
| `text` | string | yes | Text of the update. |
| `internal` | boolean | no | True for an Internal Update: seen only in SuiteCRM, not emailed to contacts. Defaults to false. |

Adds the update to the Case Updates thread. When internal is false, SuiteCRM sends an email notification to all Contacts related to the case, and a sent email cannot be recalled. Internal updates are not emailed or shown on the customer portal. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "update_id": "c58e0b3a-4f17-4d92-8a6e-3b1d7f9c2e40",
  "case_id": "2b7e9c14-5a30-d8f6-41e2-9c0a7b3d5e18",
  "internal": false,
  "emailed_contacts": 1,
  "created_at": "2026-10-23T09:20:00"
}
```

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

Connecting SuiteCRM takes three steps: sign up, sign in to SuiteCRM 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 SuiteCRM to your agent.

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

2. **Sign in to SuiteCRM in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to SuiteCRM 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 SuiteCRM 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.

```
Go through leads in SuiteCRM with status New. Convert the ones whose company has a website and a real contact email, create an opportunity for each, and mark obvious junk as Dead. Leave the rest for me.
```

### Call SuiteCRM 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/suitecrm 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/suitecrm/leads \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"last_name":"Lopez","first_name":"Ana","account_name":"Northwind Dental","email":"ana@northwind-dental.example","lead_source":"Website","description":"Asked for a demo through the contact form."}'
```

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

```
{
  "record_id": "5c1e7d0a-3b42-8f19-a6d4-2e7b90c1f3a8",
  "name": "Ana Lopez",
  "status": "New",
  "lead_source": "Website",
  "url": "https://crm.example.com/#/leads/record/5c1e7d0a-3b42-8f19-a6d4-2e7b90c1f3a8"
}
```

## Why use Cotlet for SuiteCRM?

**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 SuiteCRM 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 SuiteCRM changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect SuiteCRM to Cotlet?

Yes. You sign in to SuiteCRM yourself, in your own Cloud Browser, and we never save your password. Your agents only get SuiteCRM 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 SuiteCRM integration?**

No, Cotlet is independent of SuiteCRM. SuiteCRM's own API is too limited for this work. Cotlet works through your own SuiteCRM account, the way you use SuiteCRM 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 SuiteCRM in your console: your agents lose access at once and you stay signed in. Signing out of SuiteCRM in the browser works too, and Reset browser deletes the whole profile.

## Is there a SuiteCRM MCP server on GitHub?

Yes. Community SuiteCRM MCP servers exist on GitHub, usually maintained by one person. You install one yourself, create an OAuth2 client for it in your SuiteCRM admin, and keep it running; when SuiteCRM or your custom modules change, it stops working until you or the maintainer fix it. Cotlet hosts the same kind of server for you, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, ask an admin for an OAuth2 client, put its secret in a config file, add it to each MCP client | Sign up, sign in to SuiteCRM once with your own user, add one MCP server or API key |
| When SuiteCRM 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 SuiteCRM access | A client secret in a file on your computer, readable by any program you run | Your session in your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When the session expires | Tools fail until the token or the client is fixed by hand | Your Cloud Browser keeps you signed in; if SuiteCRM logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself | 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 SuiteCRM 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 SuiteCRM API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the SuiteCRM 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 10 credits (about $0.04 to $0.06), 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 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. [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 SuiteCRM 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 SuiteCRM 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 SuiteCRM only after you enable it. When SuiteCRM 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 SuiteCRM, sign out of SuiteCRM 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.
- **SuiteCRM's terms:** You use your own SuiteCRM account and stay responsible for following SuiteCRM's terms. Cotlet is independent and not affiliated with SuiteCRM. [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 SuiteCRM in the console and press Request access. Then you create your API key and connect SuiteCRM there.

**Do I need to be technical?**

No. You sign in to SuiteCRM 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 SuiteCRM to Cotlet?**

Yes. You sign in to SuiteCRM yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get SuiteCRM 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 SuiteCRM 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 SuiteCRM 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 SuiteCRM's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. SuiteCRM 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 SuiteCRM 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?**

SuiteCRM 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 an admin to create an OAuth2 client?**

No. Cotlet signs in to SuiteCRM as your own user, in your own Cloud Browser, so no OAuth2 client, keys or Admin access are needed. SuiteCRM's own API needs an admin to add a client under Admin > OAuth2 Clients and Tokens first.

**Which records can my agent see?**

The same as you. SuiteCRM roles decide what a user can do with a record, and Security Groups decide which records the user sees, so a lead outside your groups is not returned.

**Does it work with a SuiteCRM behind a firewall?**

Only if the instance can be reached over the internet from your Cloud Browser, which runs in the cloud. A SuiteCRM that is open only on an office network or behind a VPN cannot be reached.

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

No. Every call to convert_lead or add_case_update waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_lead, update_record, create_task, close_task, log_call and create_note run without asking, because they send nothing to anyone and one call undoes it.

**Can I use the SuiteCRM 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/suitecrm 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.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.