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

# Facturama API and MCP server

> Yes. Facturama has a REST API that stamps CFDI 4.0 invoices, but it is a paid add-on and it has no official MCP server (checked 14 Oct 2026). You buy the API module (MXN 1,650 a year) and separate prepaid API folios, which only work through the API.

Mexican online invoicing: you issue CFDI 4.0 invoices stamped for the SAT, keep client and product catalogs, send invoices by email, cancel them and download the PDF and XML.

## What is the Facturama API?

Cotlet's Facturama API exposes 11 endpoints for your own Facturama account: list invoices, get invoice, list clients, get client, list products, download invoice file, create client, create invoice, create credit note, email invoice and cancel invoice. The list_invoices endpoint returns invoices and credit notes in the account with folio, client, total and status, newest first. Each endpoint takes simple JSON inputs like invoice_id, limit or cursor and works both as an operation of the facturama_read or facturama_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:** 11 (6 read, 5 write)
- **Updated:** 2026-10-21

Yes. Cotlet is a hosted MCP server and REST API for Facturama with 11 endpoints (6 read, 5 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Facturama have an official API?

Yes. Facturama has a REST API that stamps CFDI 4.0 invoices, but it is a paid add-on and it has no official MCP server (checked 14 Oct 2026). You buy the API module (MXN 1,650 a year) and separate prepaid API folios, which only work through the API.

| Task | Facturama official | Cotlet |
|---|---|---|
| Issue a CFDI 4.0 invoice | Yes: POST /3/cfdis; needs the API module and API folios | Yes |
| Issue a credit note (CFDI de egreso) | Yes: Facturama documents credit notes in its API | Yes |
| Cancel an invoice | Yes: The API module includes cancellation | Yes |
| Add a client | Yes: The Web API manages clients and products for one issuing RFC | Yes |
| Look up invoices and clients | Yes: The API module includes query | Yes |
| Email an invoice to the client | Yes: The API module includes sending invoices | Yes |
| Download the XML and PDF | Partly: Facturama lists PDF and XML download for its web app; its API pages do not show it | Yes |
| Use it from an AI agent over MCP | No | Yes |

Sources: [Facturama: electronic invoicing API](https://facturama.mx/api-facturacion-electronica), [Facturama: plans and prices](https://facturama.mx/planes-facturacion), [Facturama docs: first invoice and authentication](https://facturama.mx/docs/es/guias/primera-factura), [Facturama: credit note API](https://facturama.mx/api/nota-de-credito)

## For AI agents

```text
Yes. Facturama has a REST API that stamps CFDI 4.0 invoices, but it is a paid add-on and it has no official MCP server (checked 14 Oct 2026). You buy the API module (MXN 1,650 a year) and separate prepaid API folios, which only work through the API.
Cotlet provides a hosted MCP server and REST API for Facturama: 11 tools (6 read, 5 write).
Access       Sign up at https://cotlet.dev/app/signup?app=facturama, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    facturama_read, facturama_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/facturama, each operation at its own route, e.g. POST /api/v1/facturama/clients/{client_id}/invoices
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_invoices, get_invoice, list_clients, get_client, list_products, download_invoice_file, create_client, create_invoice, create_credit_note, email_invoice, cancel_invoice
Confirm      create_invoice, create_credit_note, email_invoice, cancel_invoice (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/facturama-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=facturama, requests Facturama in the Cotlet console and creates an API key there.
2. The user signs in to Facturama once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Facturama 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 Facturama server that someone else maintains, including non-developers.

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 Facturama 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 Facturama 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 Facturama 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 Facturama's terms; Cotlet is not affiliated with Facturama.
```

## What can an AI agent do in Facturama?

Cotlet is best for Mexican freelancers and small businesses on Facturama who want their AI agent to issue CFDI invoices and credit notes and collect XML and PDF files without running or fixing a server.

- **[Issue CFDI invoices from a list of jobs](https://cotlet.dev/integrations/facturama-api-mcp-server/issue-cfdi-invoices-from-jobs.md)** (runs: weekly): "Here are this week's finished jobs. For each client, find them in Facturama (create the client if missing, and tell me), issue one CFDI invoice with 16% IVA, and email it to the client." → `list_clients`, `create_client`, `create_invoice`, `email_invoice`
- **[Issue credit notes for returns and discounts](https://cotlet.dev/integrations/facturama-api-mcp-server/issue-credit-notes.md)**: "Client Estudio Norte returned one hour of work on invoice FAC-101. Issue a credit note for 500 pesos plus IVA against that invoice and email it to them." → `get_invoice`, `create_credit_note`, `email_invoice`
- **[Send monthly CFDI XML and PDF to your accountant](https://cotlet.dev/integrations/facturama-api-mcp-server/monthly-cfdi-xml-pdf-for-accountant.md)**: "List every invoice I issued last month in Facturama, download the XML and PDF of each, and give me a table with folio, client, total and UUID." → `list_invoices`, `download_invoice_file`
- **Cancel a wrong CFDI invoice**: "Cancel invoice FAC-099 in Facturama because it was issued to the wrong client, and tell me the result." → `get_invoice`, `cancel_invoice`
- **Add clients from a spreadsheet**: "Add the clients in this sheet to Facturama with their RFC, name, tax zip code and fiscal regime, and skip the ones that already exist." → `list_clients`, `create_client`

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

Yes. Cotlet does not replace your automation platform: it gives it a Facturama 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 issue cfdi invoices from a list of jobs, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/facturama/clients. | 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/facturama/clients with your API key. | cron or GitHub Actions. |

## Tools

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

### list_invoices

Invoices and credit notes in the account with folio, client, total and status, newest first. Access: read. REST: `GET /api/v1/facturama/invoices`. MCP: `facturama_read → list_invoices`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `issued_since` | date | no | Only documents issued on or after this date, YYYY-MM-DD. |
| `issued_until` | date | no | Only documents issued on or before this date, YYYY-MM-DD. |
| `client_rfc` | string | no | Only documents for this client RFC. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists CFDI documents issued from the account, newest first, including invoices, credit notes and cancelled ones, each with its status. Filter by issue date or client RFC. Pages hold up to 100 documents; pass next_cursor back as cursor for the next page.

Example response:

```json
{
  "invoices": [
    {
      "invoice_id": "Y61TLX-Ls_ZJFqzjanPN1w2",
      "series": "FAC",
      "folio": "101",
      "cfdi_type": "ingreso",
      "status": "issued",
      "issued_at": "2026-10-14",
      "client_name": "Estudio Norte SA de CV",
      "total": 1160,
      "currency": "MXN"
    }
  ],
  "next_cursor": null
}
```

### get_invoice

One invoice or credit note with its lines, taxes, totals, series, folio and UUID. Access: read. REST: `GET /api/v1/facturama/invoices/{invoice_id}`. MCP: `facturama_read → get_invoice`.

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

Returns the full document: receiver, lines, tax per line, totals, series, folio and the UUID the SAT stamp assigned, plus its status. Fails with a not-found error when the ID does not exist. Use it before a credit note or a cancellation to see what you are changing.

Example response:

```json
{
  "invoice_id": "Y61TLX-Ls_ZJFqzjanPN1w2",
  "series": "FAC",
  "folio": "101",
  "uuid": "6f1c2a90-3b7e-4d55-9a1e-0c52b8e4d7a1",
  "cfdi_type": "ingreso",
  "status": "issued",
  "issued_at": "2026-10-14T10:32:00-06:00",
  "client": {
    "client_id": "cl_4821",
    "rfc": "XAXX010101000",
    "name": "Estudio Norte SA de CV"
  },
  "items": [
    {
      "description": "Design review hour",
      "quantity": 2,
      "unit_price": 500,
      "subtotal": 1000,
      "tax_rate": 0.16,
      "tax": 160,
      "total": 1160
    }
  ],
  "subtotal": 1000,
  "tax_total": 160,
  "total": 1160,
  "currency": "MXN"
}
```

### list_clients

Clients in your catalog with RFC, name, CFDI use, tax zip code and fiscal regime. Access: read. REST: `GET /api/v1/facturama/clients`. MCP: `facturama_read → list_clients`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `search` | string | no | Text to match against client name or RFC. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists the clients saved in the account catalog, filtered by a search text on name or RFC. Use client_id from each item in create_invoice. Pages hold up to 100 clients; pass next_cursor back as cursor for the next page.

Example response:

```json
{
  "clients": [
    {
      "client_id": "cl_4821",
      "rfc": "XAXX010101000",
      "name": "Estudio Norte SA de CV",
      "cfdi_use": "G03",
      "tax_zip_code": "64000",
      "fiscal_regime": "601",
      "email": "billing@estudionorte.example"
    }
  ],
  "next_cursor": null
}
```

### get_client

One client with all fiscal data and email addresses. Access: read. REST: `GET /api/v1/facturama/clients/{client_id}`. MCP: `facturama_read → get_client`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `client_id` | string | yes | Client ID from list_clients or create_client. |

Returns the saved receiver data of one client: RFC, name, CFDI use, tax zip code, fiscal regime and email. Use it to check that a client has every field a CFDI 4.0 invoice needs before you stamp.

Example response:

```json
{
  "client_id": "cl_4821",
  "rfc": "XAXX010101000",
  "name": "Estudio Norte SA de CV",
  "cfdi_use": "G03",
  "tax_zip_code": "64000",
  "fiscal_regime": "601",
  "email": "billing@estudionorte.example"
}
```

### list_products

Products and services saved in your catalog with SAT product code, unit and price. Access: read. REST: `GET /api/v1/facturama/products`. MCP: `facturama_read → list_products`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `search` | string | no | Text to match against the product description. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists the products and services saved in the account catalog, which Facturama keeps so you can invoice quickly. Each item has the SAT product code, unit and unit price. Pages hold up to 100 items.

Example response:

```json
{
  "products": [
    {
      "product_id": "pr_310",
      "description": "Design review hour",
      "product_code": "80141600",
      "unit": "Hour",
      "unit_price": 500,
      "tax_rate": 0.16
    }
  ],
  "next_cursor": null
}
```

### download_invoice_file

The XML or PDF of one invoice or credit note, as a file. Access: read. REST: `GET /api/v1/facturama/invoices/{invoice_id}/file/download`. MCP: `facturama_read → download_invoice_file`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | string | yes | Invoice ID from list_invoices or create_invoice. |
| `format` | enum | yes | xml or pdf. |

Returns the XML (the legal CFDI) or the PDF of one document as base64 content with its file name. Fails with a not-found error when the ID does not exist.

Example response:

```json
{
  "invoice_id": "Y61TLX-Ls_ZJFqzjanPN1w2",
  "format": "xml",
  "file_name": "FAC-101.xml",
  "content_base64": "PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4="
}
```

### create_client

Add a client to the catalog with RFC, name, CFDI use, tax zip code and fiscal regime. Access: write. REST: `POST /api/v1/facturama/tax-zips/{tax_zip_code}/clients`. MCP: `facturama_write → create_client`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `rfc` | string | yes | Client RFC. |
| `name` | string | yes | Legal name as registered with the SAT. |
| `cfdi_use` | string | yes | CFDI use code, for example G03. |
| `tax_zip_code` | string | yes | Tax zip code of the client. |
| `fiscal_regime` | string | yes | Fiscal regime code of the client. |
| `email` | string | no | Address that email_invoice uses by default. |

Saves a client and returns its client_id. It reaches no one and issues nothing, and a wrong entry is fixed in Facturama, so it does not ask for confirmation.

Example response:

```json
{
  "client_id": "cl_4822",
  "rfc": "XAXX010101000",
  "name": "Clinica Alba SC",
  "cfdi_use": "G03",
  "tax_zip_code": "03100",
  "fiscal_regime": "612",
  "email": "pagos@clinicaalba.example"
}
```

### create_invoice

Issue and stamp a CFDI 4.0 invoice for a client with one or more lines. Access: write, asks the user first. REST: `POST /api/v1/facturama/clients/{client_id}/invoices`. MCP: `facturama_write → create_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `client_id` | string | yes | Client ID from list_clients or create_client. |
| `items` | array | yes | Lines. Each has description, quantity, unit_price and tax_rate (0.16 for 16% IVA), plus optional product_id from list_products. |
| `payment_form` | string | no | How the client pays, for example transfer or cash. |
| `payment_method` | string | no | Single payment or installments. |
| `series` | string | no | Invoice series. Default: your default series. |

Issues a CFDI 4.0 invoice of type ingreso and stamps it with the SAT, so there is no draft: the invoice is final once the call succeeds. Returns the invoice_id, series, folio, UUID and totals. It uses one folio of your plan and does not email the invoice: use email_invoice for that. A wrong invoice is fixed by cancel_invoice or create_credit_note. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_id": "Y61TLX-Ls_ZJFqzjanPN1w2",
  "series": "FAC",
  "folio": "101",
  "uuid": "6f1c2a90-3b7e-4d55-9a1e-0c52b8e4d7a1",
  "cfdi_type": "ingreso",
  "status": "issued",
  "issued_at": "2026-10-14T10:32:00-06:00",
  "client": {
    "client_id": "cl_4821",
    "rfc": "XAXX010101000",
    "name": "Estudio Norte SA de CV"
  },
  "items": [
    {
      "description": "Design review hour",
      "quantity": 2,
      "unit_price": 500,
      "subtotal": 1000,
      "tax_rate": 0.16,
      "tax": 160,
      "total": 1160
    }
  ],
  "subtotal": 1000,
  "tax_total": 160,
  "total": 1160,
  "currency": "MXN"
}
```

### create_credit_note

Issue and stamp a credit note (CFDI de egreso) against one invoice. Access: write, asks the user first. REST: `POST /api/v1/facturama/invoices/{invoice_id}/credit-notes`. MCP: `facturama_write → create_credit_note`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | string | yes | The invoice the credit note corrects, from list_invoices. |
| `items` | array | yes | Credited lines. Each has description, quantity, unit_price and tax_rate. |
| `series` | string | no | Series of the credit note. Default: your default series. |

Issues a CFDI de egreso related to the invoice you name, for a return, a discount or a bonus, and stamps it with the SAT. Returns its invoice_id, series, folio, UUID and totals. The credit is final once the call succeeds. It does not email the note: use email_invoice for that. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_id": "Zq8RkV-aT2mNpLw4xYb7Hc1",
  "series": "NC",
  "folio": "12",
  "uuid": "0b7d44e1-92af-4c36-8d10-5ea7c3f19b02",
  "cfdi_type": "egreso",
  "status": "issued",
  "related_invoice_id": "Y61TLX-Ls_ZJFqzjanPN1w2",
  "items": [
    {
      "description": "Returned: design review hour",
      "quantity": 1,
      "unit_price": 500,
      "subtotal": 500,
      "tax_rate": 0.16,
      "tax": 80,
      "total": 580
    }
  ],
  "subtotal": 500,
  "tax_total": 80,
  "total": 580,
  "currency": "MXN"
}
```

### email_invoice

Send a stamped invoice or credit note to the client by email. Access: write, asks the user first. REST: `POST /api/v1/facturama/invoices/{invoice_id}/email`. MCP: `facturama_write → email_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | string | yes | Invoice ID from list_invoices or create_invoice. |
| `emails` | array | no | Recipient addresses. Default: the email saved on the client. |

Sends the document through Facturama's email to the address you give, or to the client's saved email when you give none. Fails with a not-found error when the ID does not exist. Calling it twice sends two emails. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_id": "Y61TLX-Ls_ZJFqzjanPN1w2",
  "sent_to": [
    "billing@estudionorte.example"
  ],
  "sent": true
}
```

### cancel_invoice

Cancel a stamped invoice or credit note with the SAT. Access: write, asks the user first. REST: `POST /api/v1/facturama/invoices/{invoice_id}/cancel`. MCP: `facturama_write → cancel_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | string | yes | Invoice ID from list_invoices or create_invoice. |
| `reason` | string | yes | The SAT cancellation reason code Facturama asks for. |
| `replacement_uuid` | string | no | UUID of the invoice that replaces this one, when the reason needs one. |

Asks the SAT to cancel one stamped document and returns its new status. The cancellation reason is the code the SAT asks for. A cancellation cannot be undone from here. Fails with a not-found error when the ID does not exist. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_id": "Y61TLX-Ls_ZJFqzjanPN1w2",
  "series": "FAC",
  "folio": "99",
  "status": "cancel_requested"
}
```

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

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

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

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

```
Here are this week's finished jobs. For each client, find them in Facturama (create the client if missing, and tell me), issue one CFDI invoice with 16% IVA, and email it to the client.
```

### Call Facturama 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/facturama 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/facturama/clients/cl_4821/invoices \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"items":[{"description":"Design review hour","quantity":2,"unit_price":500,"tax_rate":0.16}],"payment_form":"transfer","payment_method":"single payment"}'
```

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

```
{
  "invoice_id": "Y61TLX-Ls_ZJFqzjanPN1w2",
  "series": "FAC",
  "folio": "101",
  "uuid": "6f1c2a90-3b7e-4d55-9a1e-0c52b8e4d7a1",
  "cfdi_type": "ingreso",
  "status": "issued",
  "issued_at": "2026-10-14T10:32:00-06:00",
  "client": {
    "client_id": "cl_4821",
    "rfc": "XAXX010101000",
    "name": "Estudio Norte SA de CV"
  },
  "items": [
    {
      "description": "Design review hour",
      "quantity": 2,
      "unit_price": 500,
      "subtotal": 1000,
      "tax_rate": 0.16,
      "tax": 160,
      "total": 1160
    }
  ],
  "subtotal": 1000,
  "tax_total": 160,
  "total": 1160,
  "currency": "MXN"
}
```

## Why use Cotlet for Facturama?

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

## Is it safe to connect Facturama to Cotlet?

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

No, Cotlet is independent of Facturama. Facturama's own API comes only with a paid plan. Cotlet works through your own Facturama account, the way you use Facturama 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 Facturama in your console: your agents lose access at once and you stay signed in. Signing out of Facturama in the browser works too, and Reset browser deletes the whole profile.

## Is there a Facturama MCP server on GitHub?

No community Facturama MCP server turned up in our check. The realistic options are the official API, which you write code against, or doing each invoice by hand in the web app.

|  | Official API | Cotlet |
|---|---|---|
| Setup | Buy the API module, test in the sandbox, write code for the CFDI payload | Sign up, sign in to Facturama once, add one MCP server or API key |
| What you pay Facturama | API module (MXN 1,650 a year) plus prepaid API folios | Your invoicing plan only; Cotlet works in the web app with your folios |
| Your Facturama login | HTTP Basic Auth with your portal user and password in your code | Signed in inside your own Cloud Browser in the EU, profile encrypted; no password saved |
| When Facturama changes | You update your code when the SAT or the API changes | Our team tests it daily and fixes it for you; failed calls are free |
| Use from an AI agent | No MCP server; you build the tool layer | MCP for Claude Code, Codex and Cursor, and the same tools as REST |
| Upkeep | You host, monitor and debug your integration | Nothing to host or update |
| Price | Module and folios, no code cost counted | 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 Facturama 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 Facturama API cost?

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

**Do I need to be technical?**

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

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

Facturama 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 the Facturama API module or API folios for Cotlet?**

No. Cotlet signs in to your own Facturama account and works in the web app, so it uses the invoicing folios of your plan. The API module (MXN 1,650 a year) and the prepaid API folios, which only work through the API, are not needed. Cotlet can only do what your plan allows on screen.

**Can the agent edit a stamped invoice?**

No. Each CFDI is a legal tax act once stamped with the SAT. A wrong invoice is fixed by cancel_invoice or by create_credit_note, and every tool that stamps or cancels asks for your OK by default.

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

No. Every call to create_invoice, create_credit_note, email_invoice or cancel_invoice 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_client runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Facturama 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/facturama 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.