Cotlet

Your AI agent, logged in to the apps that never built an API.

One hosted MCP server for all your apps. A REST API too.

Website · Integrations · Docs · MCP server · REST API · Pricing · Security · Request access · X

What is Cotlet?

Cotlet is a catalog of hosted integrations for web apps that have no official API, or only a narrow one. Each integration is exposed two ways:

• as tools in one remote MCP server (https://cotlet.dev/mcp/v1) for AI agents such as Claude, ChatGPT, Cursor, Codex, GitHub Copilot, Gemini, Windsurf and n8n;
• as a REST API (https://cotlet.dev/api/v1) for your own scripts and cron jobs.

Every account gets its own Chrome in the cloud, the Cloud Browser. Sign in to your apps there yourself, once, enable them for your agents, and your agent works in your own account 24/7, even when your computer is off: it moves bookings, sends invoices, approves members, pulls reports, relists items. Cotlet never saves your password, and every background request is listed.

In one sentence: Cotlet lets your AI agent sign in to the apps you click through by hand and do the work over MCP, without waiting for the vendor to ship an API.

The problem

You asked your agent to do something. It hit a login page.

• "Send this month's invoice." No API for this app.
• "Move Friday's bookings to Monday." No API for this app.
• "Pull the weekly report from the CRM." No API for this app.

So you clicked through it yourself. Again.

AI agents are good at doing work, but they can only reach tools that expose an API or an MCP server. Most of the software that small businesses and creators live in every day does not: community platforms, booking systems, course platforms, marketplaces, property portals, field-service and invoicing tools. When an API exists at all, it is often:

• missing: no public API, no developer docs, no keys;
• limited: read-only, or missing the endpoints people actually need (DMs, drafts, coupons, reports);
• gated: partners only, after an application, a contract or a review;
• paid: locked behind a top plan or a separate add-on.

Of the 97 apps in the Cotlet catalog today, 26 have no official API at all, 31 have a limited one, 28 are partners-only and 12 sell API access as a paid add-on. Read more in docs/problem.md.

The solution

Cotlet builds and maintains the missing access, then hands it to your agent as ordinary tools.

 You ──sign in once──▶ Your Cloud Browser (Chrome in the cloud) ──▶ App (Skool, Booksy, Substack, ...)
                                   ▲
 Your agent ──MCP / REST──▶ Cotlet ┘  same requests as your browser: its IP, its cookies

1. Pick your apps from the catalog, or request one that is missing.
2. Sign in once to each app yourself, in your Cloud Browser, and press Enable for agents (read only or read and write). Password saving is off.
3. Add Cotlet to your agent with one MCP URL. Every app you connect shows up as tools.
4. Let the agent do it, on request or on a schedule. The chore is gone.

Full walkthrough: docs/how-it-works.md.

Quick start

Connect your agent over MCP

claude mcp add --transport http cotlet https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"

{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}

[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"

Then just ask:

"Approve all pending membership requests in my Skool community and welcome them in a post."

Your agent calls skool_list_members, skool_approve_membership_request and skool_create_post, signed in as you. Setup details: docs/mcp-server.md.

Or call it from a script

curl -X POST https://cotlet.dev/api/v1/skool/list_members \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"group": "yourgroup", "role": "admin"}'

Same key, same inputs, same outputs as MCP. Reference: docs/rest-api.md.

Integrations

97 apps in 6 categories. Each one has its own page on cotlet.dev with the official API status, sources, and every tool with its parameters.

Full catalog with every app, its official API status and its tools: docs/integrations.md.

Ready-made Python scripts per app: Skool API and MCP server (export members, approve membership requests, posts, DMs, stats), Substack API and MCP server (schedule posts and Notes from Markdown, export subscribers and posts, comments, stats).

Missing an app? Request it on cotlet.dev, no account needed. If enough people ask, we add it.

Security and trust

Your login stays yours. The model never sees it.

• You sign in yourself, in your own browser. One Cloud Browser per workspace, never shared. Password saving is off, so Cotlet never saves your password; the profile is stored encrypted with AES-256-GCM.
• Your agents only get the apps you enable. Signing in alone gives them nothing.
• Every background request is listed. To be fast, Cotlet doesn't click through pages: it sends the same requests your browser would, from its IP with its cookies, and lists each one in your Background activity.
• The AI model never sees a login. Agents call tools, not cookies.
• No payload retention. Data passes through a call to your agent and is not kept.
• Scoped access. Each app is read only or read and write, each API key can be narrowed further, and actions that reach other people wait for your OK by default.
• Cut access in one click. Disable for agents, sign out of the app in the browser, or Reset browser.
• What we never do: break CAPTCHAs, bypass MFA, automate banks without a licence, touch LinkedIn or Instagram, keep going after a cease-and-desist, or store your data longer than the call.
• Checked by independent scanners: A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
• Hosted in the EU: the console, API, database and Cloud Browsers run in a data centre in Finland.

More: docs/security.md and cotlet.dev/security.

Pricing

Pay as you go, no subscription: one-time credit packs, valid 12 months. Every account starts with a free 7-day trial and 2,000 credits, no card needed.

Two things use credits: a successful call (20 to 30 credits, 25 for most tools) and your Cloud Browser (50 credits a day while it has an app enabled for agents, however many apps that is). Failed calls cost nothing, and nothing is charged without a purchase. Details: docs/pricing.md.

Why not a script from GitHub?

Scripts break when the app changes, and you fix them yourself. Cotlet tests every integration daily, pauses calls when a site changes, ships the fix and refunds credits for failed calls. You get a stable tool name and schema; how Cotlet reaches each app is our job. Comparison: docs/comparison.md.

Documentation in this repository

Links

• Website: cotlet.dev
• Integrations: cotlet.dev/integrations
• Use cases: cotlet.dev/use-cases
• How it works: cotlet.dev/how-it-works
• Docs: cotlet.dev/docs (Markdown: cotlet.dev/docs.md)
• For AI agents: cotlet.dev/llms.txt
• Pricing: cotlet.dev/pricing
• Security: cotlet.dev/security
• For developers: cotlet.dev/for-developers
• For agencies: cotlet.dev/for-agencies
• Blog: cotlet.dev/blog
• Changelog: cotlet.dev/changelog
• About: cotlet.dev/about
• Contact: cotlet.dev/contact · contact@cotlet.dev
• GitHub: github.com/cotletdev
• X: @cotletdev
• Skool API and MCP server: github.com/cotletdev/skool-api-mcp-server
• Substack API and MCP server: github.com/cotletdev/substack-api-mcp-server

About

Cotlet is built in Europe for people who work with AI agents, worldwide. It is run by Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland (KRS 0000871398, NIP 6342984273).

Cotlet is independent. Product names in the catalog are trademarks of their owners; Cotlet is unofficial and not affiliated with, or endorsed by, any app it integrates with. You use your own account and stay responsible for following each app's terms.