Copilot Studio agents can call tools on any MCP server. Add GSC Wizard as one and your agent answers from real Search Console, GA4 and Bing Webmaster numbers, in the test pane, in Microsoft Teams and in Microsoft 365 Copilot.
Endpoint: https://mcp.gscwizard.com/mcp
The short answer
Four steps, about five minutes:
Every person who uses the agent signs in with their own GSC Wizard account, so a shared agent never leaks one person’s properties to another.
Most Microsoft 365 organisations already live in Teams. An agent with GSC Wizard attached turns “can someone pull the Search Console numbers?” into a question anyone can ask.
Without a data source, an assistant estimates traffic or refuses. With GSC Wizard it reads your clicks, impressions, position and CTR, and says which dates it used.
Ranking changes, decay, cannibalization and opportunity scores are computed server-side on the full dataset, so the agent explains a finished result instead of doing arithmetic over raw rows.
Publish once to Teams and Microsoft 365 Copilot. Each colleague signs in as themselves and sees the properties they have access to in GSC Wizard.
You need a GSC Wizard account with an active subscription or trial and your Search Console properties connected, and a Copilot Studio license that lets you create agents. Keep GSC Wizard and Copilot Studio open in two tabs: you switch between them once.
Open Account → MCP API keys, scroll to Microsoft Copilot Studio, give the connection a name (your agent’s name works well, since it appears on the sign-in screen) and click Create connection. Copy the client secret straight away: it is shown once.
In Copilot Studio, open the agent, add a tool from the Tools section and choose Model Context Protocol. Fill in a name, a description, and the fields in the table below. Pick OAuth 2.0 and then Manual.
Copilot Studio now shows Save your redirect URL. Copy it, paste it into the connection in GSC Wizard and click Save. Only then click Next in Copilot Studio. Each Copilot Studio tool gets its own URL, and GSC Wizard only completes a sign-in to a URL saved on that connection.
Create the tool connection when Copilot Studio asks, sign in to GSC Wizard and approve the consent screen, which names Microsoft Copilot Studio as the destination. In the test pane, ask “Which Search Console properties can you see?” and approve the tool call if Copilot Studio asks for permission.
The values for step 2
| Copilot Studio field | Value |
|---|---|
| Server URL | https://mcp.gscwizard.com/mcp |
| Authentication | OAuth 2.0 |
| Configuration type | Manual |
| Client ID | From your GSC Wizard connection (starts with gscwc_) |
| Client secret | From your GSC Wizard connection (starts with gscws_) |
| Authorization URL | https://tool.gscwizard.com/oauth/authorize |
| Token URL | https://tool.gscwizard.com/api/oauth/token |
| Refresh token URL | https://tool.gscwizard.com/api/oauth/token |
| Scopes | mcp:read mcp:write, or mcp:read for a read-only agent |
You do not have to type any of this: the connection in GSC Wizard shows every value with a copy button. Note that the authorization URL has no /api/ in it and the token URL does; both are correct.
Why Manual and not Dynamic? The Dynamic options ask Copilot Studio to register itself with the server automatically, and that step currently fails inside Copilot Studio before the request ever reaches GSC Wizard. Manual configuration, with a client you create yourself, is the route we test against.
The tool gives the agent your numbers. The agent’s Instructions decide how carefully it reads them. Two things matter most: the tool description, which the agent uses to decide when to call GSC Wizard, and instructions that name the ways assistants usually get SEO data wrong.
Tool description
Google Search Console, GA4 and Bing Webmaster data for our websites:
clicks, impressions, average position, CTR, rankings, indexing,
content decay, cannibalization and full SEO reports.Agent instructions worth pasting in
You are our SEO analyst. Use the GSC Wizard tools as the authoritative
source for search performance.
1. If the website is unclear, call list_sites first and ask which one.
2. Prefer the specialised analysis tools (ranking changes, decay,
cannibalization, opportunities) over pulling large raw datasets.
3. Always state the analysis period and the comparison period.
4. Separate measured facts, interpretation and recommendations.
5. Do not claim causation when the data only shows correlation.
6. Treat a lower average position as better.
7. Rank findings by likely impact on clicks, not by position movement.
8. Never call a tool that changes data unless the user asks for it.Most of these exist because assistants misread SEO data in predictable ways: averaging an average position, reading a lower position as worse, calling a seasonal dip a ranking loss, or quietly truncating a dataset and reporting the total anyway. Naming the failure modes up front is what turns a chat answer into something you can forward to a stakeholder.
The MCP tool belongs to the agent, not to a chat. Publish the agent to the Teams and Microsoft 365 channel and the same GSC Wizard tools answer questions in Teams chats and in Microsoft 365 Copilot.
With user authentication, everyone who chats with the agent signs in to GSC Wizard with their own account and sees only their own properties. One connection in GSC Wizard serves the whole team. If you set the tool to use the maker’s connection instead, everyone sees your data, so keep that for internal agents where it is intended.
Enter only mcp:read as the scope and the server refuses every write tool, such as IndexNow submissions or annotation changes, whatever the agent is asked. Deleting the connection in GSC Wizard cuts off everyone who signed in through it at once.
Want the numbers to come to you instead? The GSC Wizard Teams alerts post cards for indexing problems, Core Web Vitals, traffic drops and algorithm updates into a channel without anyone asking. The agent and the alerts work well side by side: alerts tell you something changed, the agent helps you dig into why.
“Invalid or unregistered redirect_uri” means the redirect URL from Copilot Studio is not saved on the connection in GSC Wizard yet, or the tool was recreated and got a new one. An “HTTP 400” from the MCP server in our testing came from the Dynamic configuration types: remove the tool and add it again with Manual. “You don’t have permission to create agents” is a Microsoft licensing message about your Copilot Studio license, not a GSC Wizard error. The full troubleshooting list is in the docs.
The agent picks from over a hundred GSC Wizard tools. Naming the analysis you want helps it pick the right one.
The same GSC Wizard account works in every assistant. See the guides for ChatGPT, Claude, Gemini and Grok, or connect any MCP client. The GSC MCP overview lists every tool, and the same connector also reads Yandex Webmaster and Merchant Center.
Yes, through an MCP tool. Copilot Studio agents can call any Model Context Protocol server, and GSC Wizard is a hosted MCP server at https://mcp.gscwizard.com/mcp that exposes Search Console, GA4 and Bing Webmaster data. Add it to an agent with OAuth 2.0 and the Manual configuration type.
The Dynamic options rely on Copilot Studio registering itself with the server automatically, and that step currently fails inside Copilot Studio before the request reaches GSC Wizard. Manual configuration uses a client ID and secret you create yourself in GSC Wizard and works reliably.
In GSC Wizard under Account, MCP API keys, in the Microsoft Copilot Studio section. Each connection gets its own client ID and secret. The secret is shown once at creation and stored only as a hash; if you lose it, delete the connection and create a new one.
Yes. With user authentication, everyone who chats with the agent signs in to GSC Wizard with their own account and sees only the properties that account can read. One connection serves all of them. If the tool is set to use the maker's connection instead, everyone sees the maker's data.
Yes. Enter only mcp:read in the Scopes field. The server then refuses every write tool, such as IndexNow submissions or annotation changes, whatever the agent is asked to do.
Yes. The MCP tool belongs to the agent, so once you publish the agent to the Teams and Microsoft 365 channel, people can ask it about Search Console performance from Teams chats and Microsoft 365 Copilot.
A GSC Wizard account with an active subscription or trial and your Search Console properties connected, plus a Copilot Studio license that lets you create agents in your Microsoft environment.
Connect your Search Console properties, create a Copilot Studio connection, and ask about your site from Teams.
Practical GSC and GA4 workflows, product updates and SEO experiments. No spam, unsubscribe anytime.