WorkOS MCP server
Manage your WorkOS workspace in plain language: orgs, users, SSO, Directory Sync, and AuthKit.
46 stars
Reviews
Write oneNobody has reviewed WorkOS yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
WorkOS tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.9 · 2026-09-20 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 70ms (auth required)20/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityOAuth resource metadata advertised on 40115/15
- Maintenancelast push 2 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year; website matches verified namespace10/10
What the publisher says
From the WorkOS repository's README, as published. We do not edit it. Read it on GitHub
@workos/skills
WorkOS skills for AI coding agents. Two skills and 40 reference files covering AuthKit, SSO, Directory Sync, RBAC, Vault, Migrations, backend SDKs, and more.
Install as Claude Code Plugin
npx skills add workos/skillsThis installs two skills: workos and workos-widgets. The workos skill acts as a router that automatically loads the right reference for your task (AuthKit setup, SSO, migrations, etc.) so you don't need to install references individually.
Works with Claude Code, Codex, Goose, and any agent that supports the skills.sh format.
Install as Cursor Plugin
Install from the Cursor Marketplace (search "WorkOS"), or clone and symlink locally — see Local Development below.
Install as npm Package
For programmatic access to skill/reference content (e.g., from the WorkOS CLI):
npm install @workos/skillsimport { getReference, getSkill } from '@workos/skills';
// Read reference content directly
const content = await getReference('workos-authkit-nextjs');
// Read a skill's SKILL.md content
const router = await getSkill('workos');Path helpers are also available for consumers that need file paths (e.g., skill discovery):
import { getReferencePath, getSkillsDir, getSkillPath } from '@workos/skills';
const refPath = getReferencePath('workos-authkit-nextjs'); // absolute path to .md file
const skillsDir = getSkillsDir(); // directory containing workos/ and workos-widgets/
const skillPath = getSkillPath('workos'); // absolute path to SKILL.mdExports
Skills
Two registered skills:
Everything else is a reference file under references/. The router dispatches to the right reference via progressive disclosure.
References
Note: References are not standalone skills. They are loaded automatically by the workos skill based on your task. You do not need to install them individually.
Full reference list (40+ files)
AuthKit Installation
Backend SDK Installation
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Install directly
claude mcp add --transport http mcp https://mcp.workos.com/mcp
WorkOS: common questions
- Is WorkOS MCP server safe?
- Yes, by our scan: it is graded A (100/100). Read the WorkOS safety report
- How do I install WorkOS?
- It runs remotely at mcp.workos.com. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does WorkOS need an API key?
- No key to paste: it signs you in with OAuth when your client connects.
- Is WorkOS maintained?
- The last commit was 2 days ago (2026-09-18). The latest release is v1.0.0.
- Is WorkOS up?
- 100% of our last 6 checks got an answer. We check remote servers about four times a day.