Can AI agents automate WorkOS?

WorkOS is automatable today through the REST API. The API is organized around REST at https://api.workos.com, accepts and returns JSON, and authenticates with a secret API key as Authorization Bearer. Keys are prefixed with sk_. Official backend SDKs are listed for Node.js, Python, Go, PHP, Ruby, Java, .NET, Rust, and Elixir. First-party management MCP is hosted at https://mcp.workos.com/mcp over Streamable HTTP with WorkOS Connect OAuth. The agent inherits the dashboard user's role. Admins can disable MCP, block production, or force read-only. The server cannot mint or rotate API keys, change its own MCP admin controls, impersonate users, or delete the team. AuthKit for MCP, which secures other people's MCP servers, is outside this product boundary. The official CLI is a standalone binary with --json output and commands that manage organizations, users, connections, and the MCP install. Webhook endpoints are created at /webhook_endpoints and include a signing secret. This record excludes Auth0, Okta, Stytch, and FusionAuth. Connector catalogs were not opened. Computer-use viability is unassessed. API, MCP, and CLI all score 8; API is the best path because it is not subject to the MCP admin kill-switch or CLI login session.

Best path today: api · Overall automatability: 8/10