WorkOS MCP server for Claude, Codex and Cursor

What your AI apps can do with WorkOS

• Inspect organizations and users
• Review SSO and directory settings

WorkOS MCP tools

Toolstile hasn't inspected the WorkOS server yet. Its tool list appears on this page after the server is inspected. Once you connect, Toolstile lists the tools the server reports, and you choose which ones each app may call.

Suggested access for each AI app

Coding agent in Claude Code or Cursor. Allow the read tools so the agent can look things up without stopping, and require approval for tools that change shared data.

Chat or research app in Claude Desktop. Allow reading and searching. Allow writes only where you want the app to act for you.

Unattended agent, such as a scheduled Codex job. No one is watching the session, so keep it narrow: allow what the job needs, require approval for changes and block the rest.

Blocked tools are removed from the tool list an app sees, so it won't try them. Because rules apply per app, the same WorkOS connection can be broad in one app and read-only in another, and the credential stays in Toolstile instead of each app's config file.

How it works with Toolstile

1. Connect once. Add WorkOS to a workspace (browser sign-in). Toolstile keeps the credential, so no agent config holds it.
2. Choose access per app. Give Claude Code every WorkOS tool, give Cursor only the read tools, or keep WorkOS away from an app entirely.
3. Share approved accounts. Teammates use the connection without copying tokens, and you can remove access in one place.
4. Review activity. See which app called which tool and when, so you can tighten access with evidence.

Add the WorkOS MCP server to an AI app

Through Toolstile, every AI app uses one gateway entry, whichever servers you connect. In Claude Code:

claude mcp add --transport http toolstile 'https://toolstile.com/mcp'

Then connect WorkOS in your workspace and choose which of its tools that app may use. Client setup covers Codex, Cursor and Claude Desktop.

To connect directly instead, add the WorkOS endpoint to each app separately. In Claude Code:

claude mcp add --transport http workos 'https://mcp.workos.com/mcp'

In Cursor's mcp.json:

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

Some servers accept only clients they have approved, or need a token header. Check the WorkOS MCP documentation for what your client needs.

Before you connect

A WorkOS account. Sign-in uses your WorkOS permissions.

Server details

WorkOS MCP documentation