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

# Method CRM API and MCP server

> Method CRM has a full REST API with read and write access to permitted records, but no ready-made official MCP server (checked 23 Oct 2026). Method builds a custom MCP for a customer on request. Its API keys can only be created by an Admin and cannot be scoped or limited to read-only.

CRM built around QuickBooks Online or QuickBooks Desktop: customers and leads, estimates, invoices, payments and activities in one place, synced both ways with your books.

## What is the Method CRM API?

Cotlet's Method CRM API exposes 15 endpoints for your own Method CRM account: list customers and leads, get a customer or lead, list estimates, get an estimate, list invoices, get an invoice, list activities, create a lead, convert a lead to a customer, create an estimate, email an estimate, convert an estimate to an invoice, email an invoice, record a payment and create an activity. The list_customers endpoint returns list customers and leads from Customers & Leads. Each endpoint takes simple JSON inputs like contact_id, cursor or assigned_to and works both as an operation of the method_crm_read or method_crm_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:** 15 (7 read, 8 write)
- **Updated:** 2026-10-22

Method CRM has a full REST API with read and write access to permitted records, but no ready-made official MCP server (checked 23 Oct 2026). Cotlet is a hosted MCP server and REST API for Method CRM with 15 endpoints (7 read, 8 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Method CRM have an official API?

Method CRM has a full REST API with read and write access to permitted records, but no ready-made official MCP server (checked 23 Oct 2026). Method builds a custom MCP for a customer on request. Its API keys can only be created by an Admin and cannot be scoped or limited to read-only.

| Task | Method CRM official | Cotlet |
|---|---|---|
| Read customers and leads | Yes | Yes |
| Create leads and activities | Yes | Yes |
| Convert a lead to a customer | Partly: The API page does not document the conversion, which is permanent and syncs to QuickBooks at once | Yes |
| Read and create estimates and invoices | Yes: Changes may sync to QuickBooks or Xero | Yes |
| Email an estimate or invoice link to the customer | Partly: The API page does not document sending; Method does it on screen with Send > Email | Yes |
| Convert an estimate to an invoice | Partly: The API creates invoices; the page does not say whether the estimate link and deposit line carry over | Yes |
| Record a payment against invoices | Yes: Records only: the API cannot process a card payment | Yes |
| Work without an Admin API key | No: The API needs a key that only an Admin can create | Yes |

Sources: [Method: Method CRM API](https://www.method.me/features/api/), [Method: How to connect Method CRM with Claude](https://www.method.me/blog/how-to-connect-method-crm-with-claude/), [Method Help: Estimate Approvals and Deposits](https://help.method.me/en/articles/8147875-estimate-approvals-and-deposits), [Method Help: Invoice Reports](https://help.method.me/en/articles/2239413-invoice-reports)

## Quick reference

```text
Method CRM has a full REST API with read and write access to permitted records, but no ready-made official MCP server (checked 23 Oct 2026). Method builds a custom MCP for a customer on request. Its API keys can only be created by an Admin and cannot be scoped or limited to read-only.
Cotlet provides a hosted MCP server and REST API for Method CRM: 15 tools (7 read, 8 write).
Access       Sign up at https://cotlet.dev/app/signup?app=method-crm, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    method_crm_read, method_crm_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/method-crm, each operation at its own route, e.g. POST /api/v1/method-crm/customers/{customer_id}/payment/receive
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_customers, get_customer, list_estimates, get_estimate, list_invoices, get_invoice, list_activities, create_lead, convert_lead_to_customer, create_estimate, send_estimate, convert_estimate_to_invoice, send_invoice, receive_payment, create_activity
Confirm      convert_lead_to_customer, create_estimate, send_estimate, convert_estimate_to_invoice, send_invoice, receive_payment (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/method-crm-api-mcp-server.md

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

## What can an AI agent do in Method CRM?

Cotlet is best for Method CRM owners and office managers who want an AI agent to chase overdue invoices, turn accepted estimates into invoices and record payments without running or fixing a server.

- **[Follow up on overdue invoices](https://cotlet.dev/integrations/method-crm-api-mcp-server/overdue-invoice-follow-up.md)** (runs: weekly): "List overdue invoices in Method. For each customer without an open activity, email the invoice link with a short reminder and log an activity. Show me the rest." → `list_invoices`, `get_invoice`, `get_customer`, `send_invoice`, `create_activity`
- **[Convert accepted estimates to invoices](https://cotlet.dev/integrations/method-crm-api-mcp-server/convert-accepted-estimates-to-invoices.md)** (runs: daily): "Find estimates customers accepted in the Method portal. Turn each into an invoice, hold the QuickBooks sync, and list them for me to check." → `list_estimates`, `get_estimate`, `convert_estimate_to_invoice`, `send_invoice`
- **[Record customer payments](https://cotlet.dev/integrations/method-crm-api-mcp-server/record-customer-payments.md)** (runs: weekly): "Here are this week's bank deposits. Match each to an open Method invoice by customer and amount, record the payment with the right invoice, and list the lines you could not match." → `list_customers`, `list_invoices`, `receive_payment`
- **Schedule follow-ups for new leads** (runs: daily): "List leads added in the last 2 days with no activity. Create a follow-up call activity for each, assigned to its Assigned To user, due in 2 days." → `list_customers`, `get_customer`, `create_activity`
- **Draft an estimate from a customer request** (runs: daily): "From this email, create an estimate for Ortega Kitchens with the items they asked for, held from QuickBooks, and show me the total." → `get_customer`, `create_estimate`, `get_estimate`

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

Yes. Cotlet does not replace your automation platform: it gives it a Method CRM 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 follow up on overdue invoices, 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/method-crm/invoices. | 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/method-crm/invoices with your API key. | cron or GitHub Actions. |

## Tools

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

### list_customers

List customers and leads from Customers & Leads. Access: read. REST: `GET /api/v1/method-crm/customers`. MCP: `method_crm_read → list_customers`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Search text for the name. |
| `contact_type` | string | no | customer or lead. Default both. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns each contact with its ID, name, type, assigned user and lead status for leads. Results come in pages; follow next_cursor until it is null. It returns only the contacts your Method user may see.

Example response:

```json
{
  "contacts": [
    {
      "contact_id": "C-2041",
      "name": "Ortega Kitchens",
      "type": "customer",
      "assigned_to": "Dana Whitfield"
    },
    {
      "contact_id": "C-2077",
      "name": "Lopez Fencing",
      "type": "lead",
      "assigned_to": "Dana Whitfield",
      "lead_status": "Contacted"
    }
  ],
  "next_cursor": null
}
```

### get_customer

Get one contact with its addresses and activities. Access: read. REST: `GET /api/v1/method-crm/contacts/{contact_id}/customer`. MCP: `method_crm_read → get_customer`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `contact_id` | string | yes | Contact ID from list_customers. |

Returns the billing and shipping addresses, assigned user, tags, balance and the open and closed activities of the contact. For a lead it also returns the lead status, rating and source. It does not return payment card data.

Example response:

```json
{
  "contact_id": "C-2041",
  "name": "Ortega Kitchens",
  "type": "customer",
  "email": "billing@ortega-kitchens.example",
  "assigned_to": "Dana Whitfield",
  "balance": 4800,
  "open_activities": [],
  "closed_activities": [
    {
      "activity_id": "A-9012",
      "type": "Call",
      "status": "Completed",
      "start": "2026-10-02T10:00:00Z"
    }
  ]
}
```

### list_estimates

List estimates, newest first. Access: read. REST: `GET /api/v1/method-crm/estimates`. MCP: `method_crm_read → list_estimates`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `contact_id` | string | no | Only this customer or lead. |
| `active_only` | boolean | no | Only estimates ticked "Estimate is active", like the Active filter. Default true. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the number, date, customer, status and total of each estimate. The status comes from QuickBooks and changes when a customer accepts in the portal. Follow next_cursor until it is null.

Example response:

```json
{
  "estimates": [
    {
      "estimate_id": "2217",
      "number": "2217",
      "date": "2026-10-01",
      "customer": "Ortega Kitchens",
      "status": "Accepted",
      "total": 9600
    }
  ],
  "next_cursor": null
}
```

### get_estimate

Get one estimate with its lines, deposit and acceptance. Access: read. REST: `GET /api/v1/method-crm/estimates/{estimate_id}`. MCP: `method_crm_read → get_estimate`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `estimate_id` | string | yes | Estimate ID from list_estimates. |

Returns the line items, taxes, discount, shipping, customer message, deposit required and received, and accepted_by and accepted_date when the status is Accepted. Memo (Internal) is included and never sent to the customer.

Example response:

```json
{
  "estimate_id": "2217",
  "customer": "Ortega Kitchens",
  "status": "Accepted",
  "accepted_by": "Ana Ortega",
  "accepted_date": "2026-10-05",
  "lines": [
    {
      "item": "Cabinet install",
      "quantity": 1,
      "rate": 9600,
      "amount": 9600
    }
  ],
  "total": 9600,
  "deposit_received": 2400
}
```

### list_invoices

List invoices, newest first. Access: read. REST: `GET /api/v1/method-crm/invoices`. MCP: `method_crm_read → list_invoices`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | string | no | all, overdue or paid, like the Invoice Reports filter. Default all. |
| `contact_id` | string | no | Only this customer. |
| `assigned_to` | string | no | Method user, or Sales Rep on QuickBooks Desktop accounts. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the number, date, due date, customer, total and balance due of each invoice. Follow next_cursor until it is null. On QuickBooks Desktop accounts Method keeps only the last month of transactions by default, so older invoices need a full sync first.

Example response:

```json
{
  "invoices": [
    {
      "invoice_id": "1043",
      "date": "2026-09-15",
      "due": "2026-09-30",
      "customer": "Ortega Kitchens",
      "total": 4800,
      "balance_due": 4800,
      "status": "overdue"
    }
  ],
  "next_cursor": null
}
```

### get_invoice

Get one invoice with its lines and balance. Access: read. REST: `GET /api/v1/method-crm/invoices/{invoice_id}`. MCP: `method_crm_read → get_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | string | yes | Invoice ID from list_invoices. |

Returns the lines, terms, taxes, discount, shipping, customer message, balance due and the linked estimate when there is one. Balance due is the value Method last saved.

Example response:

```json
{
  "invoice_id": "1043",
  "customer": "Ortega Kitchens",
  "date": "2026-09-15",
  "due": "2026-09-30",
  "terms": "Net 15",
  "lines": [
    {
      "item": "Demolition",
      "quantity": 1,
      "rate": 4800,
      "amount": 4800
    }
  ],
  "total": 4800,
  "balance_due": 4800
}
```

### list_activities

List activities from the Activities List. Access: read. REST: `GET /api/v1/method-crm/activities`. MCP: `method_crm_read → list_activities`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `assigned_to` | string | no | Method user the activity is assigned to. |
| `contact_id` | string | no | Only this contact. |
| `status` | string | no | An activity status from your Method account. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the type, status, contact, assigned user and start date of each activity. Types and statuses are the ones your account defines, so the values differ between accounts.

Example response:

```json
{
  "activities": [
    {
      "activity_id": "A-9120",
      "type": "Call",
      "status": "Not Started",
      "contact": "Nguyen Garage",
      "assigned_to": "Dana Whitfield",
      "start": "2026-10-24T09:00:00Z"
    }
  ],
  "next_cursor": null
}
```

### create_lead

Create a lead in Customers & Leads. Access: write. REST: `POST /api/v1/method-crm/leads`. MCP: `method_crm_write → create_lead`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Name in QuickBooks, the name the customer gets after conversion. |
| `email` | string | no | Contact email. |
| `phone` | string | no | Contact phone. |
| `assigned_to` | string | no | Method user responsible for the lead. |
| `source` | string | no | A lead source from your account. |

Returns the new contact ID. A lead is not synced to QuickBooks until it becomes a customer, and the call sends nothing to anyone, so it does not wait for your OK. A wrong lead is removed by hand in Method.

Example response:

```json
{
  "contact_id": "C-2090",
  "name": "Lopez Fencing",
  "type": "lead",
  "synced_to_quickbooks": false
}
```

### convert_lead_to_customer

Convert a lead to a customer. Access: write, asks the user first. REST: `POST /api/v1/method-crm/contacts/{contact_id}/lead-to-customer/convert`. MCP: `method_crm_write → convert_lead_to_customer`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `contact_id` | string | yes | Lead ID from list_customers. |

Removes the lead status and syncs the customer to QuickBooks at once. Method says it cannot be reversed. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "contact_id": "C-2090",
  "type": "customer",
  "synced_to_quickbooks": true
}
```

### create_estimate

Create an estimate for a customer or lead. Access: write, asks the user first. REST: `POST /api/v1/method-crm/contacts/{contact_id}/estimates`. MCP: `method_crm_write → create_estimate`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `contact_id` | string | yes | Customer or lead ID. |
| `date` | string | yes | YYYY-MM-DD. |
| `expiration_date` | string | no | YYYY-MM-DD. |
| `lines` | array | yes | Objects with item (a name from your Items), quantity and optional rate. |
| `customer_message` | string | no | Shown to the customer. |
| `wait_for_sync_approval` | boolean | no | Ticks "Wait for approval before syncing" so QuickBooks stays untouched until you untick it in Method. Default true. |

Returns the estimate ID and total. Items must exist in your Items App; an unknown item fails and the error lists nearby names. With the hold on, nothing reaches QuickBooks, and for a lead the conversion happens only when you release it. It sends nothing to the customer. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "estimate_id": "2230",
  "customer": "Ortega Kitchens",
  "total": 1850,
  "status": "Pending",
  "sync": "held"
}
```

### send_estimate

Email the customer a portal link to an estimate. Access: write, asks the user first. REST: `POST /api/v1/method-crm/estimates/{estimate_id}`. MCP: `method_crm_write → send_estimate`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `estimate_id` | string | yes | Estimate ID. |
| `subject` | string | no | Email subject. Default from your template. |
| `body` | string | no | Email text. Default from your template. |

Does what Send > Email does: the customer gets a link to their portal, where they can accept or reject. It fails if the contact has no email. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "estimate_id": "2230",
  "status": "sent",
  "sent_to": "billing@ortega-kitchens.example"
}
```

### convert_estimate_to_invoice

Create an invoice from an estimate. Access: write, asks the user first. REST: `POST /api/v1/method-crm/estimates/{estimate_id}/to-invoice/convert`. MCP: `method_crm_write → convert_estimate_to_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `estimate_id` | string | yes | Estimate ID. |
| `wait_for_sync_approval` | boolean | no | Ticks "Wait for approval before syncing" so QuickBooks stays untouched until you untick it in Method. Default true. |

