WorkOS

com.workosPublished by workos.comOfficial publisherv1.0.0Updated Oct 24, 2026

Manage your WorkOS workspace in plain language: orgs, users, SSO, Directory Sync, and AuthKit.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring Business & Commerce

Server details

Identifier: com.workos/mcp
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to workos.com, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/com.workos%2Fmcp.svg)](https://sourceweft.com/mcp/com.workos%2Fmcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Remote WorkOS MCP server that lets an assistant manage organizations, users, SSO, Directory Sync and AuthKit in your WorkOS workspace.

What you can do: Check identity, role and reachable environments, and list the WorkOS operations available to the agent
Run read-only operations such as listing organizations, users, SSO connections or directories
Run write operations such as creating an organization, inviting a user, or configuring SSO and AuthKit branding
Provision a WorkOS workspace for a first-time user
Work across organizations, users, SSO, Directory Sync, AuthKit branding, webhooks and feature flags
When to use it: Useful when you administer a WorkOS workspace and want an assistant to inspect or change organizations, users, SSO connections, directories or AuthKit branding in plain language, including troubleshooting sign-in problems.
Requirements: A remote MCP client pointed at the hosted WorkOS endpoint over Streamable HTTP. OAuth 2.1 sign-in with Dynamic Client Registration through a WorkOS consent screen; no API key to paste. A WorkOS account and team, and a client that supports remote MCP servers.

Before you install

The agent acts as your WorkOS account and inherits your dashboard role, so write operations change real workspace data; it defaults to a sandbox environment but can touch production when told. Irreversible operations such as deleting an organization, connection or directory require an explicit confirmation step. Credentials such as API keys and client secrets are stripped from responses. Team admins can disable MCP access, block production access, or make it read-only.

Installation

In SourceWeft

Open WorkOS in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.workos%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "workos": {
      "type": "http",
      "url": "https://mcp.workos.com/mcp"
    }
  }
}

README

WorkOS MCP Server

Manage your WorkOS workspace with AI agents. The WorkOS MCP server is a remote Model Context Protocol server. Any MCP client can use it to manage organizations, users, SSO connections, directories, branding, and more, by calling the WorkOS API on your behalf.

Server URL: https://mcp.workos.com/mcp
Transport: Streamable HTTP
Auth: OAuth 2.1 with Dynamic Client Registration (WorkOS Connect). No API keys to paste.
Docs: https://workos.com/docs/mcp

This folder holds the registry metadata (server.json) for the server. The server runs as a hosted service at WorkOS. Its source is not published here. The rest of this repository holds WorkOS skills for AI coding agents.

The server acts as you. It inherits your WorkOS dashboard role and can only do what your account can do.

Connect a client

The first time you connect, your client opens a WorkOS consent screen. Sign in and approve access. After that the agent is connected as your account.

WorkOS CLI (Claude Code, Codex, Cursor)

The CLI detects installed clients. Use --agent claude-code, --agent codex, or --agent cursor to target one. workos mcp status shows what is installed and signed in.

GitHub Copilot / VS Code

Add the server to .vscode/mcp.json:

json

{  "servers": {    "workos": {      "type": "http",      "url": "https://mcp.workos.com/mcp"    }  }}

{  "servers": {    "workos": {      "type": "http",      "url": "https://mcp.workos.com/mcp"    }  }}

Start the server from the mcp.json editor, or run MCP: List Servers from the Command Palette.

Claude Code

Use /mcp inside Claude Code to check status or sign in again.

Cursor

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project):

Open Settings → MCP and click Login next to WorkOS.

Codex CLI

Claude Desktop, ChatGPT

Open Settings → Connectors, click Add custom connector, name it WorkOS, and enter https://mcp.workos.com/mcp.

Other clients

Add a remote MCP server with the URL https://mcp.workos.com/mcp. Setup steps for Antigravity, Factory, Goose, OpenCode, Windsurf, and Zed are in the docs.

Tools

Tool	What it does
`whoami`	Returns your identity, role, and the environments you can reach.
`list_operations`	Lists the WorkOS operations available to the agent, with parameters.
`query`	Runs a read-only operation from the catalog, such as listing organizations or users.
`mutate`	Runs a write operation from the catalog, such as creating an organization or inviting a user.
`setup_account`	Provisions a WorkOS workspace for a first-time user.

Operations cover organizations, users, SSO connections, Directory Sync, AuthKit branding, webhooks, feature flags, and more.

Example prompts

"Set up a new organization for Acme Corp and invite everyone in acme_employees.csv."
"Help me understand why org_123 is having trouble signing in with SSO."
"Invite [email protected] to org_123 as an admin."
"List every organization with a draft SSO connection, and flag any directories that haven't synced in 24 hours."
"Here's a screenshot of our marketing site. Make our AuthKit sign-in page match it."
"Set up a Datadog audit log stream for our production environment."

Permissions and safety

Role inheritance. The agent runs every operation through the same access controls as the dashboard. A read-only role cannot make changes.
Environment scope. The agent works in one environment at a time. It defaults to a sandbox environment and only touches production when you say so.
Destructive confirmation. Irreversible operations, such as deleting an organization, connection, or directory, return a description of what will be destroyed and require an explicit confirmation step before they run.
Secrets. API keys, client secrets, and similar values are stripped from responses before they reach the agent.
Admin controls. Team admins can disable MCP access, block production access, or make MCP read-only for the whole team from the team authentication settings.

Limitations

No user impersonation.
The most sensitive dashboard actions are not exposed: changing MCP access settings, minting or rotating credentials, and deleting your WorkOS team.
One team at a time. The agent is scoped to the team you authenticate with.

Support

Listings

server.json here is the source of truth for the com.workos/mcp entry in the MCP Registry. Other directories are tracked in LISTINGS.md.

Source: mcp/README.md at commit d56befc

Tools

This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

v1.0.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts