WorkOS

MCP-Server von WorkOS

Manage WorkOS organizations, users, SSO connections, Directory Sync and AuthKit branding from your assistant.

OAuth-Anmeldung (Beim ersten Verbinden meldest du dich beim Anbieter an)Streamable HTTP

Mit WorkOS verbinden

WorkOS braucht eine Anmeldung. Verbinde dich mit seiner eigenen URL:

https://mcp.workos.com/mcp

Dein Client öffnet beim ersten Mal die Anmeldung von WorkOS. Das Token bleibt zwischen deinem Client und WorkOS.

Diesen Server teilen

Öffnet diese Seite, mit der URL und den Einrichtungsschritten.

mcp.tc/i/workos

Über den Server

Connects to the WorkOS API so an assistant can manage your WorkOS workspace. Operations cover organizations, users, SSO connections, Directory Sync, AuthKit branding, webhooks and feature flags. It can also help diagnose SSO sign-in problems for an organization.

This is a hosted Streamable HTTP server at https://mcp.workos.com/mcp. You sign in with OAuth 2.1 through a WorkOS consent screen, and no API keys are pasted. The server acts as your account, inherits your dashboard role, defaults to a sandbox environment, and asks for confirmation before destructive operations.

Was du damit machen kannst

  • Check your identity, role and reachable environments
  • List available WorkOS operations with their parameters
  • Run read-only queries such as listing organizations or users
  • Run write operations such as creating organizations or inviting users
  • Provision a WorkOS workspace for a first-time user
  • Inspect SSO connections and Directory Sync status
  • Adjust AuthKit sign-in branding

Tools

WorkOS zeigt seine Tools erst nach der Anmeldung, deshalb können wir sie hier nicht auflisten. Dein Client zeigt sie, sobald du verbunden bist.

Beispiel-Prompts

  • Invite bob@example.com to org_123 as an admin.

  • Help me understand why org_123 is having trouble signing in with SSO.

  • List every organization with a draft SSO connection.

  • Set up a new organization for Acme Corp in the sandbox environment.

Einrichtung

Jeder Client verbindet sich mit mcp.workos.com, und beim ersten Mal fragt WorkOS nach deiner Anmeldung. Wähl deinen; die Seite merkt sich deine Wahl.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport http workos https://mcp.workos.com/mcp
  1. Start Claude Code, type /mcp, pick workos and choose Authenticate. A browser window opens for the WorkOS sign-in.

Add --scope user to make it available in every project, not just this one.

Claude Desktop

  1. Open Settings → Connectors and click Add custom connector.
  2. Name it WorkOS and paste this URL:
https://mcp.workos.com/mcp
  1. Click Add, then Connect, and sign in when WorkOS asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

claude.ai

  1. Open the connector form on claude.ai. This button fills in the name and URL for you:
  1. Check that the URL reads https://mcp.workos.com/mcp and click Add.
  2. Click Connect and sign in when WorkOS asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.

ChatGPT

  1. On chatgpt.com, open Settings → Security and login and turn on Developer mode.
  2. Go to chatgpt.com/plugins and click + to create an app for a remote MCP server.
  3. Paste https://mcp.workos.com/mcp as the server URL and choose OAuth. ChatGPT sends you to WorkOS to sign in.

Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "workos": {
      "url": "https://mcp.workos.com/mcp"
    }
  }
}

Cursor shows Needs login next to the server. Click it to sign in.

VS Code

Or from a terminal:

code --add-mcp '{"name":"workos","type":"http","url":"https://mcp.workos.com/mcp"}'

Or commit it to the repo in .vscode/mcp.json:

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

VS Code asks you to sign in the first time the server starts.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "workos": {
      "serverUrl": "https://mcp.workos.com/mcp"
    }
  }
}
  1. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.

Codex

codex mcp add workos --url https://mcp.workos.com/mcp
codex mcp login workos

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.workos]
url = "https://mcp.workos.com/mcp"

Gemini CLI

gemini mcp add --transport http workos https://mcp.workos.com/mcp

Then, inside Gemini CLI, run /mcp auth workos to sign in.

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.

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

Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.

Client only starts local servers? Bridge it with npx -y mcp-remote https://mcp.workos.com/mcp.

Häufige Fragen

Can I paste mcp.tc/i/workos into my MCP client?

No. mcp.tc links are pages, not server addresses. Connect with https://mcp.workos.com/mcp, so your client talks to WorkOS directly. The sign-in token only works there anyway. The quick link is for sharing: it opens this page, with setup steps for every client.

Does WorkOS need an API key or a sign-in?

Yes, you need a WorkOS account. The first time your client connects, it opens WorkOS’s sign-in page. The token goes straight to the server’s own URL, never through mcp.tc.

Is WorkOS a remote or a local server?

Remote. WorkOS hosts it at https://mcp.workos.com/mcp, and it speaks Streamable HTTP. There’s nothing to install.

What can WorkOS do?

You can Check your identity, role and reachable environments, List available WorkOS operations with their parameters und Run read-only queries such as listing organizations or users.

Which clients can use it?

Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT in developer mode, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.

Who wrote this page?

mcp.tc’s robot read WorkOS’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

Einbinden

Zeig WorkOS in einem README oder auf deiner Website. Jede Einbindung verlinkt auf diese Seite, nutzt die eigene URL des Servers und setzt keine Cookies. So funktionieren Einbindungen

README-Badge

Badge-Vorschau, hellBadge-Vorschau, dunkel
Markdown
[![WorkOS on mcp.tc](https://mcp.tc/i/workos/badge.svg)](https://mcp.tc/i/workos)
HTML
<a href="https://mcp.tc/i/workos"><img src="https://mcp.tc/i/workos/badge.svg" alt="WorkOS on mcp.tc" height="20"></a>

Es folgt dem hellen oder dunklen Modus der Lesenden. Hänge ?theme=light oder ?theme=dark an, um ihn festzulegen, oder ?style=compact, um das Zeichen ohne Schriftzug zu zeigen.

Website-Karte

HTML
<script src="https://mcp.tc/w/workos.js" async></script>

Die Karte erscheint dort, wo das Tag steht. Füge dem Tag data-theme="dark" oder data-size="compact" hinzu, um sie zu ändern. Die Datei enthält alles, was sie braucht, stellt also keine weiteren Anfragen und setzt keine Cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/workos" title="WorkOS on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Nutze es auf Seiten, die keine Skripte erlauben. Hänge ?theme=light oder ?theme=dark an die Adresse an, um die Farben festzulegen.

JSON

Der Eintrag als Daten für deine eigenen Seiten und Tools: Name, Kurzbeschreibung, die eigene URL des Servers, Tools und die „Add to“-Links. Jede Website kann ihn lesen (CORS ist offen).

https://mcp.tc/i/workos.json

Was jedes Feld bedeutet

mcp.tc ist nicht mit WorkOS verbunden. Diese Seite entstand aus den öffentlichen Metadaten von WorkOS, zuletzt geprüft am 3. Okt. 2026, und ein KI-Modell hat die Beschreibung geschrieben, sie kann also Fehler enthalten. Namen und Marken gehören ihren Inhabern. Stimmt etwas nicht? Eintrag melden.