Does what Create > Create Invoice does and saves the invoice. A deposit already received appears as a line item with your Deposit Item. The customer is not contacted; send_invoice does that. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_id": "1051",
  "from_estimate_id": "2217",
  "customer": "Ortega Kitchens",
  "total": 9600,
  "deposit_received": 2400,
  "balance_due": 7200,
  "sync": "held"
}
```

### send_invoice

Email the customer a portal link to an invoice. Access: write, asks the user first. REST: `POST /api/v1/method-crm/invoices/{invoice_id}`. MCP: `method_crm_write → send_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | string | yes | Invoice ID. |
| `subject` | string | no | Email subject. Default from your template. |
| `body` | string | no | Email text. Default from your template. |

Does what Send > Email does: the customer gets a link to their portal, where they can view the invoice and pay if a payment gateway is set up. It fails if the contact has no email. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_id": "1043",
  "status": "sent",
  "sent_to": "billing@ortega-kitchens.example",
  "subject": "Invoice 1043 is 23 days overdue"
}
```

### receive_payment

Record a payment against a customer's invoices. Access: write, asks the user first. REST: `POST /api/v1/method-crm/customers/{customer_id}/payment/receive`. MCP: `method_crm_write → receive_payment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `customer_id` | string | yes | Customer ID. |
| `amount` | number | yes | Payment amount. |
| `payment_method` | string | yes | A payment method from your account, such as Check. |
| `date` | string | yes | YYYY-MM-DD. |
| `deposit_to_account` | string | yes | An account from QuickBooks. |
| `invoice_ids` | array | no | Invoices to pay. Without it Method applies the payment by its auto-apply rule. |
| `reference_number` | string | no | Check or transfer number. |
| `wait_for_sync_approval` | boolean | no | Ticks "Wait for approval before syncing" so QuickBooks stays untouched until you untick it in Method. Default true. |

Returns the payment ID and how it was applied to each invoice. It records a payment that already arrived and never charges a card. A customer with a negative balance is refused. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "payment_id": "P-3320",
  "customer": "Ortega Kitchens",
  "amount": 4800,
  "applied": [
    {
      "invoice_id": "1043",
      "amount": 4800,
      "balance_due": 0
    }
  ],
  "sync": "held"
}
```

### create_activity

Create an activity on a contact. Access: write. REST: `POST /api/v1/method-crm/contacts/{contact_id}/activities`. MCP: `method_crm_write → create_activity`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `contact_id` | string | yes | Customer or lead ID. |
| `type` | string | yes | An activity type from your account. |
| `status` | string | yes | An activity status from your account. |
| `start` | string | yes | Start date and time, ISO 8601. |
| `assigned_to` | string | no | Method user. Default the signed-in user. |
| `comments` | string | no | Notes on the activity. |

Returns the activity ID. It does not use Notify Assigned To, so nobody is emailed, and it does not wait for your OK. A wrong activity is deleted by hand in Method.

Example response:

```json
{
  "activity_id": "A-9121",
  "contact": "Ortega Kitchens",
  "type": "Call",
  "status": "Not Started",
  "start": "2026-10-26T09:00:00Z"
}
```

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

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

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

2. **Sign in to Method CRM in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Method CRM 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 Method CRM 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 overdue invoices in Method. For each customer without an open activity, email the invoice link with a short reminder and log an activity. Show me the rest.
```

