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

# Vtiger API and MCP server

> Yes, Vtiger has a REST API, but its limits table lists 0 requests for One Pilot and 24,000 a day (30 a minute) for One Growth, and Vtiger has no official MCP server (checked 22 Oct 2026).

CRM for sales, support and marketing teams: contacts, organizations, deals in pipelines, support cases with SLAs, quotes and invoices, with workflows on top.

## What is the Vtiger API?

Cotlet's Vtiger API exposes 10 endpoints for your own Vtiger account: list contacts, list deals, get deal, list cases, get case, create contact, convert contact to deal, update deal stage, create case and update case. The list_contacts endpoint returns contacts of your CRM with organization, lifecycle stage and owner; leads too when the Leads module is on. Each endpoint takes simple JSON inputs like assigned_to, record_id or lifecycle_stage and works both as an operation of the vtiger_read or vtiger_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:** 10 (5 read, 5 write)
- **Updated:** 2026-10-20

Yes, Vtiger has a REST API, but its limits table lists 0 requests for One Pilot and 24,000 a day (30 a minute) for One Growth, and Vtiger has no official MCP server (checked 22 Oct 2026). Cotlet is a hosted MCP server and REST API for Vtiger with 10 endpoints (5 read, 5 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Vtiger have an official API?

Yes, Vtiger has a REST API, but its limits table lists 0 requests for One Pilot and 24,000 a day (30 a minute) for One Growth, and Vtiger has no official MCP server (checked 22 Oct 2026).

| Task | Vtiger official | Cotlet |
|---|---|---|
| List contacts, deals and cases | Partly: REST API on editions with a limit above 0; no MCP server | Yes |
| Create a contact | Partly: REST API, same editions; Zapier has Create or Update Contact | Yes |
| Convert a lead or contact into a deal | Partly: Records can be created by API; the Convert screen is the CRM path, and Zapier has no conversion action | Yes |
| Move a deal to another sales stage or pipeline | Partly: REST API, same editions; Zapier has Create or Update Opportunity | Yes |
| Create a case, with or without an email to the customer | Partly: REST API and Zapier Create Case; the Send Email tab is a CRM screen | Yes |
| Set a case group, priority, status or SLA | Partly: REST API, same editions; Zapier has no update action for cases | Yes |
| Use it on the free One Pilot edition | No: The limits table shows 0 requests for One Pilot | Yes |
| Connect an AI agent without writing code | No: No official MCP server | Yes |

Sources: [Vtiger Help: API limits per edition](https://help.vtiger.com/faq/146868966-What-are-the-API-Limits-as-per-editions-in-Vtiger-CRM), [Vtiger Help: Where can I find the Access Key for Web Services](https://help.vtiger.com/faq/146631436-Where-can-I-find-the-Access-Key-for-Web-Services), [Vtiger Application Platform: REST API](https://vtap.vtiger.com/platform/rest-apis.html), [Vtiger on Zapier](https://zapier.com/apps/vtiger/integrations)

## For AI agents

```text
Yes, Vtiger has a REST API, but its limits table lists 0 requests for One Pilot and 24,000 a day (30 a minute) for One Growth, and Vtiger has no official MCP server (checked 22 Oct 2026).
Cotlet provides a hosted MCP server and REST API for Vtiger: 10 tools (5 read, 5 write).
Access       Sign up at https://cotlet.dev/app/signup?app=vtiger, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    vtiger_read, vtiger_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/vtiger, each operation at its own route, e.g. PATCH /api/v1/vtiger/records/{record_id}/deal-stage
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_contacts, list_deals, get_deal, list_cases, get_case, create_contact, convert_contact_to_deal, update_deal_stage, create_case, update_case
Confirm      create_contact, convert_contact_to_deal, update_deal_stage, create_case, update_case (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/vtiger-api-mcp-server.md

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

## What can an AI agent do in Vtiger?

Cotlet is best for Vtiger sales and support teams who want an AI agent to convert leads, move deals and triage cases without running or fixing a server.

- **[Convert qualified leads to deals](https://cotlet.dev/integrations/vtiger-api-mcp-server/convert-leads-to-deals.md)** (runs: daily): "List Vtiger contacts with Lifecycle Stage Lead created since yesterday. Convert the ones from a company domain (not Gmail or Yahoo) into a deal named after the organization in the Standard pipeline, and list the rest for me." → `list_contacts`, `list_deals`, `convert_contact_to_deal`
- **[Triage new support cases](https://cotlet.dev/integrations/vtiger-api-mcp-server/triage-new-cases.md)** (runs: daily): "Go through Vtiger cases with status New. Read each one, set the group (Billing or Support) and the priority, and leave anything about refunds over 500 for me." → `list_cases`, `get_case`, `update_case`
- **Weekly pipeline review** (runs: weekly): "Every Monday, list open Vtiger deals by sales stage with the total amount, and flag deals whose expected close date has already passed." → `list_deals`, `get_deal`
- **Move deals after sales calls**: "After my call with Whitfield Dental, move their deal to Negotiation and set the probability to 75." → `list_deals`, `update_deal_stage`
- **Log an emailed request as a case**: "Open a High priority Billing case for Luis Ortega: his invoice 1051 shows the wrong address. Do not email him." → `list_contacts`, `create_case`

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

Yes. Cotlet does not replace your automation platform: it gives it a Vtiger 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 qualified leads to deals, 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/vtiger/contacts. | 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/vtiger/contacts with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 10 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 Vtiger.

### list_contacts

Contacts of your CRM with organization, lifecycle stage and owner; leads too when the Leads module is on. Access: read. REST: `GET /api/v1/vtiger/contacts`. MCP: `vtiger_read → list_contacts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `module` | enum | no | contacts (default) or leads, for CRMs where the Leads module is enabled. |
| `lifecycle_stage` | string | no | Only contacts with this Lifecycle Stage, for example Lead. |
| `query` | string | no | Name, email or phone to search for. |
| `limit` | integer | no | Contacts per page. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists one page of the Contacts list under Main Menu > Essentials > Contacts, or of Essentials > Leads when module is leads. Filter by lifecycle_stage (Lead finds leads that are stored as contacts) or search by name, email or phone. Pass next_cursor back as cursor for the next page. You only see the records your Vtiger role lets you see.

Example response:

```json
{
  "contacts": [
    {
      "record_id": "1523",
      "name": "Dana Whitfield",
      "email": "dana@whitfielddental.example",
      "phone": "+1 555 0142",
      "organization": "Whitfield Dental",
      "lifecycle_stage": "Lead",
      "assigned_to": "Sam Rivera",
      "created_at": "2026-10-21"
    },
    {
      "record_id": "1524",
      "name": "Luis Ortega",
      "email": "luis@ortegabuilds.example",
      "phone": "+1 555 0177",
      "organization": "Ortega Builds",
      "lifecycle_stage": "Lead",
      "assigned_to": "Sam Rivera",
      "created_at": "2026-10-21"
    }
  ],
  "next_cursor": null
}
```

### list_deals

Deals with amount, sales stage, pipeline, expected close date and owner. Access: read. REST: `GET /api/v1/vtiger/deals`. MCP: `vtiger_read → list_deals`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `pipeline` | string | no | Only deals in this sales pipeline. |
| `sales_stage` | string | no | Only deals in this sales stage, named as in your pipeline. |
| `assigned_to` | string | no | Only deals owned by this user. |
| `query` | string | no | Deal or organization name to search for. |
| `limit` | integer | no | Deals per page. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists one page of deals from Main Menu > Sales > Deals, as the List View shows them. Filter by pipeline, sales_stage, owner or a search on the deal or organization name. amount is the number in the Amount field. Pass next_cursor back as cursor for the next page. Closed Won and Closed Lost deals come back like any other stage.

Example response:

```json
{
  "deals": [
    {
      "record_id": "2041",
      "name": "Whitfield Dental, 5 seats",
      "organization": "Whitfield Dental",
      "amount": 4200,
      "sales_stage": "Proposal",
      "pipeline": "Standard",
      "expected_close_date": "2026-11-15",
      "assigned_to": "Sam Rivera"
    },
    {
      "record_id": "2044",
      "name": "Ortega Builds, annual plan",
      "organization": "Ortega Builds",
      "amount": 9800,
      "sales_stage": "Qualification",
      "pipeline": "Standard",
      "expected_close_date": "2026-12-01",
      "assigned_to": "Sam Rivera"
    }
  ],
  "next_cursor": null
}
```

### get_deal

One deal with its fields, related contact and journey tasks. Access: read. REST: `GET /api/v1/vtiger/records/{record_id}/deal`. MCP: `vtiger_read → get_deal`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `record_id` | string | yes | Deal record id from list_deals. |

Opens one deal as its Summary View shows it: the fields, the related contact and organization, and the journey tasks listed in its Tasks tab. Use it before update_deal_stage to read the current stage and probability. A record your role cannot see returns an error instead of empty fields.

Example response:

```json
{
  "record_id": "2041",
  "name": "Whitfield Dental, 5 seats",
  "amount": 4200,
  "sales_stage": "Proposal",
  "pipeline": "Standard",
  "probability": 60,
  "expected_close_date": "2026-11-15",
  "assigned_to": "Sam Rivera",
  "contact": {
    "record_id": "1523",
    "name": "Dana Whitfield"
  },
  "journey_tasks": [
    {
      "title": "Send pricing sheet",
      "status": "Completed"
    },
    {
      "title": "Book demo call",
      "status": "Not Started"
    }
  ]
}
```

### list_cases

Support cases with status, priority, group, owner and contact. Access: read. REST: `GET /api/v1/vtiger/cases`. MCP: `vtiger_read → list_cases`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | enum | no | New, Assigned, Open, Wait for 3rd party, Wait for customer, Resolved or Closed. |
| `priority` | enum | no | Urgent, High, Medium or Low. |
| `group` | string | no | Only cases assigned to this group. |
| `assigned_to` | string | no | Only cases assigned to this user. |
| `limit` | integer | no | Cases per page. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists one page of cases from Main Menu > Support > Cases. status is one of New, Assigned, Open, Wait for 3rd party, Wait for customer, Resolved or Closed, and priority one of Urgent, High, Medium or Low. group is the team the case is assigned to. Pass next_cursor back as cursor for the next page.

Example response:

```json
{
  "cases": [
    {
      "record_id": "3318",
      "title": "Invoice 1042 charged twice",
      "status": "New",
      "priority": "Medium",
      "group": "Support",
      "assigned_to": null,
      "contact": "Dana Whitfield",
      "created_at": "2026-10-22 08:14"
    },
    {
      "record_id": "3319",
      "title": "Cannot log in to the customer portal",
      "status": "New",
      "priority": "Medium",
      "group": "Support",
      "assigned_to": null,
      "contact": "Luis Ortega",
      "created_at": "2026-10-22 08:31"
    }
  ],
  "next_cursor": null
}
```

### get_case

One case with its description, contact, SLA and current assignment. Access: read. REST: `GET /api/v1/vtiger/records/{record_id}/case`. MCP: `vtiger_read → get_case`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `record_id` | string | yes | Case record id from list_cases. |

Opens one case as its Deep Dive View shows it: title, description, status, priority, group, owner, contact and SLA Name. Use it to read what the customer wrote before you set a group or priority. A record your role cannot see returns an error.

Example response:

```json
{
  "record_id": "3318",
  "title": "Invoice 1042 charged twice",
  "description": "We were billed 480 twice on 18 October. Please refund one charge.",
  "status": "New",
  "priority": "Medium",
  "group": "Support",
  "assigned_to": null,
  "sla_name": null,
  "contact": {
    "record_id": "1523",
    "name": "Dana Whitfield"
  },
  "created_at": "2026-10-22 08:14"
}
```

### create_contact

Create a contact with email, phone, organization and lifecycle stage. Access: write, asks the user first. REST: `POST /api/v1/vtiger/contacts`. MCP: `vtiger_write → create_contact`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `first_name` | string | no | First name. |
| `last_name` | string | yes | Last name. |
| `email` | string | no | Email address. |
| `phone` | string | no | Phone number. |
| `organization` | string | no | Organization name. An existing organization is linked. |
| `lifecycle_stage` | string | no | Lifecycle Stage, for example Lead. |
| `assigned_to` | string | no | Owner. Default: the signed-in user. |

Creates one contact, the same as + Add Contact in the Contacts module. It does not look for duplicates, so call list_contacts with query first. Returns the new record_id. Fields your Vtiger layout marks mandatory must be filled; a missing one fails with the field name. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "record_id": "1530",
  "name": "Mira Okafor",
  "email": "mira@okaforlegal.example",
  "lifecycle_stage": "Lead",
  "assigned_to": "Sam Rivera"
}
```

### convert_contact_to_deal

Convert a lead into a deal, as the Convert button does. Access: write, asks the user first. REST: `POST /api/v1/vtiger/records/{record_id}/contact-to-deal/convert`. MCP: `vtiger_write → convert_contact_to_deal`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `record_id` | string | yes | Contact or lead record id from list_contacts. |
| `deal_name` | string | yes | Name of the new deal. |
| `amount` | number | no | Deal amount. |
| `expected_close_date` | date | no | Expected close date. |
| `pipeline` | string | no | Sales pipeline of the deal. |
| `lifecycle_stage` | string | no | New Lifecycle Stage of the contact. |

Runs the Convert flow on one record: a contact whose Lifecycle Stage is Lead, or a lead when the Leads module is enabled. It creates the deal with the name, amount, expected close date and pipeline you give, and can update the lifecycle stage. Field values carried over follow your Lead Conversion Data Mapping. A deal can start workflows you set up, such as emails on a sales stage. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "status": "converted",
  "contact": {
    "record_id": "1523",
    "name": "Dana Whitfield"
  },
  "deal": {
    "record_id": "2041",
    "name": "Whitfield Dental, 5 seats",
    "amount": 4200,
    "pipeline": "Standard",
    "expected_close_date": "2026-11-15"
  }
}
```

### update_deal_stage

Move a deal to another sales stage or pipeline. Access: write, asks the user first. REST: `PATCH /api/v1/vtiger/records/{record_id}/deal-stage`. MCP: `vtiger_write → update_deal_stage`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `record_id` | string | yes | Deal record id from list_deals. |
| `sales_stage` | string | yes | Target sales stage, named as in the pipeline. |
| `pipeline` | string | no | Target pipeline, only to move the deal to another pipeline. |
| `probability` | integer | no | Probability in percent, optional. |

Moves one deal like dragging it between columns of the Kanban view. With pipeline, it does what Change Pipeline does: pick the new pipeline and stage, and optionally the probability. A stage name your pipeline does not have fails, and the error lists the stages. Contacts can get emails from your Vtiger workflows when a stage changes. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "record_id": "2041",
  "name": "Whitfield Dental, 5 seats",
  "sales_stage": "Negotiation",
  "pipeline": "Standard",
  "probability": 75
}
```

### create_case

Open a support case for a contact, with or without an email to the customer. Access: write, asks the user first. REST: `POST /api/v1/vtiger/cases`. MCP: `vtiger_write → create_case`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `title` | string | yes | Case Title. |
| `contact_name` | string | yes | Contact the case belongs to. |
| `priority` | enum | no | Urgent, High, Medium or Low. |
| `group` | string | no | Group (team) to assign the case to. |
| `assigned_to` | string | no | Person in the group to assign it to. |
| `description` | string | no | What the customer reported. |
| `notify_customer` | boolean | no | true emails the customer through the Send Email tab. Default: false. |

Creates one case from the + Add Case form. With notify_customer true it uses the Send Email tab, which emails the customer; the default false uses Add Case and sends nothing. Title and contact are required; group and assigned_to place it with a team or person. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "record_id": "3320",
  "title": "Wrong address on invoice 1051",
  "status": "New",
  "priority": "High",
  "group": "Billing",
  "contact": "Luis Ortega",
  "customer_emailed": false
}
```

