Authentication
How Everyn MCP binds one user, one client, and one organization through WorkOS Connect.
The public production MCP endpoint is live at https://mcp.everyn.ai/mcp. Configure a host with that Streamable HTTP URL and complete WorkOS OAuth.
Everyn MCP authenticates through WorkOS AuthKit Standalone Connect. Everyn remains the resource server: it validates the token, intersects scopes with current membership, and authorizes every tool call against the selected organization.
Binding
One grant binds:
- one user
- one client
- exactly one explicitly selected Everyn organization
There is no first-membership fallback. Callers cannot select another user or organization from tool input. No MCP tool accepts organization_id, organizationId, or org_id.
Membership removal or role reduction removes authority promptly. Tokens issued for the dashboard, another Everyn service, or another organization are rejected.
Scopes hosts may request
WorkOS cannot advertise custom Everyn scope strings on CIMD or dynamic client registration. Hosts that register that way must request only:
| Scope | When to request it |
|---|---|
openid | Required OIDC. |
profile | Basic profile claims. |
email | Email claim. |
offline_access | Durable reconnect where the host supports refresh. |
Do not add custom Everyn scope strings such as everyn.inspect, everyn.create_edit, or everyn.run to CIMD or DCR registration. Those strings are not live scopes_supported values on CIMD/DCR.
What users see at consent
Consent groups permissions for humans as:
- Inspect Everyn
- Create and edit
- Run work
Grouping never broadens the underlying grant. Human-only billing mutation, payment, API-key administration, and organization administration remain unreachable from MCP.
During connect, the user picks one current membership. If the wrong workspace is bound, disconnect in the host and connect again, then select the correct organization.
Paid admission
start_run uses Everyn's shared billing controls. MCP does not implement checkout, funding top-up, plan change, or payment mutation.
If admission is denied, report the stable error and send the user to Usage and Billing at https://app.everyn.ai/settings. A paused Run after mid-run wallet exhaustion preserves completed work; resume it after Usage and Billing shows spendable value.
Reconnect and revoke
Inspect, reconnect, and revoke from MCP settings. Reconnect is the normal host authorization flow plus that Settings control. Exact revoke can fail closed; Settings then leaves the connection unchanged rather than pretending the host grant ended.
If the wrong workspace is bound, disconnect in the host and connect again, then select the correct organization at consent. Everyn intersects every call with live membership, so removing a person from the organization ends MCP authority for that workspace.
Do not paste access tokens, refresh tokens, or signed transfer descriptors into chat, tickets, or logs.