6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Manage a WorkOS workspace.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The WorkOS MCP server connects a WorkOS workspace to Claude, ChatGPT and any MCP-compatible agent. It ships four tools, but two are generic verbs — query and mutate — that dispatch onto WorkOS's management API: 28 resource groups and 240 documented operations covering organizations, users, SSO connections, directory sync, roles and audit logs. Sign-in is OAuth against signin.workos.com.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
mutate dispatches.mutate verb on an identity platform.scopes_supported is an empty array on the descriptor; the authorization server offers only email, profile, openid and offline_access. The read/write split exists, but as a dashboard role and a team admin toggle, not a scope.initialize on 2026-08-19, so no schemas and no safety annotations were readable. WorkOS publishes no tool descriptions either, so the tool table's job column is inference from the names.prompts/list, so we cannot say whether the server serves any.Far more than its four tools suggest. One tool is a bare `mutate` verb and another is `query`, and WorkOS's own machine-readable docs index enumerates 28 API resource groups and 240 leaf operations behind them — organizations, users, SSO connections, directories, roles, MFA factors and audit logs. The tool count measures the dispatcher, not the surface it reaches.
It can reach deletes, but not silently. WorkOS's API reference documents 29 delete, revoke or deactivate operations, including deleting a user, an SSO connection and a directory. WorkOS states that irreversible operations are not run on first attempt: the agent is handed a description of what would be destroyed and must confirm explicitly before execution.
Only if you direct it there, and only if an admin allows it. WorkOS documents that the agent works against one environment at a time and defaults to sandbox, operating on production only when told to. A team-level Allow production access toggle can restrict MCP to sandbox entirely, and switching environments never escalates the account's existing access.
Your dashboard account, not a workspace-wide machine credential. WorkOS documents that the agent authenticates as you and assumes your exact dashboard role, with every operation running through the same access controls as the dashboard. A read-only role cannot make changes through the agent, and a non-admin cannot perform admin-only actions.
None that narrow access. Its RFC 9728 descriptor publishes `scopes_supported` as an explicitly empty array, verified live on 2026-08-19. The authorization server at `signin.workos.com` supports only `email`, `profile`, `openid` and `offline_access` — identity and refresh scopes. Nothing in the grant distinguishes read from write; that split lives in dashboard roles and admin toggles instead.
WorkOS documents four carve-outs. It cannot impersonate your end users, and mutations are blocked on impersonated sessions. It cannot change the MCP access settings governing itself, mint or rotate API keys, OAuth client secrets and signing certificates, or delete your WorkOS team. It is scoped to one team, and existing secret values are stripped from responses.
.md suffix; this is the documentation URL Anthropic's directory publishes. Source for role inheritance, environment scope, destructive confirmation, secret stripping, admin toggles, limitations and example prompts) · retrieved 2026-08-19workos.com/robots.txt is a bare Allow: / naming the sitemap, with no Content-Signal header on any axis (fetched 2026-08-19) · retrieved 2026-08-19…/oauth-protected-resource/mcp (both fetched 2026-08-19, byte-identical at 155 bytes, scopes_supported: []; the path-insert form returns 404) · retrieved 2026-08-19https://signin.workos.com) · retrieved 2026-08-19initialize POST to the endpoint returns HTTP 401 {"error":"unauthorized"} with www-authenticate: Bearer … resource_metadata="…/oauth-protected-resource/mcp". We did not authenticate and called no tool · retrieved 2026-08-19permissions field present, no prompt names listed) · retrieved 2026-08-16Connect WorkOS once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.