How to Connect SISTRIX (MCP server) to Microsoft Copilot via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, open Connectors → SISTRIX (MCP server), install it, click Authorize with Provider and approve in SISTRIX, then mint an MCP API key. No Docker, no git clone, no local server.

SISTRIX (MCP server) + Microsoft Copilot

Connect Claude, ChatGPT or Copilot to SISTRIX through SISTRIX's official MCP server: Visibility Index and history, ranking keywords and URLs, competitors, keyword data and SERPs, backlinks, AI visibility in ChatGPT and AI Overviews, and your Optimizer projects. Sign in with your SISTRIX login; no API key and no API credits.

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:

(none: you sign in with SISTRIX after installing)

Step 1 — Sign in with SISTRIX

Setting up takes about 2 minutes. You need a SISTRIX account; any package works, and no API key is needed.

SISTRIX runs its own official remote MCP server at https://api.sistrix.com/mcp. This connector bridges it: the tools are SISTRIX's, and AnythingMCP puts them behind your MCP endpoint with OAuth for Claude and ChatGPT, per-tool roles and the audit log.

1. Install the connector. There is nothing to paste: no API key, client ID or secret.
2. On the connector page click Authorize with Provider. AnythingMCP registers itself with SISTRIX and sends you to the SISTRIX Toolbox login. There is no redirect URI to set up.
3. Sign in with your SISTRIX login and approve access. Back in AnythingMCP the tool list is reloaded from SISTRIX's server.
4. To check it works, run sistrix_mcp_domain with view visindex and country de for your own domain: it returns the current Visibility Index.

Which SISTRIX connector? This one signs in with your SISTRIX login and spends no API credits: SISTRIX opened its MCP server to every package, and requests count against a generous daily fair-use quota. The SISTRIX connector uses the classic REST API with an API key (Plus plan and higher) and spends API credits on every call. For SEO analysis in chat, take this one; the REST connector is the choice when you want to work with your API key and credits, for example when the daily MCP quota is not enough.

Whose account it is: the person who signs in is the SISTRIX user for everyone who uses this connector, and the Optimizer projects and AI trackers are that account's.

What it reads: the Visibility Index of any domain, host, directory or URL, now, at a date or as weekly or daily history, with the all-time high and low, plus ranking keywords and URLs, ranking distribution, top URLs by estimated clicks, competitors, ideas and opportunities (sistrix_mcp_domain); every keyword a domain ranks for, with position and URL, filtered by position range, SERP feature or regular expression, for striking-distance and content gap work (sistrix_mcp_keyword_domain_seo); keyword data such as the results page, search volume, CPC, competition, search intent and SERP features (sistrix_mcp_keyword); backlinks, anchor texts and the most linked URLs (sistrix_mcp_links); and your Optimizer projects with tracked rankings, project Visibility Index, competitors and the onpage crawl (sistrix_mcp_project, sistrix_mcp_project_onpage).

AI visibility: sistrix_mcp_ai_check shows how brands and domains appear in answers from ChatGPT, Gemini, AI Overviews, AI Mode, Perplexity and others without a configured tracker: competitors, prompts with the answer text, daily history and the cited sources. sistrix_mcp_ai_tracker_overview and sistrix_mcp_ai_tracker read the prompt trackers set up in your account, sistrix_mcp_ai_prompt_answers returns the answers AI models gave to one prompt, and sistrix_mcp_ai_topicresearch finds the topics and prompts people ask AI assistants around a keyword, for content and GEO planning.

Reading the data: country is a lowercase code (de, at, ch, us, fr...), and SISTRIX uses uk for the United Kingdom. An unsupported code is not rejected but returns other data, so the AI checks it. Visibility Index history is weekly by default; daily values are a rotating sample, so the AI judges a Google update on the weekly values. Search intent comes as four independent scores from 0 to 100, not as shares that add up to 100. Project and tracker hashes are opaque, so the AI lists them first (sistrix_mcp_project with view overview, sistrix_mcp_ai_tracker_overview).

The tools come from SISTRIX: SISTRIX groups its data into a few tools that each take a view parameter, and adds datasets as new views. After SISTRIX announces new data, open the connector and click Discover tools.

Asks before every change: there is nothing to confirm. Every tool reads, and nothing in your SISTRIX account is changed.

Switched off at install: nothing. All 11 tools only read, so they are all on.

Limits: requests count against SISTRIX's daily fair-use MCP quota, not against API credits. When it is used up, the quota resets the next day.

Common errors: error 7010 means the daily MCP quota is used up; it resets the next day. Error 1000 means SISTRIX has no data for that query. When calls fail with an authorization error after it worked, click Authorize with Provider again.

Passing data on: SISTRIX's terms do not allow passing its data on to third parties without permission.

The connector does not change anything in SISTRIX, does not spend API credits, and does not create Optimizer projects or AI trackers: set those up in the SISTRIX Toolbox.

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 SISTRIX (MCP server) 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.com developed in Germany over the last 12 months, and in which weeks did it drop?"
• "Show me our striking-distance keywords: everything example.com ranks for in positions 11 to 20 in the US."
• "Who are our strongest SEO competitors for example.com, and which keywords do they rank for that we do not?"
• "How often does our brand appear in ChatGPT and AI Overviews answers compared with our competitors, and which sources are cited?"
• "Which onpage issues does the crawl of our Optimizer project show, and which ones affect the most URLs?"

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