Skip to main content

Connect Nexatron to Claude

Connect Claude to Nexatron's hosted MCP server to ask business questions and use the analytical tools available to your Nexatron account. Source access, metric definitions and enabled workspace controls determine what can be answered. A connected status confirms the connection, not the correctness of an answer.

Nexatron is listed in Claude's connector directory, so most people add it from there. Adding the server URL as a custom connector is the alternative. Both paths reach the same hosted server. For the local stdio package, see MCP Integration; it exposes a different tool set.

Before connecting​

  • Choose the Nexatron account and workspace you intend Claude to access. Use a restricted demo identity with synthetic data for an external demonstration.
  • Confirm source access in Nexatron and any required workspace approval. Source authorization and authorization for Claude are separate steps.
  • Your Claude plan and your Claude organization's settings decide which connectors you can add. Ask your Claude organization owner if Nexatron is not available to you.
  • Decide whether the workflow needs analytical reads or actions. Do not request broader access solely to make a demonstration easier.

Add Nexatron from Claude's connector directory​

  1. In Claude, open Settings → Connectors and browse the connector directory.
  2. Search for Nexatron and open its listing.
  3. Choose Connect. Claude opens the Nexatron sign-in page.
  4. Sign in with your Nexatron identity. Check the account and workspace before approving the requested access. OAuth uses an authorization code and PKCE; enter your password only in the Nexatron sign-in flow.
  5. Open the connected Nexatron entry and inspect its tools and permission settings. Keep approval required for any tool that changes data. A tool marked read-only can still return sensitive information from sources you can access.
  6. Start a new Claude conversation with Nexatron enabled. Begin with approved synthetic data or a narrowly scoped business question.

Claude's menu labels change from time to time and can differ between the web, desktop and mobile apps. If you do not see these labels, check the current product UI or Claude's own help pages.

Alternative: add a custom connector​

Use this path when the directory listing is not available to your Claude organization, or when you need to point Claude at the server URL directly. See Claude's custom connector instructions for the current steps.

  1. In Claude's connector settings, choose the option to add a custom connector.

  2. Enter this server URL:

    https://api.nexatron.io/api/v1/mcp

  3. Connect and complete the Nexatron sign-in, then continue from step 5 above.

Workspace approval (first connect)​

A Nexatron workspace administrator approves Nexatron for the workspace before people there can connect an AI assistant. When someone connects Claude to a workspace that has not approved it yet, the request waits as pending, and that person reconnects after an administrator reviews it.

Review pending requests under Settings → Integrations → AI assistants (MCP) → Pending approvals. Approve only the intended client and access. Workspace approval does not replace the individual account's permissions or source authorization.

Claude registers a new OAuth client with Nexatron for each new connection. Today, approval applies to one registered client at a time, so an administrator can see a new pending request when another person connects Claude. An upcoming update changes this: once Claude is approved for a workspace, later Claude connections to that workspace follow that approval. That applies only to connections that use the same HTTPS sign-in callback addresses. It never carries across workspaces, and a request the administrator rejected stays rejected.

Verify your first analytical workflow​

Use an approved reference result and record the account role, source snapshot, question and observed result. The following is an evaluation procedure, not a claim that a particular customer dataset has passed it.

  1. Check available sources. Ask Claude to list your Nexatron sources. Confirm the expected source and its authorization state before querying it.
  2. Ask one bounded question. Specify the period, population and grouping. For example, ask for net revenue by region for a defined quarter. Nexatron's ask tool handles natural-language questions; browsing the metric catalog is not a prerequisite for every question.
  3. Inspect a named metric when needed. Use list_metrics and explain_metric to review the definitions available to you. Use query_metric for a specific named metric. These tools are listed only when your workspace can answer them. Suggested definitions and enabled governance controls need separate review; do not assume every question uses an approved metric.
  4. Check the result. Reconcile totals and representative breakdowns with the approved reference. Inspect available query, lineage and error information. A trust label alone does not establish correctness.
  5. Ask a follow-up. Change the period or grouping and verify that the intended definition remains consistent. For cross-source work, first check compatible grain, metric definitions and access for every participating source.

