Connecting an AI Assistant

Step by step guide to enabling MCP access and connecting your AI assistant to Tahua.

You will need an administrator account with the Manage Integrations permission to follow these steps.

Enabling hosted MCP access

1

Navigate to the API & MCP settings

Go to your Organisation Settings and open the API & MCP tab.

2

Enable hosted MCP access

In the Hosted MCP access section, select Enabled and click Save changes.

You will see the confirmation "Hosted MCP access is now enabled", and a Connection details section will appear below the toggle.

Connecting an AI app (Claude, Cursor, VS Code)

Use this option for desktop and web AI applications that support remote MCP servers.

1

Copy your connection URL

In the Connection details section, make sure the AI apps tab is selected, then click Copy to copy your organisation's unique MCP URL.

2

Add the connector in your AI app

In Claude (web or desktop), go to Settings → Connectors → Add custom connector, paste the URL, and confirm.

Other apps that support remote MCP servers (Cursor, VS Code, and others) have an equivalent "add MCP server" option - paste the same URL there.

3

Sign in and approve access

Your browser will open a Tahua sign-in page. Sign in with your administrator account and approve the read-only access request.

Once approved, the Tahua tools become available to your assistant and you can start asking questions about your data.

Connecting a command-line client (Claude Code)

Use this option for terminal-based clients such as Claude Code.

1

Create a connection client

In the Connection details section, switch to the Command line tab and click Create connection.

Tahua provisions a connection client for your organisation and shows a ready-to-paste configuration block. Clicking the button again later simply shows the same details - it never creates duplicates.

2

Paste the configuration into your MCP client

Copy the configuration block into your client's MCP settings. For Claude Code, it goes in the mcpServers section of your MCP configuration file and looks like this:

"tahua-yourorganisation": {
  "type": "http",
  "url": "https://yourorganisation.api.tahua.io/mcp",
  "oauth": { "clientId": "your-client-id", "callbackPort": 49152 }
}

Use the exact values shown in your settings page - the URL and client ID are unique to your organisation.

3

Connect and approve

Run /mcp in your client and select the Tahua server. Your browser will open - sign in as an administrator and approve the connection.

The client ID is not a secret, but every connection still requires an administrator to sign in and approve access in the browser. Anyone connecting must have their own Tahua administrator account - access can never be shared through the configuration alone.

Troubleshooting

• The Connection details section doesn't appear - hosted MCP access is disabled. Enable it as described above. If you see a message that hosted MCP is not fully configured for your tenant, contact support.

• The browser approval fails - make sure you are signed in as an administrator of the correct organisation, and that your account has an active administrator role.

• The assistant says the connection is unauthorised - the connection may have been revoked, or MCP access disabled for your organisation. Check the Authorized connections table in Settings, then reconnect.