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

# Recurly API and MCP server

> Yes, Recurly has a full REST API for accounts, subscriptions, invoices, transactions and coupon redemptions (checked 14 Oct 2026). It authenticates with one private API key for the whole site, and Recurly's own MCP server, Compass, only searches the docs and writes code examples; it does not change your billing data.

Subscription billing platform for recurring-revenue businesses: accounts, plans, subscriptions, invoices, transactions, coupons and dunning for past-due payments, managed in the Recurly Admin Console.

## What is the Recurly API?

Cotlet's Recurly API exposes 11 endpoints for your own Recurly account: list accounts, get account, list subscriptions, list invoices, get invoice, list transactions, change subscription, cancel subscription, postpone subscription, refund invoice and redeem coupon. The list_accounts endpoint returns accounts with code, name, email, company and state. Each endpoint takes simple JSON inputs like per_page, cursor or state and works both as an operation of the recurly_read or recurly_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-22

Yes, Recurly has a full REST API for accounts, subscriptions, invoices, transactions and coupon redemptions (checked 14 Oct 2026). Cotlet is a hosted MCP server and REST API for Recurly with 11 endpoints (6 read, 5 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Recurly have an official API?

Yes, Recurly has a full REST API for accounts, subscriptions, invoices, transactions and coupon redemptions (checked 14 Oct 2026). It authenticates with one private API key for the whole site, and Recurly's own MCP server, Compass, only searches the docs and writes code examples; it does not change your billing data.

| Task | Recurly official | Cotlet |
|---|---|---|
| List and open accounts | Yes: GET /accounts, filter by state active or closed | Yes |
| List past-due subscriptions | Yes: GET /subscriptions with state past_due | Yes |
| List invoices and see their state | Yes: GET /invoices, state open, collected, failed or past_due | Yes |
| Change a subscription | Yes: PUT /subscriptions/{uuid}, timeframe now or renewal | Yes |
| Cancel a subscription | Yes: Stays active to the end of the current bill cycle | Yes |
| Postpone (pause) a subscription | Yes: Paused until a date you set, not prorated | Yes |
| Refund an invoice by line item | Yes: POST /invoices/{invoice_number}/refund | Yes |
| Apply a coupon to an account | Yes: Redeemed before or after a subscription | Yes |

Sources: [Recurly Docs: Compass public MCP server](https://docs.recurly.com/recurly-subscriptions/docs/compass-public-mcp-server), [Recurly Docs: Quick-start guide (private API key)](https://docs.recurly.com/recurly-subscriptions/docs/quick-start-guide), [Recurly API reference: Update Subscription](https://docs.recurly.com/recurly-subscriptions/reference/updatesubscription), [Recurly on Zapier: triggers and actions](https://zapier.com/apps/recurly/integrations)

## For AI agents

```text
Yes, Recurly has a full REST API for accounts, subscriptions, invoices, transactions and coupon redemptions (checked 14 Oct 2026). It authenticates with one private API key for the whole site, and Recurly's own MCP server, Compass, only searches the docs and writes code examples; it does not change your billing data.
Cotlet provides a hosted MCP server and REST API for Recurly: 11 tools (6 read, 5 write).
Access       Sign up at https://cotlet.dev/app/signup?app=recurly, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    recurly_read, recurly_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/recurly, each operation at its own route, e.g. POST /api/v1/recurly/invoices/{invoice_number}/refund
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_accounts, get_account, list_subscriptions, list_invoices, get_invoice, list_transactions, change_subscription, cancel_subscription, postpone_subscription, refund_invoice, redeem_coupon
Confirm      change_subscription, cancel_subscription, postpone_subscription, refund_invoice, redeem_coupon (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/recurly-api-mcp-server.md

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

## What can an AI agent do in Recurly?

Cotlet is best for billing and support teams on Recurly who want an agent to find past-due accounts, change or cancel subscriptions and issue refunds without running or fixing a server.

- **[List past-due accounts](https://cotlet.dev/integrations/recurly-api-mcp-server/list-past-due-accounts.md)** (runs: daily): "Every morning, list Recurly subscriptions that are past due. For each, show the account, the unpaid invoice and its amount, and sort by the oldest invoice first." → `list_subscriptions`, `list_invoices`, `get_account`
- **[Refund an invoice line item](https://cotlet.dev/integrations/recurly-api-mcp-server/refund-invoice-line-item.md)**: "Refund 1 unit of the setup fee on invoice 1042 back to the account, then show me the refund invoice." → `get_invoice`, `refund_invoice`
- **[Cancel subscriptions at the end of the term](https://cotlet.dev/integrations/recurly-api-mcp-server/cancel-subscription-at-term-end.md)**: "Cancel the subscriptions of acme-co and bright-lab at the end of their current term, and tell me the date each one ends." → `list_subscriptions`, `cancel_subscription`
- **Downgrade a plan at renewal**: "Move the subscription of bright-lab to the starter plan at renewal, and show me what it will cost." → `list_subscriptions`, `change_subscription`
- **Apply a coupon to an account**: "Redeem the coupon WINBACK20 for account north-yard and tell me when it will be applied." → `get_account`, `redeem_coupon`

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

Yes. Cotlet does not replace your automation platform: it gives it a Recurly 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 list past-due accounts, 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/recurly/subscriptions. | 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/recurly/subscriptions 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 Recurly.

### list_accounts

Accounts with code, name, email, company and state. Access: read. REST: `GET /api/v1/recurly/accounts`. MCP: `recurly_read → list_accounts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `state` | enum | no | active or closed. Default: all. |
| `per_page` | integer | no | 1 to 200. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists Recurly accounts, 50 per page by default and up to 200. Filter by state active or closed. Each item carries the account_code you pass to the other tools. An account can sit in more than one state view, so check the state field in each item.

Example response:

```json
{
  "accounts": [
    {
      "account_code": "acme-co",
      "state": "active",
      "company_name": "Acme Co",
      "email": "billing@acme.example",
      "first_name": "Dana",
      "last_name": "Reed",
      "created_at": "2026-03-02T10:14:00Z"
    },
    {
      "account_code": "north-yard",
      "state": "active",
      "company_name": "North Yard",
      "email": "ap@northyard.example",
      "first_name": "Lee",
      "last_name": "Park",
      "created_at": "2026-04-19T08:41:00Z"
    }
  ],
  "total": 2,
  "next_cursor": null
}
```

### get_account

One account with contact details, tax fields and links to its subscriptions and invoices. Access: read. REST: `GET /api/v1/recurly/accounts/{account_code}`. MCP: `recurly_read → get_account`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `account_code` | string | yes | Account code from list_accounts. |

Returns one account by account_code: name, company, email, address, VAT number, whether it is tax exempt and its state. Use it to see who the customer is before you change a subscription or refund an invoice.

Example response:

```json
{
  "account_code": "acme-co",
  "state": "active",
  "company_name": "Acme Co",
  "email": "billing@acme.example",
  "first_name": "Dana",
  "last_name": "Reed",
  "country": "US",
  "tax_exempt": false,
  "created_at": "2026-03-02T10:14:00Z"
}
```

### list_subscriptions

Subscriptions with plan, state, quantity, price and renewal dates. Access: read. REST: `GET /api/v1/recurly/subscriptions`. MCP: `recurly_read → list_subscriptions`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `state` | enum | no | active, canceled, expired, future, in_trial, live or past_due. Default: all. |
| `per_page` | integer | no | 1 to 200. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists subscriptions, 50 per page by default and up to 200. Filter by state; past_due returns active or canceled subscriptions that have an overdue invoice. Each item has the subscription_id for the write tools, the plan code, the unit amount in cents and the current period end.

Example response:

```json
{
  "subscriptions": [
    {
      "subscription_id": "44f83d0cbf86d2b8a5b3d3e6c3e8b16f",
      "account_code": "acme-co",
      "plan_code": "team",
      "state": "active",
      "quantity": 1,
      "unit_amount_in_cents": 24000,
      "currency": "USD",
      "current_period_ends_at": "2026-11-14T00:00:00Z"
    }
  ],
  "total": 1,
  "next_cursor": null
}
```

### list_invoices

Invoices with number, account, state, totals and dates. Access: read. REST: `GET /api/v1/recurly/invoices`. MCP: `recurly_read → list_invoices`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `state` | enum | no | open, collected, failed or past_due. Default: all. |
| `per_page` | integer | no | 1 to 200. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists invoices, 50 per page by default and up to 200. Filter by state: open, collected, failed or past_due. Each invoice has exactly one state. Totals are in cents with the currency, and each item has the invoice_number used by get_invoice and refund_invoice.

Example response:

```json
{
  "invoices": [
    {
      "invoice_number": "1042",
      "account_code": "acme-co",
      "state": "past_due",
      "subtotal_in_cents": 24000,
      "tax_in_cents": 0,
      "total_in_cents": 24000,
      "currency": "USD",
      "created_at": "2026-09-06T07:00:00Z"
    },
    {
      "invoice_number": "1077",
      "account_code": "bright-lab",
      "state": "past_due",
      "subtotal_in_cents": 9900,
      "tax_in_cents": 0,
      "total_in_cents": 9900,
      "currency": "USD",
      "created_at": "2026-09-21T07:00:00Z"
    }
  ],
  "total": 2,
  "next_cursor": null
}
```

### get_invoice

One invoice with its line items, state and totals. Access: read. REST: `GET /api/v1/recurly/invoices/{invoice_number}`. MCP: `recurly_read → get_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_number` | string | yes | Invoice number from list_invoices. |

Returns one invoice by invoice_number: line items with their ids, quantities and amounts, the state, the totals and the linked subscription. Read it before refund_invoice to pick the right line item_id and to see what was already refunded.

Example response:

```json
{
  "invoice_number": "1042",
  "account_code": "acme-co",
  "state": "collected",
  "line_items": [
    {
      "line_item_id": "3dc1a8f09b4c4e55a1e0",
      "description": "Setup fee",
      "quantity": 2,
      "unit_amount_in_cents": 900,
      "total_in_cents": 1800
    },
    {
      "line_item_id": "9ab07e22c15f4b0d8e61",
      "description": "Team plan",
      "quantity": 1,
      "unit_amount_in_cents": 24000,
      "total_in_cents": 24000
    }
  ],
  "subtotal_in_cents": 25800,
  "tax_in_cents": 0,
  "total_in_cents": 25800,
  "currency": "USD"
}
```

### list_transactions

Payments and refunds of an account with amount, status and date. Access: read. REST: `GET /api/v1/recurly/accounts/{account_code}/transactions`. MCP: `recurly_read → list_transactions`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `account_code` | string | yes | Account code from list_accounts. |
| `per_page` | integer | no | 1 to 200. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists the transactions of one account, newest first: payments, refunds and failed attempts, with the amount in cents and the invoice each belongs to. Use it to see why an invoice is past due before you act on it.

Example response:

```json
{
  "transactions": [
    {
      "transaction_id": "tx_7e31a4",
      "account_code": "acme-co",
      "invoice_number": "1042",
      "type": "purchase",
      "status": "declined",
      "amount_in_cents": 24000,
      "currency": "USD",
      "created_at": "2026-09-07T07:02:00Z"
    }
  ],
  "total": 1,
  "next_cursor": null
}
```

### change_subscription

Change the plan or quantity of a subscription now, on the next bill date or at renewal. Access: write, asks the user first. REST: `PATCH /api/v1/recurly/subscriptions/{subscription_id}`. MCP: `recurly_write → change_subscription`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `subscription_id` | string | yes | Subscription UUID from list_subscriptions. |
| `plan_code` | string | no | New plan code. Omit to keep the plan. |
| `quantity` | integer | no | New quantity. Omit to keep it. |
| `timeframe` | enum | no | now, bill_date or renewal. Default: now. |
| `proration` | enum | no | For immediate changes: prorated, full or none. Default: the site setting. |
| `add_ons` | array | no | Add-on codes that should exist after the change. Add-ons you leave out are removed. |

Changes the plan or the quantity of one subscription. With timeframe now the change applies at once, an invoice is created and, with automatic collection, a payment is attempted right away. With bill_date or renewal it applies later with no proration. Only one pending change is kept, and a new one replaces it. Existing add-ons are removed unless you list them in add_ons. Changes bill or credit the customer. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "subscription_id": "44f83d0cbf86d2b8a5b3d3e6c3e8b16f",
  "account_code": "bright-lab",
  "plan_code": "starter",
  "state": "active",
  "timeframe": "renewal",
  "effective_at": "2026-11-02T00:00:00Z",
  "status": "pending"
}
```

### cancel_subscription

Cancel a subscription so it stops renewing; access continues until the end date. Access: write, asks the user first. REST: `POST /api/v1/recurly/subscriptions/{subscription_id}/cancel`. MCP: `recurly_write → cancel_subscription`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `subscription_id` | string | yes | Subscription UUID from list_subscriptions. |
| `timing` | enum | no | immediately, next_billing_cycle or end_of_term. Default: the end of the current bill cycle. |

Cancels one subscription at the timing you choose: immediately, at the next billing cycle or at the end of the term. It stays active until then, and can be reactivated in Recurly before it expires. After expiry you need a new subscription. A subscription set to start in the future is deleted instead. It does not terminate, which ends access now. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "subscription_id": "44f83d0cbf86d2b8a5b3d3e6c3e8b16f",
  "account_code": "acme-co",
  "state": "canceled",
  "canceled_at": "2026-10-14T10:20:00Z",
  "expires_at": "2026-11-14T00:00:00Z"
}
```

### postpone_subscription

Pause an active subscription until a date you set. Access: write, asks the user first. REST: `POST /api/v1/recurly/subscriptions/{subscription_id}/postpone`. MCP: `recurly_write → postpone_subscription`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `subscription_id` | string | yes | Subscription UUID from list_subscriptions. |
| `renewal_date` | date | yes | Date the subscription renews again. |

Pauses an active subscription until the renewal date you give. The postponed period is not prorated. For a subscription in a trial, changing the renewal date changes when the trial ends. It changes when the customer is next billed. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "subscription_id": "44f83d0cbf86d2b8a5b3d3e6c3e8b16f",
  "account_code": "north-yard",
  "state": "active",
  "next_renewal_at": "2026-12-01T00:00:00Z"
}
```

### refund_invoice

Refund a line item or the whole invoice by quantity, amount or percentage. Access: write, asks the user first. REST: `POST /api/v1/recurly/invoices/{invoice_number}/refund`. MCP: `recurly_write → refund_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_number` | string | yes | Invoice number from list_invoices. |
| `method` | enum | yes | quantity, amount or percentage. |
| `line_item_id` | string | no | Line item from get_invoice. Omit to refund the entire invoice (amount or percentage only). |
| `quantity` | integer | no | Units to refund. Required for method quantity. |
| `amount_in_cents` | integer | no | Amount to refund. Required for method amount. |
| `percentage` | integer | no | Percentage to refund. Required for method percentage. |
| `prorate` | boolean | no | Prorate the refunded line item. Default: false. |
| `refund_apply_order` | enum | no | credit or transaction. Default: credit. |

Refunds part or all of one invoice and creates a refund credit invoice with credit line items against the paid charges. Methods: quantity on a line item, a specific amount, or a percentage. Amount and percentage refunds on a line item need the Only Bill What Changed and Credit Memos features on your site. The money goes back as account credit by default; refund_apply_order transaction sends it to the payment method first. It moves money to the customer. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "refund_invoice_number": "1105",
  "original_invoice_number": "1042",
  "state": "collected",
  "subtotal_in_cents": -900,
  "total_in_cents": -900,
  "currency": "USD",
  "refund_apply_order": "credit"
}
```

