Server address
The same address for every client and every customer. Also shown in Odins under Settings and MCP setup.
Before you start
The Odins MCP gives Copilot access to your own model and data. Copilot reads from it. The data work, the model and the analyst review stay with Odins.
-
An Odins subscription with MCP switched on
MCP is enabled per organisation. If you are not sure, ask your Odins contact.
-
An Odins user for each person
Everyone who will ask questions needs their own Odins login with two-factor sign-in. Without one, the connection cannot complete.
-
For Copilot Studio: credentials and a connector definition
Both come from the Odins platform, under Settings and MCP setup. You also need a Power Apps environment where you can create a custom connector.
What Copilot can and cannot do
Copilot sees only the data your Odins user can see; access follows the person, not the connector. It never touches your ad accounts. Where your Odins role allows a change inside Odins, such as saving a budget, it asks before it runs the tool.
GitHub Copilot in VS Code
The server connects directly. VS Code handles the sign-in.
-
Add the server
Open VS Code in any project. Run MCP: Add Server from the Command Palette and choose HTTP.
-
Paste the address
Paste the server address, name the server Odins and pick Workspace or Global.
Server address
https://app.odins.ai/mcp -
Sign in
VS Code opens a browser window the first time the server connects. Sign in to Odins and approve.
-
Or commit it as a file
For a project the whole team shares, add the server to
.vscode/mcp.jsonand commit it..vscode/mcp.json
{ "servers": { "odins": { "type": "http", "url": "https://app.odins.ai/mcp" } } }
VS Code's MCP documentation covers workspace and global scopes.
Copilot Studio
Copilot Studio cannot register itself with Odins the way Claude and ChatGPT do, so it signs in through a Power Platform custom connector. The credentials and the connector definition come from the Odins platform, and the connection is limited to that organisation.
-
Create the credentials in Odins
Sign in to Odins, open Settings and MCP setup, pick Copilot Studio and create the credentials the connector signs in with. The client secret is shown once, so copy it there and then. Every reveal is recorded in your organisation's audit log.
-
Create the connector in Power Apps
Open Custom connectors, then New custom connector and Create from blank. Name it Odins. On the Definition step, open the Swagger editor and replace everything in it with the connector definition copied from the Odins setup page.
-
Set the security
On the Security step, set Authentication type to OAuth 2.0 and Identity provider to Generic OAuth 2. Paste the client ID and secret, then the two URLs. Leave scope blank: each person gets exactly what their Odins access allows.
OAuth URLs
Authorization URL: https://app.odins.ai/oauth/authorize Token URL and Refresh URL: https://app.odins.ai/oauth/token -
Register the redirect URL
Select Create connector. The Security step now shows a Redirect URL. Paste it into the Odins setup page exactly as shown and register it, then select Update connector in Power Apps.
-
Connect, and add the tool
On the Test step, select New connection: Odins opens, you sign in and approve. Then add the connector as a tool in your Copilot Studio agent and pick this connection. Every person who uses the agent connects with their own Odins user.
If it does not work
The two connector errors keep your sign-in valid: you change the connector, not the connection.
-
No sign-in, and the agent reports invalid_token
The connector is calling Odins anonymously. Reopen the Security step, set OAuth 2.0 and Generic OAuth 2 again, select Update connector, then create the connection again.
-
The agent reports Method not allowed
In the Swagger editor, the operation under
/mcpmust sit onpost:withx-ms-agentic-protocol: mcp-streamable-1.0. Save and select Update connector. -
Cannot connect, or MCP not enabled
MCP may not be switched on for your organisation yet. Ask your Odins contact.
-
Still stuck
Your Odins contact can check the connection attempts from our side.
Questions
Can I use Odins from Microsoft Copilot?
Yes, in two ways. GitHub Copilot in VS Code connects to the Odins MCP server directly. A Copilot Studio agent connects through a Power Platform custom connector that signs in to Odins with OAuth. Customers run both today.
What is the Odins MCP server address?
Why does Copilot Studio need a custom connector?
Copilot Studio cannot register itself with Odins, so the connector signs in with a client ID and secret that Odins issues for your organisation. The connector definition, the credentials and the redirect URL registration are all handled on the MCP setup page in Odins.
What does Copilot see?
Only what your Odins user can see: the organisations, markets and data your access allows. Every person connects with their own login, so access follows the person. Copilot reads from Odins when you ask it a question.
Does Copilot change anything in our ad accounts?
No. Odins recommends: how much to spend, where, and what to test. Copilot reads those answers. Acting on them stays with you. Where your Odins role allows a change inside Odins, such as saving a scenario or a budget, Copilot asks before it runs the tool.
Is Microsoft Copilot harder to set up than Claude or ChatGPT?
Copilot Studio takes more steps, because the sign-in runs through a Power Platform connector. VS Code is four steps. Claude and ChatGPT are the clients Odins has the most experience with. See Odins in Claude and Odins in ChatGPT.
Does the Odins MCP work with other Microsoft tools?
The two routes on this page are the ones in use today. To connect something else on the Microsoft stack, ask your Odins contact.
-1.png?width=1132&height=292&name=Asset%201@2x%20(12)-1.png)