For individual access using your own Kadoa account, see MCP Server setup →.
Setup
-
In Kadoa, open Settings → Service accounts, select the service account the connector should act as, and find MCP service connector. Only workspace Owners and Admins signed in with their own account can do this. The connector acts with that account’s role, so choose an account whose role fits what members should be able to do.

-
Select Generate credentials and copy the MCP server URL, OAuth client ID, and OAuth client secret. The secret is shown once.

- A Claude organization owner opens Organization settings → Connectors, clicks Add, and chooses Custom → Web.
-
Enter a name (for example
Kadoa) andhttps://service.mcp.kadoa.com/mcp, then paste the OAuth client ID and secret under OAuth client. - In the connector’s tool settings, allow only the tools that organization members should use.
- Organization members open Customize → Connectors, find the custom connector, and select Connect.
How it works
The connector is an OAuth client (a client ID and secret) registered with Kadoa for your workspace. When an organization member selects Connect in Claude, the OAuth handshake completes silently againsthttps://service.mcp.kadoa.com/mcp, with no Kadoa login or consent screen. The resulting session acts as the service account the connector belongs to.
- The service connector uses a separate hostname from the personal connector at
https://mcp.kadoa.com/mcp, so users can configure both side by side. - All members share the same service-account identity and team, and team switching is unavailable.
- Each service account has at most one active connector. A workspace can have several, one per service account, for example a read-only Viewer account for most members and a Member account for a smaller group. Each connector has its own credentials, and rotating or revoking one does not affect the others.
- A connector created before service accounts could be named belongs to the workspace’s default service account, which has the Admin role.
The service connector acts as its service account: every tool call runs under that account, with its role, in its team, and workflow history records the service account, not the individual member who ran the action. If you need per-user attribution, use the personal connection.
Supported clients
Claude (Team and Enterprise custom connectors) is supported today. Other MCP clients need their OAuth redirect URI registered with Kadoa first. Contact support to enable one.Manage access
- The client secret is shown once, at generation or rotation. Store it securely.
- To rotate credentials, select Rotate secret in Kadoa, replace the secret in Claude’s connector settings, and reconnect. Rotation immediately invalidates tokens issued with the previous secret.
- To stop all access through a connector immediately, select Revoke connector on its service account. Deleting the service account revokes its connector too.
- To limit what members can do, restrict the allowed tools in the MCP client’s connector settings.