Analytical reads and actions​

Review the actual tools in Claude's connector details. Discovery and analytical reads are distinct from executing an action. Use list_actions to inspect available actions and dry_run to review a proposed action contract when the account is entitled to it. execute_action can change a connected system. Review its target, parameters, predicted side effects and required confirmation before approving execution. A tool's presence does not prove the current user is authorized to perform every action.

See the MCP reference for the documented interface, and compare it with the tools exposed by your connection.

What this connection does not imply​

  • Configuring an external MCP service as a source in Nexatron does not automatically pass every upstream tool through to Claude.
  • Missing source access, incomplete metric setup or disabled controls are not resolved simply by connecting an MCP client.
  • Source credentials and MCP tokens are separate. Never paste warehouse credentials, tokens or private results into a public troubleshooting report.

Permissions and sessions​

Claude asks for scopes when it connects, and Nexatron checks them on every tool call. When Claude asks for none, the connection gets the read-only defaults mcp:query, mcp:read and openid. Action scopes are never granted by default.

Two settings decide which tools a connection sees:

  • The workspace action setting. The action tools are on by default for each workspace, and a workspace administrator can switch them off. When they are off, every connection to that workspace sees only the analytics tools.
  • The scopes the connection was granted. With an upcoming update, the tool list follows the granted scopes. A connection that granted only read scopes (Claude's default request is mcp:read mcp:query openid offline_access) sees only the analytics tools, even when the workspace has actions on. The action tools appear only for a connection that was also granted an actions:* scope. Today the tool list follows the workspace setting alone, but a call to an action tool without an actions:* scope is still refused.
ToolAccepted scopes
list_sources, list_metrics, explain_metricmcp:read or mcp:query
askmcp:query
query_metricmcp:metrics:execute or mcp:query
compare_metric_across_sourcesmcp:federation, mcp:metrics:execute or mcp:query
auditchecks the account's own role instead of a scope
list_actions, dry_run, execute_actionan actions:execute_low, _medium or _high scope; running an action also needs the tier that matches its risk

A scope only narrows what Claude may do on your behalf. It never adds to what your Nexatron role allows: row policies, masking and metric access still apply to every answer.

Session lifetimes. The sign-in code is valid for 60 seconds. An access token lasts one hour. If Claude asked for offline_access, it also receives a refresh token that lasts 30 days and is replaced every time it is used, so Claude can renew the session without asking you to sign in again.

Disconnecting. Removing the connector in Claude stops Claude from using it. A tenant administrator can also revoke a Claude client under Settings → Integrations → AI assistants (MCP): every token issued to that client in the workspace stops working at once. Nexatron also has a pre-registered Claude client that is approved for every workspace and has no workspace approval to revoke; if your connection uses it, remove the connector in Claude to disconnect.

When a session ends. An expired or revoked token is refused with 401 Unauthorized and a WWW-Authenticate header that tells Claude where to sign in again. Claude then offers to reconnect. Reconnect with the same Nexatron account; see Troubleshooting below.

Troubleshooting​

Sign-in does not open. Check the exact server URL and the browser's popup settings. Inspect the error before removing a working connection.

Workspace approval required. Ask the tenant administrator to review the pending request under Settings → Integrations → AI assistants (MCP) → Pending approvals, then reconnect with the intended user account.

Tools missing. Confirm Nexatron is connected and enabled in the conversation. Review the connector's tool permissions and organization controls. Refresh the tool list if your Claude client offers that action. If only the action tools are missing, check whether the workspace has actions switched off and which scopes the connection was granted (see Permissions and sessions).

Unauthorized or expired session. Reconnect with the intended Nexatron account. Do not switch to an administrator account merely to bypass an access failure.

Empty results or permission denied. Check the source's authorization state, the account role and the requested scope in Nexatron. An empty result alone does not prove the source contains no records.

Unexpected answer. Preserve the question, source snapshot and reference result in an approved internal location. Review definitions and source coverage before broadening the query or treating the answer as a reporting result.

Next steps​

Last updated on