Connect your AI to Ringover

What your AI can do with Ringover

Once connected, these tools appear automatically in your AI assistant:

• list_callsread-only

  List recent calls (paginated). Optionally filter by date range.

• get_callread-only

  Get a single call by its id, with its details.

• list_contactsread-only

  List contacts, optionally filtered by a search term.

• list_numbersread-only

  List the phone numbers of the Ringover account.

• send_smswrite · needs approval

  Send an SMS from one of the account's numbers. Writes to the real world, so it goes through the confirmation guardrail when enabled.

• list_transcriptionsread-only

  List call transcriptions, or search their content. Given a `search` term, Ringover runs a semantic search over what was actually said and returns the closest matches — the way to answer 'which calls mentioned the renewal?'. In search mode the date and duration filters are ignored. Use get_transcription for the full text of one known call.

• get_transcriptionread-only

  Get the full transcription of one call, as `transcription_data.speeches`. In each speech, `channelId` is 1 for the person who placed the call and 0 for the person who received it. Takes the call id from list_calls, not an Empower UUID.

• list_analyzed_callsread-only

  List the calls analysed by Empower, Ringover's AI layer, and get their `call_uuid` — the identifier the other Empower tools need. Filter by call date, direction or source. Ringover refuses a date range wider than 15 days.

• get_call_analysisread-only

  Get everything Empower knows about one analysed call: transcription, scores and metadata. Takes the `call_uuid` from list_analyzed_calls.

• get_call_summaryread-only

  Get Empower's AI summary of a call, with its key topics, action items and sentiment. Read `recap.summary` — the top-level `summary` field is a retired pipeline and is always null. Takes the `call_uuid` from list_analyzed_calls.

• get_call_momentsread-only

  Get the key moments Empower detected during a call — objections, commitments, questions — each with where it occurred. Takes the `call_uuid` from list_analyzed_calls.

• list_conversationsread-only

  List SMS and chat conversations. Without monitoring enabled on the API key, only the conversations of the key's own user are returned.

• list_conversation_messagesread-only

  Read the messages of one conversation — including the replies to an SMS sent with send_sms. Pages with `lastIdReturned` rather than an offset, so no message is seen twice.

• list_tagsread-only

  List the call tags defined for the team, with their names and colours. Tags are shared by every user of the team.

• list_usersread-only

  List the team's Ringover users, to attribute a call to the person who took it. Without monitoring enabled on the API key, only the key's own user is returned.

• get_contactread-only

  Get one contact: names, company, numbers and whether it is shared with the team.

• create_contactswrite · needs approval

  Create contacts, up to fifty in one call. Each is filed under the user the API key belongs to. Note that this route does double duty at Ringover: the same POST with a filter body reads contacts instead, which is what list_contacts uses.

• update_contactwrite · needs approval

  Replace a contact's details. This is a full replacement: the numbers you send become the contact's numbers, so send back the ones that should survive.

• set_contact_companywrite · needs approval

  Change only a contact's company, leaving everything else untouched. Ringover carries the new value in the path, so it must be a single path segment.

• set_contact_firstnamewrite · needs approval

  Change only a contact's first name, leaving everything else untouched. Ringover carries the new value in the path, so it must be a single path segment.

• set_contact_lastnamewrite · needs approval

  Change only a contact's last name, leaving everything else untouched. Ringover carries the new value in the path, so it must be a single path segment.

• add_contact_numberswrite · needs approval

  Add one or more phone numbers to a contact, keeping the ones already there.

• update_contact_numberwrite · needs approval

  Change one of a contact's numbers — the value itself, its type, or both.

• get_conversationread-only

  Get one conversation: its name, its kind, and when it was last active.

• list_conversation_membersread-only

  List who is in a conversation.

• rename_conversationwrite · needs approval

  Rename a conversation. Everyone in it sees the new name.

• get_userread-only

  Get one user: their name, numbers, profile and current status.

• get_user_planningread-only

  A user's weekly working hours, day by day. What decides whether a call reaches them or goes to the fallback.

• list_presencesread-only

  Who is available, busy, on a call or away, across the whole team, right now.

• get_user_presenceread-only

  One user's current availability.

• list_profilesread-only

  List the permission profiles of the account — what each class of user is allowed to do.

• get_profileread-only

  Get one permission profile and its rights.

• get_teamread-only

  The account itself: its name, its plan and its overall settings.

• get_numberread-only

  Get one phone number of the account: what it is called, where it routes, and whether it is active.

