Chat4U MCP overview

Chat4U MCP lets an external AI client work with the same project-scoped control plane used by Chat4U. It is for safe operational work—not a way to browse raw customer data, scrape sources, or control a visitor’s browser.

Choose your MCP task

Start with the smallest privilege and the clearest outcome.

Get connectedConnect an MCP client

Sign in and select the intended workspace and project.

ToolingFind the right tool

See what reads and proposal-based changes are supported.

ChangesPrepare a safe change

Understand exact proposals, approvals, retries, and request IDs.

AutomationSet up service-account access

Use the separately gated, single-project API-key capability.

The rule that matters

What stays protected

• OAuth callers are checked against workspace role, project, capability, and entitlement.
• Service accounts, where enabled, are tied to one immutable project.
• Raw source contents, transcripts, message examples, internal instructions, and sensitive values are not returned.
• A service account can prepare a write but cannot supply human approval evidence.

Start with reads. When a change is needed, prepare the exact proposal, obtain first-party approval, then retry the unchanged request with the same client_request_id.

MCP cannot create a project in the current catalog. File uploads and unrestricted source content remain dashboard-only. Destructive changes are proposals that follow the stronger first-party approval path.

Last updated on