### update_case

Set a case's group, owner, priority, status or SLA. Access: write, asks the user first. REST: `PATCH /api/v1/vtiger/records/{record_id}/case`. MCP: `vtiger_write → update_case`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `record_id` | string | yes | Case record id from list_cases. |
| `status` | enum | no | New, Assigned, Open, Wait for 3rd party, Wait for customer, Resolved or Closed. |
| `priority` | enum | no | Urgent, High, Medium or Low. |
| `group` | string | no | Group (team) to assign the case to. |
| `assigned_to` | string | no | Person to assign the case to. |
| `sla_name` | string | no | Customer SLA to apply. |

Changes the fields you pass on one case and leaves the others as they are. group is the team picklist from Deep Dive, assigned_to a person, sla_name one of the customer SLAs. Setting Resolved starts Vtiger's own wait before the case closes by itself. A group or SLA the CRM does not have fails, and the error lists the options. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "record_id": "3318",
  "title": "Invoice 1042 charged twice",
  "status": "New",
  "priority": "High",
  "group": "Billing",
  "assigned_to": null,
  "sla_name": null
}
```

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

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

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

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

```
List Vtiger contacts with Lifecycle Stage Lead created since yesterday. Convert the ones from a company domain (not Gmail or Yahoo) into a deal named after the organization in the Standard pipeline, and list the rest for me.
```

### Call Vtiger 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/vtiger 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 PATCH https://cotlet.dev/api/v1/vtiger/records/2041/deal-stage \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"sales_stage":"Negotiation","probability":75}'
```

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

