Connect an external AI app to Nexia

Before you start

Your company must have external AI connections enabled. Enter the Nexia MCP URL in a compatible app, sign in, and allow the connection. The app and Nexia establish the client information automatically; administrators do not need to register each app. The app must support MCP 2026-07-28 and CIMD-based OAuth. Compatibility with every app is not guaranteed.

You need a Nexia account and permission to access the relevant business data. Retrieved data is sent to and processed by the external app. Review the app and the access you intend to grant.

This guide covers using Nexia from an external AI app. It does not cover adding another service's MCP server to the Nexia agent.

Find your connection URL

1. In Nexia, open Agent management → Personal settings → AI app connections (MCP) and copy the URL under How to connect. The shared address is https://mcp.nexia.to, without an added path.
2. Enter the URL in the external app's MCP settings. If it requires a configuration file, use its supported format; Nexia also provides a copyable VS Code JSON example.
3. Start the connection. On the Nexia company selection screen, enter your company address or subdomain, for example example or https://example.nexia.to.
4. Continue to that company's sign-in screen, complete any required SSO or verification, and check the company and account before allowing access.

Each connection belongs to the company selected during sign-in. To use another company, create a separate connection and select that company. Existing company-specific MCP URLs remain supported; you do not need to replace a working connection.

Choose permitted operations

Check the app name, company and account on the consent screen, then choose the operations to allow.

You cannot select operations the app did not request or that your current permissions and policies do not allow. Allow the connection, return to the external app and check that it completes.

Consent does not grant new business permissions. Your access to legal entities, operating units and records still applies, as do company agent tool policies.

Read data and request changes

Tell the external app what you need and which organization you mean. Read tools can discover data types, describe fields and query options, find authorized organization targets, and retrieve a list or a single item. The AI app connections (MCP) page also explains the available tools.

Connections with create/update or delete access additionally expose change-request and request-status tools. These cover generic single-resource creation, updates and deletion. They do not expose every business feature, batch changes or custom workflow actions.

Review changes that require confirmation

1. Follow the Nexia review link provided by the external app, or find the request under pending approvals on AI app connections (MCP).
2. Review the requesting app, target data, operation and submitted values.
3. Reject an unwanted request. To proceed, choose the approve-and-execute action and confirm.
4. Check the result before continuing in the external app.

A company policy block still applies even if you granted the operation during connection. Changes that require confirmation must be approved in Nexia. Changes permitted to run automatically may execute without a separate approval. Read operations requiring confirmation are currently unavailable through an external connection.

Review requests expire 15 minutes after creation. An expired request cannot execute; submit a new request if it is still needed. If execution is in progress or the outcome is unknown, check the actual data and request status before submitting another change. A new request could duplicate the operation.

Manage or disconnect a connection

Select an app on AI app connections (MCP) to inspect granted operations and recent usage. Settings → Security & access → External AI connections also lists these separately from browser sign-in sessions.

Access tokens expire after one hour. Apps that support automatic refresh can keep the connection active. If refresh is rejected or the connection is revoked, reconnect.

To stop access, select the app's disconnect action and confirm. Subsequent requests are blocked, but disconnection does not recall data already sent to the app or undo work already executing.

Troubleshooting

• The feature or client is unavailable: Ask your administrator to check feature availability, and check that the external app supports the documented MCP and OAuth flow.
• A read or change is refused: Check the connection grant, permissions for the target organization and agent tool policies.
• Refresh fails or authentication expires: Reconnect from the external app. If failures repeat, check its OAuth refresh support.
• The approval link is unavailable: Sign in to the company and account that authorized the connection. Requests from revoked connections cannot be approved.

Related guides

• Use the Nexia agent workspace
• All product guides