### redeem_coupon

Attach a coupon to an account before or after a subscription. Access: write, asks the user first. REST: `POST /api/v1/recurly/accounts/{account_code}/coupons/{coupon_code}/redeem`. MCP: `recurly_write → redeem_coupon`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `account_code` | string | yes | Account code from list_accounts. |
| `coupon_code` | string | yes | Coupon code as created in Recurly. |
| `currency` | string | no | Currency of the redemption, for example USD. |

Redeems a coupon code for one account. Recurly holds the redemption on the account and applies it at the next subscription creation, change or renewal, so it changes what the customer pays. Returns the total discounted so far and the currency. A wrong code or currency fails with a validation error. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "account_code": "north-yard",
  "coupon_code": "WINBACK20",
  "currency": "USD",
  "total_discounted_in_cents": 0,
  "created_at": "2026-10-14T10:31:00Z"
}
```

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

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

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

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

```
Every morning, list Recurly subscriptions that are past due. For each, show the account, the unpaid invoice and its amount, and sort by the oldest invoice first.
```

### Call Recurly 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/recurly 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/recurly/invoices/1042/refund \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"method":"quantity","line_item_id":"3dc1a8f09b4c4e55a1e0","quantity":1,"refund_apply_order":"credit"}'
```

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

```
{
  "refund_invoice_number": "1105",
  "original_invoice_number": "1042",
  "state": "collected",
  "subtotal_in_cents": -900,
  "total_in_cents": -900,
  "currency": "USD",
  "refund_apply_order": "credit"
}
```

