W
WorkOS
Manage WorkOS directories and SSO.
·No reviews yet
Share:
About
Auto-generated
WorkOS is a Model Context Protocol server in the Developer Tools category. It lets AI assistants that speak MCP call its tools and read its resources over STDIO.
Example tools
Illustrative tool names — the actual tool set is defined by the server at runtime.
list_resources
Enumerate resources exposed by this MCP
get_resource
Fetch a resource by ID
invoke
Invoke the primary action of this MCP
Screenshots
No screenshots yet.
Frequently Asked Questions
Common questions about WorkOS.
- What is the WorkOS MCP and what does it manage?
- The WorkOS MCP provides a standardized interface for interacting with WorkOS. It enables managing WorkOS directories and Single Sign-On (SSO) configurations, streamlining integration for various developer tools and platforms.
- How do I install the WorkOS MCP in an MCP client like Cursor?
- The WorkOS MCP can be installed in Cursor by configuring its stdio transport via the client's extension or plugin management interface. Typically, this involves specifying the path to the WorkOS MCP executable downloaded from its GitHub repository.
- Does the WorkOS MCP require an API key for authentication?
- Yes, the WorkOS MCP uses an API key for authentication. This key must be obtained from your WorkOS account and provided during the MCP configuration to access and manage your WorkOS resources securely.
- What are the primary capabilities exposed by the WorkOS MCP?
- The WorkOS MCP primarily exposes capabilities related to managing enterprise features like Directory Sync and SSO. This includes programmatic access to user and group provisioning, as well as configuring identity provider connections.
- Is there any cost associated with using the WorkOS MCP?
- The WorkOS MCP itself is open-source and community-provided, implying no direct cost for its usage. However, the underlying WorkOS service may involve costs based on its pricing model, which typically depends on usage and features.
- What is a common prerequisite for using the WorkOS MCP?
- A common prerequisite for using the WorkOS MCP is a pre-existing WorkOS account and configured WorkOS environment. You must have access to API keys and relevant WorkOS resource identifiers to effectively utilize the MCP's functionalities.
Install WorkOS
Claude Desktop
Add this to claude_desktop_config.json.
{
"mcpServers": {
"workos": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-workos"
]
}
}
}Cursor
Add this to ~/.cursor/mcp.json.
{
"mcpServers": {
"workos": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-workos"
]
}
}
}VS Code
Add this to your workspace settings.json.
{
"mcp.servers": {
"workos": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-workos"
]
}
}
}Reviews
Sign in to leave a review.
No reviews yet. Be the first!
Discussion(0)
No comments yet.