WorkOS · VS Code (GitHub Copilot)

Add the WorkOS MCP server to VS Code (GitHub Copilot)

Manage WorkOS organizations, users, SSO, Directory Sync and AuthKit.

Official serverRemoteAuthentication

1. Add the server

Run in your terminal

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

2. Sign in

VS Code opens the sign-in flow when Copilot first calls a remote OAuth server. WorkOS is hosted by WorkOS, so there is nothing to install or keep updated.

3. Try it

Ask VS Code (GitHub Copilot) for something WorkOS can do. Manage WorkOS organizations, users, SSO, Directory Sync and AuthKit. Approve the first tool call and check the result before allowing write actions automatically.

  • · mcp.json uses a top-level servers key, not mcpServers.
  • · code --add-mcp installs a server into your user profile from the terminal.

FAQ

How do I add the WorkOS MCP server to VS Code (GitHub Copilot)?
Run: code --add-mcp '{"name":"workos","type":"http","url":"https://mcp.workos.com/mcp"}'. VS Code opens the sign-in flow when Copilot first calls a remote OAuth server.
Is this the official WorkOS MCP server?
Yes. It is published by WorkOS as com.workos/mcp in the official MCP registry.
Does the WorkOS MCP server need an API key?
It is a hosted server. Most hosted servers sign you in with OAuth the first time VS Code (GitHub Copilot) uses them; check WorkOS's docs for any plan or permission requirements.

Links

WorkOS in other clients

More authentication for VS Code (GitHub Copilot)

Work at WorkOS?

Feature WorkOS across the directory and its category from $49/month.

Feature this server

Reviewed Oct 5, 2026. Command generated from the registry record and checked against VS Code (GitHub Copilot)'s documented syntax.