How it works
Sign in once. Your agent does the clicking
Four steps from your app to a chore you never do again.
- Step 1
Find your app
Pick it from the catalog. Its tools are ready to use.
- Step 2
Sign in with your account
You log in on the app yourself. We never see or store your password.
AES-256 Allowed actions You decide what agents can do List bookings Create booking Update client Delete client - Step 3
Add it to Claude over MCP
Paste one MCP URL into Claude. Your app shows up as tools.
agent > What are today's bookings? MCP list_bookings({ "date": "today" }) response [{ "time": "09:30", "guest": "A. Kim" }, { "time": "12:00", "guest": "J. Ruiz" }] MCP tools/call list_bookings 200 OK - Step 4
Automate it and forget it
Your agent does the work on request or on a schedule. The chore is gone.
Weekly bookings report Every Monday, 8:00 Last runs Mon, Oct 5 14 bookings exported Mon, Sep 28 11 bookings exported Mon, Sep 21 16 bookings exported Next run: Mon, Oct 12
Your password and data stay yours
We work like OpenRouter: your data passes through and is never kept.
-
No password stored
You sign in yourself. We keep only an encrypted session you can revoke.
-
We do not see your data
It goes from the app straight to your agent. Nobody at Cotlet reads it.
-
Nothing saved to disk
Results live in memory for the call and are gone after it.
When a site changes
Every integration has its own status page.
-
Daily canary tests
Every integration is tested every day.
-
Auto-pause
Calls pause until the fix ships.
-
Credits refunded
Failed calls never cost you credits.
Your app is not in the catalog?
Tell us which one. If enough people ask, we add it.