Who can use this feature?
- Unison users who can sign in to Unison
- Org-wide results are available only to authorized leaders and admins
- Available for Unison Intelligence launch customers
Unison MCP lets you connect your Unison Customer Knowledge Graph to compatible AI agents through an MCP server. After setup, your AI agent can help you find Accounts, review recent Touchpoints, search customer activity, retrieve Segments, and generate briefs.
Setup summary
✓ Purpose: Connect your Unison Customer Knowledge Graph to a compatible AI agent.
✓ Setup: Copy the MCP configuration from Settings > MCP into your AI client.
✓ Access: Your AI agent can retrieve only the Unison data you are allowed to access.
Connect your AI client
- Sign in to Unison in your browser.
- Open Settings > MCP.
- In Client instructions, choose the AI client you want to connect.
- Copy the command or configuration shown in Unison.
- Add the configuration to your AI client.
- When your AI client asks you to authenticate, complete the browser sign-in flow with the same Unison account you already use.
- Return to your AI client and retry the request if the client does not continue automatically.
Choose the right setup option
| Option | Use when | What to copy |
|---|---|---|
| Claude Code | You use Claude Code locally and want a terminal command. | The Claude Code command from Settings > MCP. |
| Codex | You use Codex and need to add the MCP server, then sign in. | The Codex commands from Settings > MCP. |
| Generic remote MCP client | Your client supports remote MCP servers with browser-based sign-in. | Server name, endpoint, metadata URLs, registration URL, and authentication details. |
| Hosted MCP client | Your hosted AI environment supports remote MCP connections. | The hosted server configuration, then verify compatibility in that host. |
Use the generic configuration
Use the generic setup when your AI client asks for individual remote MCP values instead of a command.
Copy these values from Settings > MCP:
- Name: unison
- URL: the Unison MCP endpoint shown in your settings page
- Transport: streamable-http
- Protected resource metadata: the metadata URL shown in your settings page
- Authorization server metadata: the authorization server metadata URL shown in your settings page
- Dynamic client registration: the registration endpoint shown in your settings page
- Authentication: browser sign-in through Unison
The endpoint usually ends with /api/mcp/unison. Use the endpoint shown in your own Unison environment rather than copying a localhost or test URL from an internal screenshot.
Sign in with Unison
When your AI client needs access, Unison opens a browser authentication flow. This flow reuses your same Unison login credentials.
- Start the connection from your AI client.
- In the browser window, confirm that you are signing in to Unison.
- If prompted, complete the Unison sign-in.
- Approve the connection.
- Return to your AI client.
Requested MCP scopes may appear during setup for client compatibility. Your effective access is still determined by your Unison login credentials and what you can access in Unison.
Understand what Unison MCP can access
Unison MCP is read-only. It can help compatible AI clients retrieve customer intelligence that the signed-in user is already allowed to access in Unison.
| Tool | What it helps with |
|---|---|
| Find Account | Searches Unison to find the correct Account and resolve aliases or abbreviations. |
| Get Account context | Reviews health, contacts, recent activity, risks, opportunities, renewal timing, and related customer context. |
| Get Touchpoints | Retrieves calls, meetings, emails, and tickets for an Account or portfolio. |
| Search Accounts | Searches for multiple Accounts within your Unison instance. |
| Get Segment | Retrieves a Segment of data. |
| Get brief | Finds or generates an account, meeting prep, or custom brief. |
Troubleshoot setup
Use these checks if your AI client cannot connect or authenticate.
- Confirm that you can sign in to Unison in the same browser.
- Retry the browser flow from the MCP connection page if the client reports an authentication failure.
- Make sure the AI client is using the endpoint from Settings > MCP.
- For Codex, add the MCP server first, then run the login command shown in Unison.
- If your client asks for metadata URLs, copy both the protected resource metadata URL and authorization server metadata URL from Unison.
- If you are testing in a local environment, use the backend API URL from the settings page, not the frontend page URL.
- If a request returns less data than expected, check whether your Unison role or account assignments limit access.
FAQs
Question: Do I need a separate Unison API key?
Answer: No. End users authenticate with Unison through the browser flow. API keys are not used for standard Unison MCP setup.
Question: Can any user search the whole organization?
Answer: No. Org-wide scope is available only to users who can access that information in Unison.
Question: Why does the setup page show scopes if permissions are handled by Unison?
Answer: Some MCP clients expect scopes during setup. Unison exposes read scopes for compatibility, but effective access is based on your Unison role, permissions, and instance.
Question: Which AI clients are supported?
Answer: The Unison MCP setup page includes instructions for Claude Code, Codex, generic remote MCP clients, and hosted MCP clients that support remote MCP connections with browser-based sign-in.
Question: What should I do if authentication fails?
Answer: Sign in to Unison in the browser first, then retry the MCP connection. If your AI client stores an old connection, remove the Unison MCP entry and add it again from the latest settings page values.