Summary
Give your AI SISTRIX SEO data: the Visibility Index (Sichtbarkeitsindex) and its history, ranking keywords, competitors, top URLs, keyword rankings, metrics and questions, and backlinks, with the credit cost of every call.
Guided setup
Connect SISTRIX to Microsoft Copilot in 2 minutes
Start a free trial on AnythingMCP Cloud, connect SISTRIX in the guided setup, then add your MCP URL to Microsoft Copilot. No code and no server to run.
No credit card · 7-day trial · Self-host alternative available
Try asking
Example prompts for SISTRIX
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 → SISTRIX, paste your credentials, mint an MCP API key and you're done. No Docker, no
git clone, no local server.
SISTRIX + Microsoft Copilot
Give your AI SISTRIX SEO data: the Visibility Index (Sichtbarkeitsindex) and its history, ranking keywords, competitors, top URLs, keyword rankings, metrics and questions, and backlinks, with the credit cost of every call.
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:
SISTRIX_API_KEY
Step 1 — Get credentials
- API access and weekly API credits come with SISTRIX plans from Plus upwards.
- In the SISTRIX Toolbox, open Account → API access (
https://app.sistrix.com/account/api) and create or copy an API key. - Paste it into
SISTRIX_API_KEYand install the connector. The key is stored encrypted, added to each request by the connector and sent only to api.sistrix.com. - Start with
sistrix_get_credits: it is free and shows how many credits are left this week.
Paid from your own SISTRIX credits: every call spends API credits from your account's weekly allowance. Most functions cost 1 credit per row returned (per keyword, URL, competitor, link or value); sistrix_domain_overview costs 5 credits, sistrix_keyword_metrics 5 per keyword and sistrix_links_overview 25. SISTRIX itself returns 100 rows when no limit is sent (10,000 links for backlinks), so every list tool here starts at 10 rows, and sistrix_backlinks costs at most 250 credits per request. A full Visibility Index history can run to hundreds of values, so the AI sets a limit. sistrix_get_credits and sistrix_list_countries are free, and every answer ends with the credits it used.
What it does: the SISTRIX Visibility Index (Sichtbarkeitsindex) now, for a past week, as weekly history or as daily values for the last 30 days; the number of ranking keywords and how they spread over Google's first ten result pages; SEO competitors with their similarity; ranking keywords with position and URL; the best-ranking URLs and the paths with the most estimated clicks; keyword opportunities just beyond page one; who ranks for a keyword, and a site's ranking history for it; keyword metrics, search traffic and question queries; and backlinks, link totals and anchor texts. Every tool only reads.
What to analyse: the domain tools take a whole domain (with all subdomains), a host, a path or a single URL. country is a lower-case code (de, at, ch, uk, us, it, fr, es and more); without it SISTRIX uses the account's default country, usually de. A date asks for the weekly value of a past week.
Reading the answers: search traffic on keywords is SISTRIX's index from 0 to 100, not visits; competition also runs from 0 to 100.
Common errors: 100 (wrong api key) or 403 (permission denied): the key is wrong or the plan has no API access. 200 (not enough credits): the weekly credits are used up; sistrix_get_credits shows the balance. 1000, 2000 or 3000: SISTRIX has no data for this domain or keyword in this country. 1002 or 1003: a parameter is invalid or missing, for example no domain, host, path or URL. 429: more than 300 requests a minute.
The connector does not cover SISTRIX projects (Optimizer), the AI visibility functions, the Amazon marketplace functions, Google Ads (SEM) data or bulk keyword requests.
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 showsYOUR_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.
- In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
- Enter a Server name (for example
AnythingMCP), a Server description that says what the connector does, and the Server URLhttps://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server. - Under authentication, choose API key, set Type to Header and the header name to
X-API-Key, then select Create. - 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.
- Try it in the agent's Test pane: ask for something that needs the
SISTRIXtools. - 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
| Tool | What it does |
|---|---|
sistrix_get_credits | Show how many SISTRIX API credits this key has left this week |
sistrix_list_countries | List the country codes SISTRIX supports for Google (and Amazon marketplace) data |
sistrix_domain_overview | Latest key figures of a domain, host, path or URL: Visibility Index (Sichtbarkeitsindex), number of SEO keywords and of Google Ads… |
sistrix_visibility_index | SISTRIX Visibility Index (Sichtbarkeitsindex) of a domain, host, path or URL: the current value, the value of a past week (date), or the… |
sistrix_keyword_count | Number of keywords a domain, host, path or URL ranks for in Google's top 100, now, on a past date, or as weekly history |
sistrix_ranking_distribution | How many keywords of a domain rank on each of Google's first ten result pages (page01 = positions 1 to 10, page02 = 11 to 20...), now, for… |
sistrix_competitors | SEO competitors of a domain, host, path or URL with their similarity (match, in %); the analysed domain itself appears with 100 |
sistrix_ranking_keywords | Keywords a domain, host, path or URL ranks for in Google: keyword, position, competition, search traffic (0 to 100) and ranking URL |
sistrix_top_urls | The best-ranking URLs of a domain, host or path with their top-10 and top-100 keyword counts and their share of the domain's Visibility… |
sistrix_traffic_estimation | Paths of a domain with the most estimated organic clicks: estimated clicks, share of clicks (%) and number of top-100 keywords per path |
sistrix_keyword_opportunities | Keywords a domain ranks for beyond page one that could reach page one with little effort: gain (0 to 100), current position, ranking URL… |
sistrix_keyword_serp | The organic Google ranking for a keyword: position, domain and URL of each result, now or for a past week |
sistrix_keyword_metrics | Main metrics of a keyword: competition, CPC, search traffic (0 to 100), clicks and the mobile and desktop share |
sistrix_keyword_traffic | Search traffic (0 to 100) and clicks of a keyword in one country, all countries (show_all_countries) or as history (show_all) |
sistrix_keyword_questions | Google queries that combine a keyword with question words (what, how, why...), with search volume |
sistrix_links_overview | Backlink overview of a domain, host or path: total backlinks and the number of linking hosts, domains, networks and class C IP ranges |
sistrix_backlinks | Backlinks of a domain: source URL (url.from), link text and target URL (url.to) |
sistrix_link_texts | Most-used anchor texts of the backlinks of a domain, host or path, with the number of links and of linking hosts, domains, IPs and networks |
Example prompts
- "What is the SISTRIX Visibility Index of example.de today, and how did it develop week by week over the last six months?"
- "Who are the SEO competitors of example.de in Germany, and how does their Visibility Index compare to ours?"
- "Which keywords does example.de rank for beyond page one that could reach page one with little effort?"
- "Who ranks in the top 10 for 'wärmepumpe kaufen' in Germany, and which questions do people search around it?"
- "How many SISTRIX credits do we have left this 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
Was this guide helpful?