How to Connect Ringostat to Microsoft Copilot via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Ringostat, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

Ringostat + Microsoft Copilot

Ringostat call tracking and virtual PBX: the call log with traffic sources, talk time, status, employees and recording links, who is online or in a call, employees with departments, the daily SIP online report and Smart Phone statuses. Starting a callback is installed switched off.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

RINGOSTAT_AUTH_KEY, RINGOSTAT_PROJECT_ID

Step 1 — Get credentials

Setting up takes about 2 minutes and needs a project administrator in Ringostat.

1. In Ringostat open Settings, Integrations, Ringostat API and copy the Auth-key into RINGOSTAT_AUTH_KEY. It belongs to one project and is sent as the Auth-key header.
2. Set RINGOSTAT_PROJECT_ID to the number of that project: the value after project_id= or projectId= in the address bar of the Ringostat web app, e.g. 39071. Only the employee, SIP report and custom status tools use it.
3. Install the connector; the check runs ringostat_list_online_sip.

What it reads: the call log of a period, one row per call with the columns you ask for: date, caller and called number, call type, status (disposition), talk time, total duration and waiting time, employee name and department, number pool and forwarding scheme, target and repeated flags, UTM source, medium, campaign, content and term, landing page and referrer, the reason a call was missed, CSAT rating, call id and recording link; the SIP accounts online right now and those in a call right now; the employees with SIP status, full name, e-mail, extension, staffId, departments and call directions (main and backup SIP accounts or phone numbers); online and offline time per employee and day; and the custom Smart Phone statuses such as Lunch or Meeting.

Call log: ringostat_list_calls takes from and to as YYYY-MM-DD HH:MM:SS; without them it returns the last 24 hours. The answer is one array with every call of the period, not paginated, so on busy projects the AI keeps periods short (a day or a week) and asks only for the fields it needs. Talk time is billsec in seconds; call_type is in, out, callback, transitin or transitout; proper_flag and repeated_flag mark target and repeated calls. For statistics per employee the AI groups the rows by employee_fio and sums billsec.

Filters and sorting: filters are Ringostat expressions joined by commas, e.g. call_type=in,billsec>=30, with =, <>, >, <, >=, <= or ~ (a regular expression, base64-encoded). order sorts, e.g. calldate desc; merge groups calls by caller number per day (1) or over the whole period (2).

Personal data: phone numbers and recording links are personal data. Recording links in recording and recording_wav stay available for one year.

Switched off at install: ringostat_start_callback starts a real call that connects a project number with a phone number or an employee's SIP login. It dials at once and costs call minutes, so an administrator turns it on deliberately. Even then the AI shows you both numbers and waits for your yes. Numbers are in international format without +.

Read-only POST calls: the employee list, the SIP report and the custom statuses are POST requests in Ringostat's API, but they only read.

Common errors: 401 or 403 mean a missing or wrong Auth-key, or a key and a project id from different projects. A JSON-RPC error from the employee, report or status tools usually means a wrong RINGOSTAT_PROJECT_ID; "User does not exist" means the employee filter matched nobody.

The connector does not change PBX settings, employees, number pools or forwarding schemes, and it returns recording links rather than the audio itself.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Microsoft Copilot

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.

1. In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
2. Enter a Server name (for example AnythingMCP), a Server description that says what the connector does, and the Server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server.
3. Under authentication, choose API key, set Type to Header and the header name to X-API-Key, then select Create.
4. In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
5. Try it in the agent's Test pane: ask for something that needs the Ringostat tools.
6. Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.

Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.

Available tools

Example prompts

• "How many incoming calls did we get yesterday, how many were missed, and what was the average talk time?"
• "Group last week's calls by employee with the number of calls and the total talk time."
• "Which UTM sources and campaigns brought target calls this month?"
• "Who is online right now, and which of them are on a call?"
• "How long was each employee online per day last week?"

FAQ

Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.

What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.

The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT
• Connect to Cursor
• Connect to Gemini
• Connect to Meta Muse