[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) # Ringover API and MCP server > Ringover has a public REST API and an official MCP server, but the MCP server only reads (checked 23 Oct 2026). The API returns calls, contacts, users, IVRs and SMS messages and uses an API key with rights per area. The MCP server has 36 read-only tools for contacts, calls, transcriptions and phone settings, and it has no SMS, call or contact write tools. Cloud business phone system: calls, SMS, call recordings with transcripts, call tags, a shared contact directory and call flows in one web and desktop app. ## What is the Ringover API? Cotlet's Ringover API exposes 11 endpoints for your own Ringover account: list calls, get call, get call transcript, list missed calls and voicemails to follow up, search contacts, list SMS conversations, get SMS conversation, list call tags, add a tag to a call, remove a tag from a call and send an SMS. The list_calls endpoint returns calls of your account for a period, newest first, with direction, state, duration, contact and tags. Each endpoint takes simple JSON inputs like limit, call_id or cursor and works both as an operation of the ringover_read or ringover_write MCP tool for agents and as a REST call for scripts. - **Category:** [Customer support](https://cotlet.dev/integrations/category/customer-support.md) - **Endpoints:** 11 (8 read, 3 write) - **Updated:** 2026-10-24 Ringover has a public REST API and an official MCP server, but the MCP server only reads (checked 23 Oct 2026). Cotlet is a hosted MCP server and REST API for Ringover with 11 endpoints (8 read, 3 write): you sign in once in your own cloud browser, your AI agent does the work. ## Does Ringover have an official API? Ringover has a public REST API and an official MCP server, but the MCP server only reads (checked 23 Oct 2026). The API returns calls, contacts, users, IVRs and SMS messages and uses an API key with rights per area. The MCP server has 36 read-only tools for contacts, calls, transcriptions and phone settings, and it has no SMS, call or contact write tools. | Task | Ringover official | Cotlet | |---|---|---| | List calls for a period | Yes: API and MCP server, within the rights of the API key | Yes | | Read call details with notes and tags | Yes: API and MCP server | Yes | | Read a call transcript | Yes: MCP server and API; the transcription feature must be on for the team | Yes | | Search contacts by name, number or company | Yes: MCP server, read only | Yes | | Read SMS conversations | Yes: API returns SMS messages; the MCP server has no SMS tools | Yes | | Send an SMS | Partly: API, Make and Zapier can send; the official MCP server cannot | Yes | | Tag a call | Partly: The official MCP server is read-only; the Make app only watches tag changes | Yes | | List missed calls and voicemails to follow up | Partly: MCP server reads the call history; no action list like the Conversations tab "To Do" view | Yes | Sources: [Ringover blog: Ringover MCP server](https://www.ringover.com/blog/mcp-server), [Ringover Help: Using our API](https://support.ringover.com/hc/en-us/articles/15206971712657-Using-our-API), [Make: Ringover integration](https://www.make.com/integrations/ringover), [Zapier: Ringover integrations](https://zapier.com/apps/ringover/integrations) ## Quick reference ```text Ringover has a public REST API and an official MCP server, but the MCP server only reads (checked 23 Oct 2026). The API returns calls, contacts, users, IVRs and SMS messages and uses an API key with rights per area. The MCP server has 36 read-only tools for contacts, calls, transcriptions and phone settings, and it has no SMS, call or contact write tools. Cotlet provides a hosted MCP server and REST API for Ringover: 11 tools (8 read, 3 write). Access Sign up at https://cotlet.dev/app/signup?app=ringover, then request the app and create API keys in the Cotlet console. MCP server https://cotlet.dev/mcp/v1 MCP tools ringover_read, ringover_write, reads and writes apart; call one with {"operation": "", "arguments": {...}} REST base https://cotlet.dev/api/v1/ringover, each operation at its own route, e.g. POST /api/v1/ringover/froms/{from_number}/sms Auth Authorization: Bearer . Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in. Operations list_calls, get_call, get_call_transcript, list_todo_conversations, search_contacts, list_sms_conversations, get_sms_conversation, list_call_tags, add_call_tag, remove_call_tag, send_sms Confirm send_sms (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/ringover-api-mcp-server.md How access works: 1. The user signs up at https://cotlet.dev/app/signup?app=ringover, requests Ringover in the Cotlet console and creates an API key there. 2. The user signs in to Ringover once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Ringover 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 Ringover 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 Ringover 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 Ringover 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 Ringover 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 Ringover 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 Ringover's terms; Cotlet is not affiliated with Ringover. ``` ## What can an AI agent do in Ringover? Cotlet is best for sales and support teams on Ringover who want an AI agent to tag calls and text missed callers without running or fixing a server. - **[Tag calls by outcome](https://cotlet.dev/integrations/ringover-api-mcp-server/tag-calls-by-outcome.md)** (runs: daily): "Go through yesterday's answered Ringover calls longer than a minute. Read each transcript and tag it with one of my call tags: Demo booked, Price question, Support, or No fit. Leave a call untagged if none fits." → `list_calls`, `get_call_transcript`, `list_call_tags`, `add_call_tag` - **[Text back missed callers](https://cotlet.dev/integrations/ringover-api-mcp-server/text-back-missed-callers.md)** (runs: daily): "Check Ringover for calls missed during the last 2 hours. For each new caller, send one SMS from our sales mobile number: sorry we missed you, we will call back today. Skip anyone I already texted this week." → `list_todo_conversations`, `list_sms_conversations`, `search_contacts`, `send_sms` - **Find calls that mention a topic**: "Search my Ringover calls from the last 14 days for ones where the customer says they are comparing us with another provider. List the call, the sentence and the contact." → `list_calls`, `get_call_transcript`, `search_contacts` - **Daily call summary for your team** (runs: daily): "Summarize yesterday's Ringover calls: how many answered, missed and voicemail, the longest 3 calls, and which calls have no tag. Post it here as a short list." → `list_calls`, `get_call` - **Answer SMS replies**: "Read the unread SMS threads on our sales mobile number. For each, draft a reply from my notes and send the ones that only confirm a time." → `list_sms_conversations`, `get_sms_conversation`, `send_sms` ## Can Ringover automations run on a schedule in n8n, Make or Zapier? Yes. Cotlet does not replace your automation platform: it gives it a Ringover 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 tag calls by outcome, 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/ringover/calls. | 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/ringover/calls 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 Ringover. ### list_calls Calls of your account for a period, newest first, with direction, state, duration, contact and tags. Access: read. REST: `GET /api/v1/ringover/calls`. MCP: `ringover_read → list_calls`. | Parameter | Type | Required | Description | |---|---|---|---| | `from` | datetime | no | Calls that started at or after this time (ISO 8601). | | `to` | datetime | no | Calls that started before this time (ISO 8601). | | `status` | enum | no | answered, missed or voicemail. Default: all. | | `direction` | enum | no | incoming or outgoing. Default: both. | | `limit` | integer | no | How many calls per page. | | `cursor` | string | no | Next page cursor from the previous call. | Lists calls from the call log, newest first, one page at a time; pass next_cursor back as cursor for the next page. status filters by the call state: answered, missed or voicemail. direction is incoming or outgoing. duration_seconds is the talk time, 0 for a call nobody answered. Calls follow what your Ringover user can see in the call logs. call_id goes into get_call and get_call_transcript. Example response: ```json { "calls": [ { "call_id": "c_91e04a77", "direction": "incoming", "status": "answered", "started_at": "2026-10-22T09:14:00Z", "duration_seconds": 412, "contact": "Dana Whitfield", "number": "+15550100142", "user": "Sam Reyes", "tags": [] }, { "call_id": "c_91e04a80", "direction": "incoming", "status": "missed", "started_at": "2026-10-22T09:31:00Z", "duration_seconds": 0, "contact": null, "number": "+15550100177", "user": null, "tags": [] } ], "next_cursor": "eyJwIjoyfQ" } ``` ### get_call One call with its contact, user, number, notes, tags and whether a recording and transcript exist. Access: read. REST: `GET /api/v1/ringover/calls/{call_id}`. MCP: `ringover_read → get_call`. | Parameter | Type | Required | Description | |---|---|---|---| | `call_id` | string | yes | Call ID from list_calls. | Returns the call details panel of the call log: who called whom, the Ringover number, the user who answered, duration, notes, tags and the AI call summary when Ringover made one. has_recording and has_transcript tell whether the recording player and the Transcript tab exist; both depend on call recording being on for the user. Notes and tags are those saved after the call. Example response: ```json { "call_id": "c_91e04a77", "direction": "incoming", "status": "answered", "started_at": "2026-10-22T09:14:00Z", "duration_seconds": 412, "contact": "Dana Whitfield", "number": "+15550100142", "ringover_number": "+15550100100", "user": "Sam Reyes", "notes": "Wants a demo for 5 seats.", "tags": [ "Price question" ], "has_recording": true, "has_transcript": true, "summary": "Dana asked about pricing for 5 seats and agreed to a demo on Thursday at 10:00." } ``` ### get_call_transcript The full text of a recorded call, in order, with who said what. Access: read. REST: `GET /api/v1/ringover/calls/{call_id}/transcript`. MCP: `ringover_read → get_call_transcript`. | Parameter | Type | Required | Description | |---|---|---|---| | `call_id` | string | yes | Call ID from list_calls. | Returns the Transcript tab of a call as lines in order, each with the speaker and a time offset in seconds. It works for calls with a recording where transcription is enabled for the team; any other call answers that no transcript exists. The text is as Ringover wrote it and may contain recognition errors. Example response: ```json { "call_id": "c_91e04a77", "lines": [ { "speaker": "Sam Reyes", "at_seconds": 3, "text": "Thanks for calling, how can I help?" }, { "speaker": "Dana Whitfield", "at_seconds": 6, "text": "Hi, I would like to know the price for five seats." }, { "speaker": "Sam Reyes", "at_seconds": 14, "text": "Happy to show you. Does Thursday at 10 work for a demo?" } ] } ``` ### list_todo_conversations Contacts with pending tasks, missed calls and voicemails, as the To Do view of the Conversations tab shows them. Access: read. REST: `GET /api/v1/ringover/todo-conversations`. MCP: `ringover_read → list_todo_conversations`. | Parameter | Type | Required | Description | |---|---|---|---| | `reason` | enum | no | missed_call, voicemail or task. Default: all. | | `limit` | integer | no | How many entries per page. | | `cursor` | string | no | Next page cursor from the previous call. | Returns the entries of the To Do view in the Conversations tab, newest first: the contact or number, the reason (missed call, voicemail or task) and when it happened. Use it to find people who still wait for an answer. It follows what your Ringover user sees. Calls already answered back are not shown by Ringover in this view. Example response: ```json { "items": [ { "contact": null, "number": "+15550100177", "reason": "missed_call", "at": "2026-10-22T09:31:00Z", "call_id": "c_91e04a80" }, { "contact": "Marta Kowal", "number": "+15550100163", "reason": "voicemail", "at": "2026-10-22T08:55:00Z", "call_id": "c_91e04a6d" } ], "next_cursor": null } ``` ### search_contacts Contacts of your directory found by name, number or company. Access: read. REST: `GET /api/v1/ringover/contacts/search`. MCP: `ringover_read → search_contacts`. | Parameter | Type | Required | Description | |---|---|---|---| | `query` | string | yes | A name, a phone number or a company. | | `limit` | integer | no | How many contacts to return. | Searches the Ringover contact directory by name, phone number or company and returns each match with its numbers. An empty list means no contact matches, which is normal for a first-time caller. Use the number as to_number in send_sms. Example response: ```json { "contacts": [ { "contact_id": "ct_5528", "name": "Dana Whitfield", "company": "Northline Dental", "numbers": [ "+15550100142" ] } ] } ``` ### list_sms_conversations SMS threads of your numbers, most recent first, with the last message and unread count. Access: read. REST: `GET /api/v1/ringover/sms-conversations`. MCP: `ringover_read → list_sms_conversations`. | Parameter | Type | Required | Description | |---|---|---|---| | `unread_only` | boolean | no | Only threads with unread messages. Default: false. | | `your_number` | string | no | Only threads of this mobile number of yours. | | `limit` | integer | no | How many threads per page. | | `cursor` | string | no | Next page cursor from the previous call. | Lists the threads of the SMS inbox for the mobile numbers your user can use, most recent first. Each thread shows the other number, the contact when known, the last message with its direction and the unread count the app shows as a red badge. conversation_id goes into get_sms_conversation. Needs the Business plan, as SMS does in the app. Example response: ```json { "conversations": [ { "conversation_id": "sms_3301", "number": "+15550100142", "contact": "Dana Whitfield", "your_number": "+15550100100", "last_message": { "direction": "incoming", "text": "Thursday at 10 works.", "at": "2026-10-22T11:02:00Z" }, "unread": 1 } ], "next_cursor": null } ``` ### get_sms_conversation The messages of one SMS thread in order, with direction and time. Access: read. REST: `GET /api/v1/ringover/conversations/{conversation_id}/sms-conversation`. MCP: `ringover_read → get_sms_conversation`. | Parameter | Type | Required | Description | |---|---|---|---| | `conversation_id` | string | yes | Thread ID from list_sms_conversations. | Returns the messages of one thread, oldest first, each with its direction, text and time. Reading a thread does not send anything. Attachments are named but not returned. Example response: ```json { "conversation_id": "sms_3301", "number": "+15550100142", "contact": "Dana Whitfield", "messages": [ { "direction": "outgoing", "text": "Hi Dana, does Thursday at 10 work for the demo?", "at": "2026-10-22T10:40:00Z" }, { "direction": "incoming", "text": "Thursday at 10 works.", "at": "2026-10-22T11:02:00Z" } ] } ``` ### list_call_tags The call tags your team created, with their groups. Access: read. REST: `GET /api/v1/ringover/call-tags`. MCP: `ringover_read → list_call_tags`. No parameters. Returns the tags available for calls, with the group each belongs to. Tags are created in the Ringover dashboard; this tool cannot create them. Call it before add_call_tag to use the exact spelling. If tagging is not activated in the Marketplace, the list is empty. Example response: ```json { "tags": [ { "name": "Demo booked", "group": "Outcome" }, { "name": "Price question", "group": "Outcome" }, { "name": "Support", "group": "Outcome" } ] } ``` ### add_call_tag Adds one of your call tags to a call. Access: write. REST: `POST /api/v1/ringover/calls/{call_id}/tag`. MCP: `ringover_write → add_call_tag`. | Parameter | Type | Required | Description | |---|---|---|---| | `call_id` | string | yes | Call ID from list_calls. | | `tag` | string | yes | Tag name from list_call_tags. | Adds the tag to the call, as when you pick Add a tag in the call logs. The tag must exist in list_call_tags, and your Ringover user needs the Tag calls permission; without it the call fails and the agent reports that. It returns the tags the call has now. The tag reaches no one and remove_call_tag undoes it in one call, so it does not wait for your OK. Example response: ```json { "call_id": "c_91e04a77", "tags": [ "Demo booked" ] } ``` ### remove_call_tag Removes one tag from a call. Access: write. REST: `DELETE /api/v1/ringover/calls/{call_id}/tag`. MCP: `ringover_write → remove_call_tag`. | Parameter | Type | Required | Description | |---|---|---|---| | `call_id` | string | yes | Call ID from list_calls. | | `tag` | string | yes | Tag name to remove. | Removes the tag from the call and returns the tags left on it. It undoes add_call_tag and reaches no one, so it does not wait for your OK. A tag the call does not have changes nothing. Example response: ```json { "call_id": "c_91e04a77", "tags": [] } ``` ### send_sms Sends a text message from one of your mobile numbers to a phone number. Access: write, asks the user first. REST: `POST /api/v1/ringover/froms/{from_number}/sms`. MCP: `ringover_write → send_sms`. | Parameter | Type | Required | Description | |---|---|---|---| | `from_number` | string | yes | A mobile number assigned to your user, the sender ID, with country code. | | `to_number` | string | yes | The recipient phone number with country code. | | `body` | string | yes | The message text. | | `send_at` | datetime | no | ISO 8601 time to send later. Omit to send now. | Sends the SMS as the Message > SMS > + New form does: from a mobile number assigned to your user, to a phone number, with your text. Ringover splits the text into 160-character fragments, bills each fragment and allows at most 8 segments. Needs a Business plan. With send_at the message is scheduled instead of sent now. It returns the message with its state; a failed message can be sent again. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "message_id": "msg_7710", "conversation_id": "sms_3301", "from_number": "+15550100100", "to_number": "+15550100142", "body": "Hi Dana, sorry we missed your call. We will call you back today.", "state": "sent", "sent_at": "2026-10-22T09:40:00Z" } ``` ## How do I connect Ringover to Claude Code, Codex or Cursor? Connecting Ringover takes three steps: sign up, sign in to Ringover 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 Ringover to your agent. 1. **Create an account** Sign up and add Ringover in the console. Your API key is there too. 2. **Sign in to Ringover in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Ringover 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 Ringover 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. ``` Go through yesterday's answered Ringover calls longer than a minute. Read each transcript and tag it with one of my call tags: Demo booked, Price question, Support, or No fit. Leave a call untagged if none fits. ``` ### Call Ringover 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/ringover 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/ringover/froms/%2B15550100100/sms \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"to_number":"+15550100142","body":"Hi Dana, sorry we missed your call. We will call you back today."}' ``` 3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing. ``` { "message_id": "msg_7710", "conversation_id": "sms_3301", "from_number": "+15550100100", "to_number": "+15550100142", "body": "Hi Dana, sorry we missed your call. We will call you back today.", "state": "sent", "sent_at": "2026-10-22T09:40:00Z" } ``` ## Why use Cotlet for Ringover? **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 Ringover 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 Ringover changes, the tool pauses until we fix it. - Failed calls cost nothing. ## Is it safe to connect Ringover to Cotlet? Yes. You sign in to Ringover yourself, in your own Cloud Browser, and we never save your password. Your agents only get Ringover 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 Ringover integration?** No, Cotlet is independent of Ringover. Ringover's own API is too limited for this work. Cotlet works through your own Ringover account, the way you use Ringover 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 Ringover in your console: your agents lose access at once and you stay signed in. Signing out of Ringover in the browser works too, and Reset browser deletes the whole profile. ## Is there a Ringover MCP server on GitHub? Yes. Community Ringover MCP servers exist on GitHub, usually maintained by one person. You install one on your own computer, add your API key, and keep it running yourself; when Ringover changes its API, it stops working until you or the maintainer fix it. 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 API key, add it to each MCP client | Sign up, sign in to Ringover once, add one MCP server or API key | | When Ringover 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 Ringover session | An API key in a file on your computer, readable by any program you run | In your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click | | When the session expires | Tools fail until you replace the key by hand | Your Cloud Browser keeps you signed in; if Ringover 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 Ringover 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 Ringover API cost? Free 7-day trial with 2,000 credits, no card needed. After that, the Ringover 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 Ringover 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 Ringover 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 Ringover only after you enable it. When Ringover 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 Ringover, sign out of Ringover 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. - **Ringover's terms:** You use your own Ringover account and stay responsible for following Ringover's terms. Cotlet is independent and not affiliated with Ringover. [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 Ringover in the console and press Request access. Then you create your API key and connect Ringover there. **Do I need to be technical?** No. You sign in to Ringover 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 Ringover to Cotlet?** Yes. You sign in to Ringover yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Ringover 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 Ringover 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 Ringover 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 Ringover's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Ringover 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 Ringover 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?** Ringover 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). **Which Ringover plan does my agent need to send SMS?** SMS needs an active Business plan and a mobile number assigned to your user, and it is not available for temporary test accounts. Another help article names the Business or Advanced plan. Reading calls and transcripts needs call recording on for the user, and transcripts need transcription enabled for the team. **Is it safe to give an agent my call data?** Call recordings and transcripts hold personal data, so use a Ringover user whose rights match the job. The agent sees what that user sees in Ringover, and you can disable the app for agents in one click. Tell callers about recording as your own rules and local law require. **Can my agent post or send messages in Ringover without asking me?** No. Every call to send_sms waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. add_call_tag and remove_call_tag run without asking, because they send nothing to anyone and one call undoes it. **Can I use the Ringover 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/ringover 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.