Official MCP server for the Mux video API, built on a code-execution scheme: the agent writes TypeScript against the SDK and runs it in a Deno sandbox.
7 views
Summary
WorkOS's official remote MCP server — run your WorkOS dashboard from an agent: organizations, users, SSO connections, Directory Sync, AuthKit branding and audit log streams.
Features
- Manage organizations, users, SSO connections and Directory Sync
- Edit AuthKit branding and configure audit log streams
- Agent inherits your exact dashboard role — never more access than you have
- Environment-scoped and sandbox by default; production only on request
- Destructive operations require explicit confirmation after a described impact
- API keys and client secrets stripped from responses before reaching the model
- Team-level admin switches: enable, allow production, allow write
- OAuth over streamable HTTP; 15+ documented clients
Installation
Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.
Description
WorkOS MCP is a remote management server at https://mcp.workos.com/mcp that hands an AI agent the same WorkOS dashboard you use — organizations, users, SSO connections, Directory Sync, AuthKit branding, audit logs — and lets it call the WorkOS API on your behalf. Ask it to onboard a customer from a CSV, work out why org_123 cannot complete an SSO sign-in, or set up a Datadog audit log stream, and it works out which operations to run.
The permission model is the reason to look at it. The agent authenticates as you, over OAuth via WorkOS Connect, and inherits your exact dashboard role — a member without admin rights cannot use it to do admin-only things, and a read-only role cannot change anything. It is scoped to one environment at a time and defaults to sandbox, only touching production when you direct it there. Irreversible operations (deleting an organization, connection or directory) are never executed on the first attempt: the agent gets a description of exactly what would be destroyed and has to confirm. API keys, client secrets and signing certificates are stripped from responses before they reach the model's context, so a secret cannot leak into a chat transcript — though the agent can still set a value you supply.
Admin controls. Team admins get three independent switches in team authentication settings, all on by default: enable MCP at all, allow production access, and allow write access. Turning off write access makes the whole surface read-only for everyone.
Deliberate gaps. No user impersonation is exposed and mutations are blocked on impersonated sessions; the agent cannot change the MCP access settings that govern itself, mint or rotate credentials, or delete your WorkOS team; and it is scoped to the single team you authenticate with.
Clients. Streamable HTTP with OAuth, documented for Claude Code, Claude Desktop, ChatGPT (Pro, Business and Enterprise custom connectors), Cursor, VS Code, Zed, Windsurf, Codex CLI, Factory, Goose, OpenCode and Antigravity — 15+ in total, plus any other client that accepts a remote MCP URL.
Related MCP Servers
Red Hat's zero-dependency C++23 code-context engine — ranked call graphs and blast-radius analysis, indexing a repo in under half a second with no server and no database.
5 views
Builds a searchable markdown graph of your repo so coding agents stop re-exploring it on every task — reported 42% fewer tokens and 46% fewer tool calls.
6 views
Expo's official remote MCP server — searches Expo docs, installs compatible SDK packages, triggers and monitors EAS builds, and drives iOS/Android simulators.
6 views