Skip to main content

Upgrade to the New UE MCP Server

We’re upgrading the UE MCP server, which connects AI assistants like Claude, ChatGPT, and Cursor to your UE account. The new server gives admins more control over these connections. This article outlines the changes and any action you may need to take.

T
Written by Tom Aristone

If your assistant connects to https://app.userevidence.com/mcp, you don’t need to change the URL. That address will keep working and will point to the new server.


​

If you connected your own AI assistant

Each connection needs to be reauthorized once:

  • By default, you don’t need to do anything in advance. When your account moves to the new server, your assistant will open the UE sign-in page. Sign in, click “Allow access,” and your assistant will work as before.

  • If your assistant shows errors instead of asking you to sign in, follow the reconnect steps below. Some assistants won’t prompt you, depending on how they first connected.

  • If you’d like to switch now, you don’t have to wait. Follow the reconnect steps below. After you reconnect, the rest of the migration won’t affect that connection.
    ​



How to reconnect

  1. Remove the UE connector from your assistant

  2. Add a new connector using https://app.userevidence.com/mcp/v1

  3. Sign in and click “Allow access”
    ​



For account admins

Some organization-wide setups won’t reconnect on their own and need action from an admin:

  • AI tools configured with a client ID: These will stop working when we retire the legacy server’s original sign-in method, which happens for all customers at the same time. Act early to avoid disruption. You can fix this in one of two ways:
    ​

    • Re-add the connector using only https://app.userevidence.com/mcp/v1, so each person signs in for themselves.

    • Create an org-wide credential in Settings → MCP and enter its client ID and secret in the tool’s admin settings.
      ​

  • Integrations that use an account API key: The new server doesn’t accept API keys. These integrations will keep working until the legacy server is retired, which is the final stage of the migration. Before then, switch each one to an org-wide credential and test it. Some tool names have changed on the new server, so integrations may need small updates.

  • Review your settings: In Settings → MCP, you can see every connection, limit which tools are available, set rules by role, and switch connections off. Private evidence is off by default on the new server. If your team’s assistants need private evidence, turn it on for each connection.

  • Let your users know they should expect one sign-in prompt in their assistant. If they see errors instead, they should follow the reconnect steps above.
    ​



Troubleshooting

  • “Wrong account” on the approval screen: A different UE account already approved the assistant. Remove the connector and add it again.

  • Your assistant stops working or asks you to sign in again later: An admin may have switched off or removed the connection in Settings → MCP, or rotated its secret. Check with your UE admin.

  • 404 Not Found: MCP isn’t enabled for your account yet. Please contact us.
    ​


If you have any questions, please contact your Customer Success representative or email us at [email protected].

Did this answer your question?