```
{
  "record_id": "2041",
  "name": "Whitfield Dental, 5 seats",
  "sales_stage": "Negotiation",
  "pipeline": "Standard",
  "probability": 75
}
```

## Why use Cotlet for Vtiger?

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

## Is it safe to connect Vtiger to Cotlet?

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

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

## Is there a Vtiger MCP server on GitHub?

Yes. Community Vtiger MCP servers exist on GitHub, usually maintained by one person. You install one yourself, give it your username and access key, and fix it when it breaks. They call the REST API, so Vtiger's per-edition limits apply to them. Cotlet hosts the same kind of server for you and works in the signed-in CRM, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, install it, set your CRM address, username and access key, add it to each MCP client | Sign up, sign in to Vtiger once, add one MCP server or API key |
| When Vtiger 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 Vtiger access | An access key in a file on your computer, readable by any program you run | Your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| API limits | Every call counts against your edition's day, hour and minute limits | Works in the CRM screens you are signed in to, so the REST limits do not apply |
| When the session expires | Tools fail until you fix the key or credentials | Your Cloud Browser keeps you signed in; if Vtiger 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 Vtiger 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 Vtiger API cost?

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

**Do I need to be technical?**

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

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

Vtiger 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).

**Does Cotlet use the Vtiger REST API, and which edition do I need?**

No. Cotlet works in your own signed-in CRM, so the REST API limits do not apply. Vtiger's limits table lists 0 requests for One Pilot, 24,000 a day for One Growth, 72,000 for One Professional and 120,000 for Enterprise (checked 22 Oct 2026). What your agent can see and change depends on your Vtiger role.

**Does it work when leads are stored as contacts?**

Yes. In Vtiger versions where leads are contacts with the Lifecycle Stage Lead, list_contacts filters on that field and convert_contact_to_deal uses the Convert button of the contact. When your CRM has the Leads module enabled, the tools use it and its Convert Lead form instead.

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

No. Every call to create_contact, convert_contact_to_deal, update_deal_stage, create_case or update_case 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 Vtiger 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/vtiger 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.