## Why use Cotlet for Recurly?

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

## Is it safe to connect Recurly to Cotlet?

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

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

## Is there a Recurly MCP server on GitHub?

Yes. Community Recurly MCP servers exist on GitHub, usually maintained by one person, and some are read-only. You install one on your own computer, give it your site's private API key, and keep it running yourself; when Recurly changes its API, it stops working until you or the maintainer fix it. The official API is the other route: you create a key and write the calls yourself. Cotlet hosts the same kind of server for you, signs in to your Recurly account in a browser, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Create a private API key, install the server, add the key to each MCP client | Sign up, sign in to Recurly once, add one MCP server or API key |
| When Recurly 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 Recurly access | A site-wide private key in a file on your computer, with the same reach as an admin | Signed in inside your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When access expires | Tools fail until you fix the key or sign in again by hand | Your Cloud Browser keeps you signed in; if Recurly 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 Recurly 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 Recurly API cost?

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

**Do I need to be technical?**

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

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

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

**Do I need an API key or a special Recurly plan?**

No. Cotlet works through your own Recurly sign-in, so you do not create a private API key under Integrations > API Keys. The user you sign in with must be allowed to do the task by hand, such as issuing a refund.

**Can my agent refund an invoice without asking me?**

Only if you switch confirmation off for refund_invoice. By default every call that moves money, such as refunds, plan changes, cancellations and coupon redemptions, waits for your OK.

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

No. Every call to change_subscription, cancel_subscription, postpone_subscription, refund_invoice or redeem_coupon 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 Recurly 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/recurly 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.