### Call Method CRM 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/method-crm 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/method-crm/customers/C-2041/payment/receive \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"amount":1250,"payment_method":"Transfer","date":"2026-10-22","deposit_to_account":"Checking","invoice_ids":["1038"],"wait_for_sync_approval":true}'
```

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

```
{
  "payment_id": "P-3321",
  "customer": "Chen Dental",
  "amount": 1250,
  "applied": [
    {
      "invoice_id": "1038",
      "amount": 1250,
      "balance_due": 0
    }
  ],
  "sync": "held"
}
```

## Why use Cotlet for Method CRM?

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

## Is it safe to connect Method CRM to Cotlet?

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

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

## Is there a Method CRM MCP server on GitHub?

Yes. Community Method CRM MCP servers exist on GitHub, usually maintained by one person. You install one on your own computer, give it an Admin API key, and keep it running yourself; when Method changes its API, it stops working until you or the maintainer fix it. Method also builds a custom MCP for a customer on request. Cotlet hosts the same kind of server for you, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, install it, create an Admin API key, add it to each MCP client | Sign up, sign in to Method once, add one MCP server or API key |
| When Method changes | It breaks until you or the maintainer fix it | Our team tests it automatically and fixes it for you; failed calls are free |
| Your Method access | An API key in a file on your computer, with the full permissions of its user and no scopes | Your own Cloud Browser in the EU, profile encrypted, only for the apps you enable; each tool has its own confirmation |
| When access stops | Tools fail until you create a new key and update the file | Your Cloud Browser keeps you signed in; if Method 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 Method CRM 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 Method CRM API cost?

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

**Do I need to be technical?**

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

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

Method CRM 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 a Method API key?**

No. Cotlet works in your signed-in Method session. Method says its API key can only be created by an Admin and has the full permissions of its user, because scoped and read-only keys are not built yet (checked 23 Oct 2026).

**Will my agent change my QuickBooks?**

Only when you let it. Method syncs saved estimates, invoices and payments with QuickBooks. create_estimate, convert_estimate_to_invoice and receive_payment tick Wait for approval before syncing by default, so QuickBooks stays untouched until you untick it in Method. There is no delete tool, and Method warns that deleted data cannot be recovered.

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

No. Every call to convert_lead_to_customer, create_estimate, send_estimate, convert_estimate_to_invoice, send_invoice or receive_payment 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 and create_activity run without asking, because they send nothing to anyone and one call undoes it.

**Can I use the Method CRM 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/method-crm 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.