Can I see how many users are currently logged in?

Yes! Use the `list_active_sessions` tool. The agent will return a list of all current sessions, allowing you to gauge real-time platform activity.

How do I check if a specific user belongs to an organization?

Use the `list_clerk_organizations` tool to find the organization and then review its members, or use `get_user_auth_details` to see the user's specific organization memberships.

Where do I find my Clerk Secret Key?

Log in to your Clerk Dashboard, select your application, and navigate to **API Keys**. You can find your Secret Key starting with `sk_` there.

Clerk MCP Server for CrewAI 8 tools — connect in under 2 minutes

Name: Clerk
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 8 Tools Framework

Connect your CrewAI agents to Clerk through the Vinkius — pass the Edge URL in the `mcps` parameter and every Clerk 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="Clerk Specialist",
    goal="Help users interact with Clerk effectively",
    backstory=(
        "You are an expert at leveraging Clerk 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 Clerk "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 8 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 Clerk MCP Server

Connect your Clerk account to any AI agent and take full control of your authentication and user management through natural conversation. Streamline how you monitor your user base and B2B organizations natively.

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

What you can do

User Oversight — List and retrieve details for all users in your application, including metadata and status natively
Session Intelligence — Access and monitor all active user sessions across your platforms flawlessly
Organization Logistics — List and manage B2B organizations and their member rosters securely
Invitation Tracking — Access and review all pending and completed user invitations flawlessly
Allowlist Management — List identifiers like emails and domains on your authentication allowlist flawlessly
Dashboard Visibility — Retrieve a high-level summary of user counts and system health directly within your workspace

The Clerk MCP Server exposes 8 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 Clerk to CrewAI via MCP

Follow these steps to integrate the Clerk 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 8 tools from Clerk

Why Use CrewAI with the Clerk MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Clerk 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 the 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

Clerk + CrewAI Use Cases

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

Automated multi-step research: a reconnaissance agent queries Clerk 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 Clerk, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Clerk 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 Clerk against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Clerk MCP Tools for CrewAI (8)

These 8 tools become available when you connect Clerk to CrewAI via MCP:

get_auth_dashboard_summary

Retrieve a summary of user counts and system health

get_user_auth_details

Get detailed information for a specific user

list_active_sessions

List all active user sessions

list_auth_allowlist

List identifiers (emails, domains) on the authentication allowlist

list_clerk_clients

List all tracking clients (browser/device instances)

list_clerk_organizations

List all organizations (B2B) in the application

list_clerk_users

List all users in your Clerk application

list_sent_invitations

List all pending and completed user invitations

Example Prompts for Clerk in CrewAI

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

"List all my users in Clerk."

"Show me the dashboard summary for my auth system."

"Check the status of invitation ID 'inv_12345'."

Troubleshooting Clerk MCP Server with CrewAI

Common issues when connecting Clerk 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

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

Clerk + CrewAI FAQ

Common questions about integrating Clerk 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.