C4UChat4U
Sign inGet started
DocumentationMCP
PRIVATE BETAREMOTE MCP

Connect Chat4U to the AI tools you already use.

Bring source health, insights, and controlled actions into Codex, Claude, or Cursor—while keeping workspace permissions and approvals intact.

Connect a client MCP settings
OAuth sign-in Role-scoped access Approval-gated writes
Choose your clientSetup takes a few minutes
CodexCLI or config.tomlClaudeApp or Claude CodeCursorGlobal or project config

BEFORE YOU CONNECT

One endpoint. Your existing permissions.

MCP access is enabled for selected workspaces during private beta.

01

Sign in with OAuth

Use the Chat4U account that belongs to the organization you want to connect.

02

Keep your role

The client can only reach projects, tools, and data allowed by your workspace permissions.

03

Approve changes

Read operations can return directly. State-changing actions wait for human approval.

INSTALLATION

Connect where you already work.

Use the same endpoint everywhere. Each client stores its own OAuth connection.

  1. 01

    Add Chat4U

    Register the remote server from your terminal.

    Terminal
    codex mcp add chat4u --url https://mcp.chat4u.ai/mcp
  2. 02

    Complete OAuth

    Choose your Chat4U organization in the browser window.

    Terminal
    codex mcp login chat4u
  3. 03

    Check the connection

    Run codex mcp list, or use /mcp inside Codex. Chat4U should show as connected.

Use config.toml instead

Add this to ~/.codex/config.toml, then run codex mcp login chat4u.

TOML
[mcp_servers.chat4u]
url = "https://mcp.chat4u.ai/mcp"
auth = "oauth"
default_tools_approval_mode = "writes"
  1. 01

    Add a connector

    Open Settings → Connectors and choose Add custom connector. Work plans may require an organization owner.

  2. 02

    Enter the endpoint

    Name the connector Chat4U and use this URL.

    MCP endpoint
    https://mcp.chat4u.ai/mcp
  3. 03

    Connect in chat

    Open Search and tools, select Chat4U, choose Connect, and complete OAuth.

Using Claude Code?

Add the remote server, then use /mcp inside Claude Code to authenticate.

Terminal
claude mcp add --transport http --scope user chat4u https://mcp.chat4u.ai/mcp
  1. 01

    Choose the scope

    Use ~/.cursor/mcp.json globally or .cursor/mcp.json inside one project.

  2. 02

    Add Chat4U

    JSON
    {
  "mcpServers": {
    "chat4u": {
      "url": "https://mcp.chat4u.ai/mcp"
    }
  }
}
  3. 03

    Authenticate

    Enable Chat4U in Cursor's MCP settings and follow OAuth. Cursor Agent users can verify from the terminal.

    Terminal
    cursor-agent mcp login chat4u

AUTHORIZATION & APPROVALS

Connected does not mean unrestricted.

OAuth identifies you and binds the client to your selected organization. Chat4U applies workspace roles and tool policy to every call.

Open approvals
1
Read

Allowed source, agent, project, and insight reads return directly.

2
Propose

A state-changing request becomes a pending action with exact inputs.

3
Approve

An authorized person reviews the action before execution.

4
Audit

The proposal, decision, actor, and outcome remain visible.

TROUBLESHOOTING

Start with the connection.

Check the endpoint, account, and workspace before changing client configuration.

The server cannot be reached

Confirm the URL is exactly https://mcp.chat4u.ai/mcp, including /mcp. Your workspace also needs private-beta access.

OAuth access is denied

Sign in with an account that belongs to the selected organization. Ask an administrator if your role lacks the requested capability.

Tools do not appear

Refresh the client after authentication and check its MCP status. Workspace and tool allowlists can intentionally hide unavailable tools.

A write is waiting

Open the approval link returned by the tool or visit Chat4U approvals. If it expired or changed, ask the client to prepare it again.

PRIVATE BETA

Connect your first client.

Open MCP settings