Connect AI

Use Claude, Cursor or any MCP client with UnifiedMCP to manage your account from the client. You can also give a client the tools of one of your connected apps.

Setup guides for more clients, and the full list of tools, are in the UnifiedMCP MCP guide.

Manage UnifiedMCP from your AI client

Each product has its own management MCP server, so a client only sees the tools of the product you connect it to. These tools work on your account itself: servers, connections, policies and so on.

UnifiedMCP MCP server

Manage hosted MCP servers: tool allow-lists, access policies, DLP rules, grants and access requests.

https://api.unifiedmcp.com/mcp/mcp

Set up your client

Signing in uses OAuth: the client opens UnifiedMCP in your browser, you choose a workspace and approve what it may do. It acts with your own role in that workspace.

In Claude, open Settings → Connectors and choose Add custom connector.
Paste one of the management server URLs above and add it.
Click Connect, sign in, and approve access.

Connect an app to your AI client

Not the UnifiedMCP management server (see the Manage UnifiedMCP tab): these URLs give the client the tools of one connected app, such as your CRM, by creating an MCP server for it.

This is a UnifiedMCP feature: UnifiedData and UnifiedFlows serve only their own management MCP server.

Create an MCP server from your AI client

Add a connected app, such as your CRM or ticketing system, to Claude, Cursor or another MCP client in one step. You give the client a URL; when it asks you to sign in, you connect the app and approve, and UnifiedMCP creates an MCP server for it. There is no server URL or token to copy.

1. Choose a URL

You choose the app when you sign in. Use it again for each app you add.

https://api.unifiedmcp.com/mcp

2. Add it to your client

In Claude, open Settings → Connectors and choose Add custom connector.
Paste the URL above, give it a name such as unifiedmcp-apps, and add it.
Click Connect. Claude opens UnifiedMCP in your browser.

3. Sign in and approve

Sign in to UnifiedMCP if you aren't already, and pick the workspace the server belongs in.
Choose the app (unless the URL names it), then pick one of its existing connections or connect a new account.
Name the server and choose the LLM client it is tuned for. Admins can assign an access policy; without one, choose whether to remove sensitive data and which tools to allow (for example crm_*).
Click Create server and allow access. You're returned to the client, which can now use the app's tools.

You need the member role or higher in the workspace. The sign-in page stays valid for 30 minutes.

What the client can do

It reaches only the server created when you approved, and only through the URL you gave it.
It sees that server's tools, limited by the tool list and sensitive-data setting, or by the access policy's tool list, data protection and network restrictions if you assigned one.
Its access is yours: if you're removed from the workspace, it stops working straight away.

Manage and disconnect

Each approval creates a new server, listed under MCP Servers, where you can change its settings and see its activity.
Deleting the server disconnects the client. Connecting it again creates a new server.
Removing the connector from the client stops the client, but leaves the server in place.

Troubleshooting

"Not found" when adding a /mcp/… URL: the app name in the URL isn't recognized. Copy the URL from this page.
"Expired or already answered": the sign-in took longer than 30 minutes, or the page was used already. Start again from the client.
"Started by a different user": you're signed in to UnifiedMCP as someone else. Sign in as the person who started connecting, or start again from the client.
The client asks you to sign in again: its server was deleted, or you were removed from the workspace. Connecting again creates a new server.