• list_ivrsread-only

  List the interactive voice menus of the account. An IVR is the tree a caller hears before reaching anyone, and it is where a routing problem usually lives.

• get_ivrread-only

  Get one voice menu with its numbers and its configuration.

• list_ivr_scenariosread-only

  List the scenarios of one voice menu. A scenario is one routing plan — office hours, holidays, out of hours — and only one is active at a time.

• get_ivr_scenarioread-only

  Get one scenario of a voice menu, with the steps a caller goes through.

• list_scenariosread-only

  List every scenario of the account, across all voice menus.

• get_scenarioread-only

  Get one scenario by id, whichever menu it belongs to.

• list_conferencesread-only

  List the conference rooms of the account, with their numbers and access codes.

• get_conferenceread-only

  Get one conference room.

• list_groupsread-only

  List the call groups — the rings that distribute an incoming call across several people.

• get_groupread-only

  Get one call group with its members and how the call is spread among them.

• list_team_tasksread-only

  List the team's tasks — the follow-ups attached to calls. Ringover reads these through a POST because the filter is too big for a URL; nothing is created or changed by this call.

• create_taskswrite · needs approval

  Create a batch of tasks from a list of numbers — one task per number, all sharing the same type, status and scheduled date.

• list_blacklisted_numbersread-only

  List the numbers blocked for the whole team, with the comment left on each.

• add_blacklisted_numberwrite · needs approval

  Block a number for the whole team. Nobody in the account will take or place a call to it in the direction you choose.

• get_blacklisted_numberread-only

  Check whether a number is on the team blacklist, and read the comment if it is.

• set_blacklist_commentwrite · needs approval

  Change the comment on a team-blocked number. Ringover carries the text in the path, so it must be a single path segment.

• list_user_blacklisted_numbersread-only

  List the numbers one user has blocked for themselves, which is separate from the team list.

• add_user_blacklisted_numberwrite · needs approval

  Block a number for one user only, leaving the rest of the team unaffected.

• get_user_blacklisted_numberread-only

  Check whether a number is on one user's personal blacklist.

• set_user_blacklist_commentwrite · needs approval

  Change the comment on a number one user has blocked.

• start_callbackwrite · needs approval

  Place a call. Ringover rings the chosen device first, then dials the destination and joins the two — so this really does make somebody's phone ring, twice over, and cannot be recalled.

• start_ivr_callbackwrite · needs approval

  Place a call through a voice menu, so the destination sees the menu's number and the call is logged against it. Same warning as start_callback: a phone actually rings.

• list_call_campaignsread-only

  List the outbound call campaigns of the account. A campaign is an automatic dialler: it walks a list of numbers and connects each answer to an available agent.

• list_my_call_campaignsread-only

  List the active campaigns assigned to the user the API key belongs to.

• get_call_campaignread-only

  Get one campaign: its state, its schedule, its retry policy and how far through its list it is.

• get_campaign_logsread-only

  The audit trail of a campaign — who started it, stopped it, changed it, and when.

• list_campaign_numbersread-only

  List the contacts in a campaign's queue, with their position, their attempt count and the custom columns carried alongside them.

• add_campaign_numberswrite · needs approval

  Add contacts to a campaign's queue. Once the campaign is running, these numbers will be dialled.

• update_campaign_numberswrite · needs approval

  Change the custom column values carried by contacts already in the queue.

• remove_campaign_numberswrite · needs approval

  Take contacts out of a campaign's queue so they are not called.

• list_campaign_usersread-only

  List the agents assigned to a campaign — the people its calls are handed to.

• assign_campaign_userswrite · needs approval

  Assign agents to a campaign.

• remove_campaign_userswrite · needs approval

  Take agents off a campaign.

• list_campaign_groupsread-only

  List the call groups assigned to a campaign.

• assign_campaign_groupswrite · needs approval

  Assign call groups to a campaign, which assigns everyone in them.

• remove_campaign_groupswrite · needs approval

  Take call groups off a campaign.

• add_campaign_columnwrite · needs approval

  Add a custom data column to a campaign's contacts — a field the agent sees on screen when the call connects.

• remove_campaign_columnwrite · needs approval

  Delete a custom data column and its values from every contact of the campaign.

• rename_campaign_columnwrite · needs approval

  Rename a custom data column, keeping its values.

• switch_campaign_columnswrite · needs approval

  Swap two custom columns, which changes the order the agent sees them in.

