How to Connect XOVI to Microsoft Copilot via MCP

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

XOVI + Microsoft Copilot

XOVI Suite SEO data, read-only: API credit balance, visibility index (OVI) history, ranking keywords, ranking value and keyword history of any domain, and the daily keyword monitoring of your projects.

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:

XOVI_API_KEY

Step 1 — Get credentials

Setting up takes about 2 minutes. The XOVI API needs a XOVI Pro, Business or Enterprise account.

1. In the XOVI Suite open Account > API Dashboard and create your personal API key.
2. Paste it into XOVI_API_KEY. The connector sends it as the key parameter on every call to https://suite.xovi.net/api.
3. Install the connector and run xovi_get_credit_state, which costs no credits, to check the key.

What it reads: the API credit balance and the usage limits of your account; the weekly domain analysis of any domain: the visibility index (OVI) over time, the keywords a domain or URL ranks for with position, search volume, CPC and competition, its ranking value, the history of its rankings, the ranking history of one keyword and the search results page of a keyword; and the daily keyword monitoring of your projects: projects with their competitors, labels, monitored domains, monitored keywords with their latest position, the daily history of a keyword, the top 100 results of a monitored keyword on a day and the monitoring OVI of a project domain.

Credits: most calls are paid from your account's API credit budget, per call or per block of rows (see each function in the XOVI reference); calls that only read your own account data are free. Before large exports the AI checks the balance with xovi_get_credit_state and xovi_get_limits, keeps limit small, and does not loop over many domains without your go-ahead. Monitoring keyword slots are counted separately: xovi_get_monitoring_keyword_limits.

Weekly domain analysis: the AI picks the search engine host with xovi_list_search_engines (weekly, e.g. google.de), then uses xovi_get_ovi_trend for visibility over time, xovi_list_ranking_keywords for what a domain ranks for, xovi_get_ranking_value, xovi_get_ranking_trend, xovi_get_keyword_trend for one keyword and xovi_get_keyword_serp for the results page of a keyword. urlpattern takes a host (www.example.com), all subdomains (example.com/*) or a directory (www.example.com/blog/*). The data of a week is published on Sunday, and date is that Sunday.

Daily monitoring: xovi_list_projects gives the project hash, xovi_list_labels the labels and xovi_list_search_engines with interval daily the numeric sengineid; then the AI uses xovi_list_monitoring_domains, xovi_list_monitoring_keywords, xovi_get_monitoring_keyword_trend, xovi_get_monitoring_serp and xovi_get_monitoring_ovi_trend.

Read-only: all 17 tools only read. Nothing in your XOVI projects changes, so there is nothing to confirm and no tool is switched off at install.

Paging: limit is at most 1000 rows; skip counts pages of limit rows, so skip 1 with limit 100 returns rows 101 to 200. Results carry resultCount with the unfiltered total.

Common errors: XOVI answers HTTP 200 with apiErrorCode and apiErrorMessage, and the connector turns them into errors. param invalid on key means a wrong or deleted API key; no permission means the key or plan may not use that function; cost error means the credit budget is used up until the next refill; param missing or param invalid on another field names the field to fix. result empty is a successful call without data, for example a domain without rankings.

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 XOVI 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 has the visibility index of example.de developed on google.de over the last 12 months?"
• "Which keywords does www.example.de/blog/ rank for on page one, with search volume and CPC?"*
• "Compare the ranking value of example.de and competitor.de for the latest week."
• "Which monitored keywords of our project lost more than 3 positions since yesterday?"
• "How many API credits do we have left, and when was the last refill?"

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