Skip the install. Get this working in under 2 minutes.
Start a free trial on cloud.anythingmcp.com, add the XOVI in one click, then point your AI client (Claude, ChatGPT, Copilot or Cursor) at the generated MCP endpoint. No Docker, no git clone, zero engineering experience required.
Summary
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.
Try asking
Example prompts for XOVI
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 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
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.
Setup
Setting up takes about 2 minutes. The XOVI API needs a XOVI Pro, Business or Enterprise account.
- In the XOVI Suite open Account > API Dashboard and create your personal API key.
- Paste it into
XOVI_API_KEY. The connector sends it as thekeyparameter on every call tohttps://suite.xovi.net/api. - 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.
Asks before every change: XOVI_API_KEY
Install the connector locally
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
Open http://localhost:3000/connectors/store, pick XOVI and paste in the env vars listed under Prerequisites.
Available tools
| Tool | What it does |
|---|---|
xovi_get_credit_state | Get the API credit balance: credits per interval, additionally booked credits, credits used and left, and the last refill date |
xovi_get_limits | Get the usage limits of the XOVI account per tool area (name and value), e.g |
xovi_list_search_engines | List the search engines XOVI crawls: id, host (e.g. google.de), country and city |
xovi_get_ovi_trend | Get the weekly visibility index (OVI) history of a domain, subdomain, directory or URL in one search engine: date and staticOvi per week |
xovi_list_ranking_keywords | List the keywords a domain or URL ranks for in one search engine in a weekly crawl: keyword, best ranking URL, position, change to the… |
xovi_get_ranking_value | Get the ranking value of a domain or directory: its traffic value computed from positions, search volume, CPC and click share, for one week |
xovi_get_ranking_trend | Get the weekly history of a domain: number of ranking keywords, rankings and keywords on page one per date |
xovi_get_keyword_trend | Get the weekly ranking history of one keyword for a domain: date, position and ranking URL |
xovi_get_keyword_serp | Get the ranking URLs and positions for one keyword in a search engine (the search result page of the weekly crawl) |
xovi_list_projects | List the XOVI projects: hash (projhash for the monitoring OVI), name, main domain and competitors |
xovi_list_labels | List the labels with hash, name and categories; a hash is the labelid of the monitoring tools |
xovi_list_monitoring_domains | List the domains in the daily keyword monitoring, optionally for one search engine |
xovi_list_monitoring_keywords | List the keywords in the daily monitoring with their latest position, change to the previous day, ranking URL, universal search type… |
xovi_get_monitoring_keyword_trend | Get the daily ranking history of a monitored keyword for a domain: crawl date and time, position, change, URL and universal search type |
xovi_get_monitoring_serp | Get the top 100 search results of a monitored keyword on a day: domain, URL, page, position and universal search type |
xovi_get_monitoring_ovi_trend | Get the daily monitoring OVI history of a project domain, optionally per device, search engine, label or competitor |
xovi_get_monitoring_keyword_limits | Get how many monitoring keyword credits the account has in total and how many are used |
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?"
Next steps
Was this guide helpful?