Can I check the sync status of a specific company directory through the agent?

Yes. The `get_directory_details` tool allows your AI agent to retrieve the current sync status and metadata for any specific directory ID, helping you monitor whether employees are being correctly provisioned.

How do I see which users belong to a specific synced group?

You can use the `list_directory_users` tool and filter by the directory ID to see the full roster. For group-level information, use the `list_directory_groups` tool to see organizational units imported from the identity provider.

Is it possible to retrieve security audit logs via chat?

Absolutely. The `get_audit_log_events` tool retrieves a stream of events for any specific organization ID, giving you instant access to compliance-related activities directly through your conversation.

WorkOS MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: WorkOS
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to WorkOS through Vinkius, pass the Edge URL in the `mcps` parameter and every WorkOS tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="WorkOS Specialist",
    goal="Help users interact with WorkOS effectively",
    backstory=(
        "You are an expert at leveraging WorkOS tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in WorkOS "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About WorkOS MCP Server

Connect your WorkOS account to any AI agent and manage your enterprise identity infrastructure through natural conversation.

When paired with CrewAI, WorkOS becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call WorkOS tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Organization Management — Browse and list all enterprise organizations (tenants), create new records, and manage authorized domains
SSO Monitoring — List and audit active Single Sign-On (SSO) connections (SAML, OIDC) configured for your enterprise customers
Directory Sync — Monitor active HRIS and SCIM directory instances and retrieve deep details on sync status and provider types
Roster Management — Retrieve the complete list of users and organizational groups synced from external directories directly from your agent
Audit Compliance — Stream and retrieve audit log events for any organization to monitor security and compliance activities
Tenant Insights — Quickly find unique organization, connection, and directory IDs required for enterprise feature configuration
Connectivity Health — Verify the status and metadata of SSO links and directory connections to ensure uptime

The WorkOS MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect WorkOS to CrewAI via MCP

Follow these steps to integrate the WorkOS MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from WorkOS

Why Use CrewAI with the WorkOS MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with WorkOS through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

WorkOS + CrewAI Use Cases

Practical scenarios where CrewAI combined with the WorkOS MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries WorkOS for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries WorkOS, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain WorkOS tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries WorkOS against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

WorkOS MCP Tools for CrewAI (10)

These 10 tools become available when you connect WorkOS to CrewAI via MCP:

create_workos_organization

Provide the name and a list of authorized domains. Creates a new organization record

get_audit_log_events

Returns a stream of events tracked in the organization. Retrieves audit log events for an organization

get_directory_details

g. Okta, Azure AD) of a directory ID. Retrieves metadata for a specific directory instance

get_organization_details

Retrieves details for a specific organization

get_sso_connection_details

Retrieves details for a specific SSO connection

list_directories

Lists all active Directory Sync instances

list_directory_groups

Lists all groups synced from a directory

list_directory_users

Lists all users synced from a directory

list_sso_connections

Lists all active SSO connections

list_workos_organizations

Lists all organizations in the WorkOS account

Example Prompts for WorkOS in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with WorkOS immediately.

"List all organizations in my WorkOS account."

"Check the status of SSO connections for 'Acme Corp'."

"List all users synced from the directory 'dir_01J...'."

Troubleshooting WorkOS MCP Server with CrewAI

Common issues when connecting WorkOS to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

WorkOS + CrewAI FAQ

Common questions about integrating WorkOS MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.