Connect an MCP client
Add the Chat4U remote MCP endpoint to Codex, Claude, or Cursor and verify the organization-bound OAuth connection.
3 min read
- Account menu
- MCP
Open MCP settings to manage the Chat4U connection, then complete the organization-bound sign-in in your MCP client.
Connect your client, verify the organization and project with a read, then decide whether to prepare any approval-gated action. Connection never bypasses Chat4U policy.
- Finish with
- A read-only, organization-bound MCP connection to the intended project
Use the endpoint below only when Chat4U has granted your organization MCP access:
https://mcp.chat4u.ai/mcpChoose your client
Use the matching section below. Each client uses the same endpoint and the same organization-bound OAuth flow.
Codex
Register the remote server, then complete the browser OAuth flow:
codex mcp add chat4u --url https://mcp.chat4u.ai/mcp
codex mcp login chat4uAlternatively, add the server to your Codex configuration and authenticate it through Codex:
[mcp_servers.chat4u]
url = "https://mcp.chat4u.ai/mcp"Use codex mcp list or Codex's MCP panel to confirm that Chat4U is connected. Client configuration formats can change; follow your installed Codex version's MCP guidance if its command or UI differs.
Claude
In Claude's connector settings, add a custom remote MCP connector named Chat4U and use the endpoint above. Choose Connect in a conversation, then finish OAuth in the browser with the organization you intend to use. In Claude Code, add the same remote HTTP endpoint using the version-appropriate MCP command, then authenticate from its MCP interface.
Cursor
In Cursor's MCP settings, add a remote server named chat4u with the same URL. Cursor may store it globally or in a project MCP configuration. Enable the server and complete the OAuth browser flow. Keep a project-scoped configuration only in a repository where that sharing choice is intentional; an OAuth connection still reflects the signed-in Chat4U organization.
Verify organization and project
The OAuth flow establishes your active Chat4U organization; it does not choose a project once for all future calls. Ask the client to call chat4u_projects_list, select the returned project ID you expect, and supply it to project-scoped tools. Do not paste project IDs from another organization or assume a client-side label grants access.
Verify and disconnect
Read before actingList projects, inspect one, and confirm its name and configuration.
Use only an ID returned for the active workspace. A client-side label never grants access.Find the connection recordUse Chat4U MCP and API keys settings to inspect clients and recent proposals.
Reads are policy filtered; writes remain approval gated.Revoke when no longer neededRevoke the client from the dashboard, then remove its local server/login.
Revocation is approval gated and the service rejects the connection until explicitly restored.
To disconnect, use that dashboard settings page and choose the client connection to revoke. Revocation is an approval-gated credential action. A revoked connection is rejected by the MCP service until an administrator explicitly restores it. Also remove the server or its stored login from the MCP client if you no longer want it offered locally.
Last updated on