• set_campaign_max_retrywrite · needs approval

  Set how many times the dialler retries a number that did not answer.

• rename_call_campaignwrite · needs approval

  Rename a campaign.

• start_call_campaignwrite · needs approval

  Start a campaign. From that moment the dialler works through the queue and rings real people, one number after another, until it is stopped or the list runs out. Give `startDate` to have it begin later instead of now.

• edit_campaign_startwrite · needs approval

  Move the scheduled start of a campaign that has not begun yet.

• stop_call_campaignwrite · needs approval

  Stop a running campaign. Calls in progress finish; nothing new is dialled.

• reset_call_campaignwrite · needs approval

  Reset a campaign to its initial state: every contact goes back into the queue as if never attempted, and the attempt counters are cleared. The call history itself is not affected.

• set_campaign_scriptwrite · needs approval

  Attach a call script to a campaign, or detach the current one by leaving `scriptUuid` out.

• set_campaign_tagswrite · needs approval

  Replace a campaign's tags. THIS REPLACES THE WHOLE SET: the tags you send become the campaign's tags, so send back the ones that should stay.

• remove_campaign_tagswrite · needs approval

  Remove every tag from a campaign.

• remove_campaign_tagwrite · needs approval

  Remove one tag from a campaign, leaving the others.

Example prompts

Just ask your AI in plain language — it picks the right Ringover tool:

• “List recent calls (paginated). Optionally filter by date range — from Ringover, in plain language.”
• “Get a single call by its id, with its details — from Ringover, in plain language.”
• “List contacts, optionally filtered by a search term — from Ringover, in plain language.”
• “List the phone numbers of the Ringover account — from Ringover, in plain language.”

How it works

1. Create your Proxoria account and add your MCP endpoint to Claude or ChatGPT.
2. Connect Ringover with your API key — each user connects their own account, credentials encrypted at rest.
3. Your AI instantly gets the Ringover tools. Write actions wait for your approval in the dashboard before anything changes.

Frequently asked questions

Does Ringover have an official MCP server?

You don't need one. Proxoria exposes Ringover to your AI through the Model Context Protocol, so you can use it from Claude, ChatGPT, Mistral or any MCP-compatible client — no official Ringover MCP server required.

What can my AI do with Ringover through Proxoria?

It gets 84 tools: list_calls, get_call, list_contacts, list_numbers, send_sms, list_transcriptions, get_transcription, list_analyzed_calls, get_call_analysis, get_call_summary, get_call_moments, list_conversations, list_conversation_messages, list_tags, list_users, get_contact, create_contacts, update_contact, set_contact_company, set_contact_firstname, set_contact_lastname, add_contact_numbers, update_contact_number, get_conversation, list_conversation_members, rename_conversation, get_user, get_user_planning, list_presences, get_user_presence, list_profiles, get_profile, get_team, get_number, list_ivrs, get_ivr, list_ivr_scenarios, get_ivr_scenario, list_scenarios, get_scenario, list_conferences, get_conference, list_groups, get_group, list_team_tasks, create_tasks, list_blacklisted_numbers, add_blacklisted_number, get_blacklisted_number, set_blacklist_comment, list_user_blacklisted_numbers, add_user_blacklisted_number, get_user_blacklisted_number, set_user_blacklist_comment, start_callback, start_ivr_callback, list_call_campaigns, list_my_call_campaigns, get_call_campaign, get_campaign_logs, list_campaign_numbers, add_campaign_numbers, update_campaign_numbers, remove_campaign_numbers, list_campaign_users, assign_campaign_users, remove_campaign_users, list_campaign_groups, assign_campaign_groups, remove_campaign_groups, add_campaign_column, remove_campaign_column, rename_campaign_column, switch_campaign_columns, set_campaign_max_retry, rename_call_campaign, start_call_campaign, edit_campaign_start, stop_call_campaign, reset_call_campaign, set_campaign_script, set_campaign_tags, remove_campaign_tags, remove_campaign_tag. For example, list recent calls (paginated). optionally filter by date range.

Is the Ringover connector read-only?

No — it can also make changes. Write actions go through Proxoria's confirmation guardrail by default: your AI proposes them, and you approve each one from your dashboard before anything is written to Ringover.

How do I connect Ringover to my AI?

Create a Proxoria account, connect Ringover with your API key, and add your Proxoria MCP endpoint to Claude or ChatGPT. Your AI instantly gains the Ringover tools.