⚠️ This is an experimental feature and a work in progress. The setup and what it can access may change as we develop it. Reach out to your uman contact if you would like to try it.

🔌 What this is

You can add uman as a tool to an agent in Microsoft Copilot Studio. Your agent can then look up and search your uman data (accounts, deals, meetings, leads, outreach and portfolio) whenever you ask it something. The connection is read-only and only ever sees what you see in uman. See the Overview for everything it can access.

📋 What you need

Access to Copilot Studio with permission to edit an agent.
An active uman account. You sign in with the same Microsoft or Google work account you use for uman.

🛠️ Add uman to your agent

In Copilot Studio, open Agents and select the agent you want to connect, or create a new one.
Go to the Tools tab and select Add a tool.
Under Create new, select Model Context Protocol.
Fill in the server details:
- Server name: uman
- Server description: Read-only access to uman: accounts, deals, meetings, leads, outreach, portfolio and search. Your agent uses this description to decide when to call uman, so keep it clear.
- Server URL: https://mcp.uman.ai/sse
Under Authentication, select OAuth 2.0, and as Type select Dynamic discovery. There is nothing else to fill in: Copilot finds uman's sign-in page by itself.
Select Create. You see the message that the uman custom connector has been created.
Next to Connection, open the dropdown, select Create new connection, and then select Create.
A sign-in window opens. uman asks you to confirm that you want to connect Copilot to your uman account. Approve it, then sign in with Microsoft or Google, whichever you use for uman.
Back in Copilot Studio, the connection now shows a green dot. Select Add and configure.

uman now appears under your agent's tools, together with the list of things it can look up.

✅ Check that it works

In the Test your agent panel, ask something like "List my uman workspaces" or "Which meetings do I have with Acme this month?". Your agent calls uman and answers with your data. Select the step in the conversation to see which uman tool it used and what came back.

🔑 Signing in

Everyone who uses the agent connects with their own uman account, so each person only sees the uman data they already have access to.
You only sign in once. Copilot keeps the connection active in the background.
You can remove the connection at any time from the Connection dropdown on the uman tool, or from your connections in Power Apps.

🏢 For IT admins

Admin approval: if your organisation does not let users approve outside apps themselves, users see a message that admin approval is needed when they sign in with Microsoft. A Microsoft Entra administrator then needs to approve the uman app once for your organisation.
Data policies: Copilot Studio connects to uman through a Power Platform connector, so your Power Platform data policies apply to it. If a policy blocks custom connectors, allow the uman connector in the Power Platform admin center.
No setup on the uman side: each agent registers itself with uman when the connection is created, so there is no client ID, secret or redirect URL to exchange with us.

❓ Troubleshooting

The sign-in window does not open: allow pop-ups for copilotstudio.microsoft.com and select Create new connection again.
Sign-in is refused: make sure you sign in with the account you use for uman. Only people with a uman account can connect.
The agent stops finding your data: open the uman tool, remove the connection, and create a new one.

Still stuck? Reach out to your uman contact.