Skip to content
Welcome to the new Tahua Help Center!
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Connect GUI AI assistants to hosted MCP by pasting a URL

What problem it solves

The hosted MCP server previously only supported command-line MCP clients (Claude Code, Codex CLI): connecting required copying a JSON config block containing a pre-provisioned OAuth client ID and a fixed callback port into a config file. Graphical AI apps — Claude on the web and desktop, Cursor, VS Code and others — could not connect at all, because they register themselves with the OAuth server automatically and use their own callback URLs.

Most administrators are non-technical and use exactly those GUI apps, so this made the MCP integration inaccessible to the people it is for.

How it works

The tenant's MCP OAuth server now supports OAuth 2.0 Dynamic Client Registration (RFC 7591). When an administrator pastes the tenant's MCP URL into a compatible AI app, the app:

  1. Discovers the tenant's OAuth configuration from the server's standard metadata documents (which now advertise a registration endpoint).

  2. Registers itself automatically as a public (no-secret) OAuth client. Registration is only accepted for redirect URIs that are HTTPS, loopback HTTP (localhost), or a native app's private-use scheme — never plain HTTP to a remote host.

  3. Opens a browser window where the administrator signs in to their tenant and approves read-only access — the same consent, PKCE and per-connection controls that already protected the command-line flow.

Self-registration grants nothing by itself: every connection still requires an active tenant administrator to sign in and approve it, the tenant's "Hosted MCP access" setting must be enabled, and each connection remains individually revocable from Settings. Registrations are rate-limited, logged as security events, and self-registered clients that are never approved are automatically cleaned up after 30 days.

UI changes

On Settings → organisation → API & MCP, the "Connection details" section now has two tabs:

  • AI apps (default): shows the tenant's MCP URL with a Copy button and step-by-step instructions for connecting Claude (Settings → Connectors → Add custom connector). Works for Claude web/desktop, Cursor, VS Code and other MCP-compatible apps.

  • Command line: the existing copy-paste JSON config for CLI clients (Claude Code, Codex), including the Create connection button for provisioning the CLI client.

The "Authorized connections" table lists connections from self-registered GUI clients alongside CLI ones, with the same Revoke control.

Last updated

Was this helpful?