Connect Microsoft Copilot Studio
Connect Omnipresence to a Copilot Studio agent over MCP with a URL and a sign-in, plus what to hand your IT and security team and how to fix a failed connection.
Updated November 4, 2026
Omnipresence speaks the Model Context Protocol (MCP) with OAuth 2.1, and Copilot Studio speaks MCP natively, so connecting is a URL and a sign-in, with no MCP key to copy.
What you need
- A Copilot Studio agent in your Microsoft 365 / Power Platform environment.
- An Omnipresence account with an active subscription or enterprise contract. The connection is gated on it.
The MCP endpoint
Add this one URL. The authorization server, dynamic client registration and token endpoint are all discovered from it automatically:
https://api.getomnipresence.com/mcpConnect it
1. Add the tool
Open your agent, then Tools, then Add a tool, then Model Context Protocol.
2. Enter the server URL
Server URL: https://api.getomnipresence.com/mcp.
3. Choose the authentication
Authentication: OAuth 2.0. Copilot Studio registers itself automatically (Dynamic Client Registration) and discovers the sign-in server, so you never create a client id or secret by hand.
4. Sign in
Sign in with your Omnipresence account and approve access. The connection is account-scoped and revocable at any time.
5. Add the tools
Add the tools, starting with list_projects and use_project, then presence_overview, presence_query, and the rest. The full list is in the tool reference.
For your IT and security review
- Transport: MCP Streamable HTTP over TLS. Auth is OAuth 2.1 with PKCE (S256), with RFC 9728 resource-metadata discovery.
- What crosses the boundary: only the public prompts you track, the public AI answers, cited URLs and your configuration, never your internal documents or customer records. See our Security page and DPA.
- Access is account-scoped: a token reaches only that account's projects.
- Your own model keys: you bring your own key on every paid plan. Add it at the account level and every run uses it. The model providers bill you directly, with no markup from us. See keys and spend.
Troubleshooting
- No tools appear after sign-in. Confirm the account has an active subscription or an in-term enterprise contract. A lapsed account authenticates but returns no tools.
- Auth loop. Allow Copilot Studio to reach
getomnipresence.comandapi.getomnipresence.comover HTTPS. - A project is not listed. It may be paused, so resume it in Omnipresence.
Questions: [email protected].
Questions about connect microsoft copilot studio
- Do I need to create a client id or secret in Copilot Studio?
- No. Copilot Studio registers itself automatically through Dynamic Client Registration and discovers the sign-in server from the endpoint, so nothing is created by hand.
- No tools appear after I sign in. Why?
- The account needs an active subscription or an in-term enterprise contract. A lapsed account authenticates but returns no tools.