Skip to main content
Copilot Studio can call the Share Of Model MCP server as a set of tools. You build an agent once, connect it to the MCP server, and publish it to Microsoft Teams and Microsoft 365 Copilot — so anyone in your organisation can ask about their AI visibility without leaving the tools they already use. You do this yourself, in your own Microsoft tenant. Share Of Model provides the MCP server; nothing has to be deployed on our side.
Each person who talks to the agent signs in with their own Share Of Model account. They see exactly the workspaces and analyses their Share Of Model role allows — publishing the agent broadly does not widen anyone’s data access.

​
Prerequisites

  • A Microsoft Copilot Studio licence and permission to create agents in a Power Platform environment.
  • A Share Of Model account for every person who will use the agent. See User Roles & Workspaces.
  • Your Power Platform admin allows custom connectors. MCP access in Copilot Studio runs through Power Platform connectors, so a data loss prevention policy that blocks custom connectors also blocks the MCP server.
  • A Microsoft 365 admin who can approve the agent, if you want it listed for the whole organisation.

​
Step 1 — Create the agent

1

Open Copilot Studio

Go to copilotstudio.microsoft.com and check the environment selector in the top-right corner. The agent is created in the selected environment — pick the one your organisation uses for production agents.
2

Start a new agent

Select Create, then New agent. Skip the description-based setup by selecting Configure, and fill in the details yourself.
3

Name and describe it

The description is what the Microsoft 365 Copilot orchestrator reads when deciding whether to route a question to your agent. Keep it specific.
4

Write the instructions

Instructions tell the agent how to behave. A good starting point:
Instructions
5

Create

Select Create. The agent’s overview page opens.
Copilot Studio must be able to choose tools on its own. Open Settings → Generative AI and confirm the orchestration is set to Generative — MCP tools are not available otherwise.

​
Step 2 — Connect the Share Of Model MCP server

1

Add a tool

Open the Tools page of your agent, select Add a tool, then New tool, then Model Context Protocol. The MCP onboarding wizard opens.
2

Fill in the server details

The server description is what the agent’s orchestrator uses at runtime to decide whether to call Share Of Model, so be explicit about what the data covers.
3

Choose the authentication

Select OAuth 2.0 as the authentication type, then Dynamic discovery as the type of OAuth 2.0 authentication.The Share Of Model MCP server publishes OAuth 2.0 metadata and supports Dynamic Client Registration, so Copilot Studio discovers the authorisation endpoints and registers itself — there is no client ID or secret to create.
Select Dynamic instead and enter the endpoints manually:If Copilot Studio shows a callback URL after you select Create, copy it and send it to your Share Of Model contact so it can be allowed for your organisation.
4

Create the connection

Select Create, then Next. On Add tool, select Create a new connection, sign in with your Share Of Model account in the window that opens, then select Add to agent.
The Share Of Model tools now appear on the Tools page. They refresh automatically — when Share Of Model adds or updates a tool, Copilot Studio picks up the change without any action from you.

​
Step 3 — Keep per-user sign-in

By default, a tool connection uses User authentication: each person is asked to connect their own Share Of Model account the first time the agent needs the data. This is the setting you want — it keeps Share Of Model permissions intact for every user. To confirm it, open the tool from the Tools page and check that the authentication is set to User authentication rather than Agent author authentication.
Selecting Agent author authentication (also shown as Maker-provided credentials) makes every user of the agent read data through your Share Of Model account. Everyone would then see everything you can see. Only use it if that is a deliberate decision.
Copilot Studio stores no Share Of Model credentials. It holds an OAuth token per user, which you or the user can revoke at any time from the connections page in Power Apps.

​
Step 4 — Test it

Use the Test your agent pane on the right of the authoring canvas. You will be asked to connect the first time a tool is called. Try:
  • List the Share Of Model workspaces I have access to.
  • Show me the completed analyses in this workspace.
  • Compare our visibility score against our top competitor over the last 30 days.
If the agent answers from general knowledge instead of calling a tool, check that generative orchestration is on and that the server description explains what the data covers.

​
Step 5 — Publish and roll out

1

Publish

Select Publish on the top menu bar, then Publish again and confirm. Publishing can take a few minutes. Republish after every change — users always talk to the last published version.
2

Add the Teams and Microsoft 365 Copilot channel

Select Channels, then the Teams and Microsoft 365 Copilot tile. Leave Make agent available in Microsoft 365 Copilot selected, then select Add channel.
3

Polish the listing

Still in that panel, select Edit details to set the icon, colour and descriptions users see in the store, then More to add your developer name, website, privacy statement and terms of use. Select Save.
Do this before you submit for approval. Changing these details later requires a new approval request.
4

Pilot with a few people

Select See agent in Teams to install it for yourself, then use Availability options → Copy link to share the installation link with a handful of colleagues. Give them access first by selecting Share on the agent’s overview page.
5

Submit it to the whole organisation

Once the pilot is satisfying, open Availability options again:
  1. Confirm the agent is not shown to teammates and shared users — remove it if it shows Added to Teams, otherwise it can end up listed twice.
  2. Select Show to everyone in my org.
  3. Review the submission requirements and select Submit for admin approval, then Yes.
Your Microsoft 365 admin reviews it in the Teams admin center. Check the status with Refresh.
6

Available to everyone

Once approved, the agent appears in the Built for your org section of the Teams app store and the Built by your org section of the Microsoft 365 Agent Store. Users install it from there and mention it with @ in Microsoft 365 Copilot.Ask your admin to use a Teams app setup policy if you want the agent installed and pinned automatically for everyone.
After submitting for approval, do not narrow who can chat with the agent. Users would install it from the store and then be unable to use it.
You only need a new approval when you change the agent’s name, icon or descriptions. Content changes — instructions, tools, topics — just need a Publish.

​
What users can ask

Once the agent is installed, people can ask in Teams or Microsoft 365 Copilot:
  • How does our brand perform across ChatGPT, Gemini and Claude?
  • Which competitors are gaining visibility this month?
  • What are our strongest and weakest perceived attributes?
  • Where are we losing AI search visibility against our main competitor?
  • Which of our creative assets scored highest?

​
Troubleshooting

Only read-only endpoints are exposed through MCP. The agent can explore analyses, metrics and evaluations, but cannot modify anything in your Share Of Model workspace.

​
What’s next

MCP Server Setup

Available tools, guided workflows and other MCP clients.

MCP Integration

Server URL, transport and authentication reference.