How to Use the Clerk MCP in VS Code Copilot

Q: Can VS Code Copilot help debug Clerk webhook issues?

Yes, your agent can call listactivesessions to see if webhooks are firing on session creation. This helps your team trace authentication lifecycles without manual database queries.

Q: Can we query Clerk invitations in VS Code Copilot?

Yes, your team can use listsentinvitations to check pending invites. This is useful for verifying that your invitation pipelines are working during local testing.

Share Clerk user management and session auditing across your team in VS Code Copilot.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Clerk MCP to VS Code Copilot

Create your Vinkius account to connect Clerk to VS Code Copilot and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Clerk with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Monitor system health inside VS Code Copilot

The `get_auth_dashboard_summary` tool pulls live user counts and system health metrics directly into your VS Code Copilot chat. Your engineering team can check active signup rates and system loads without leaving their workspace. This gives you immediate context when debugging performance spikes or signup drops. If something looks off, you ask Copilot to pull more details, keeping your team aligned on system status during on-call rotations.

Audit active signups and allowlists as a team

The `list_auth_allowlist` tool allows your VS Code Copilot agent to inspect which domains are permitted to register on your platform. When a customer reports a registration issue, your team can query the active list directly from the editor. Copilot calls `list_sent_invitations` to check if an invitation was actually sent to the user. This keeps your support and engineering teams aligned on active signup issues without switching tools.

Inspect B2B tenants with VS Code Copilot MCP Server

The `list_clerk_organizations` tool provides your development team with a shared interface to inspect B2B account structures. Your team commits this configuration to the repository, giving everyone instant access to organization data. When debugging multi-tenant access, Copilot uses `list_clerk_users` to verify which developers belong to which organization. This shared context helps resolve permission bugs during team code reviews.

Setup guide

Set up Clerk MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the Clerk MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the Clerk tools listed. Try asking: "List my recent Clerk transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "clerk-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Clerk. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Clerk now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Clerk MCP in VS Code Copilot

You save the configuration in your repo's settings file. This lets every developer on your team use tools like `list_clerk_users` inside VS Code Copilot automatically configure this MCP Server.

Yes, your agent can call `list_active_sessions` to see if webhooks are firing on session creation. This helps your team trace authentication lifecycles without manual database queries.

You need VS Code version 1.96 or higher with Copilot set to Agent mode to communicate with the MCP Server. This allows the editor to run tools like `get_user_auth_details` during interactive chats.

Yes, your team can use `list_sent_invitations` to check pending invites. This is useful for verifying that your invitation pipelines are working during local testing.

The MCP Server runs within your local workspace sandbox, handling sensitive items like active session tokens and user email addresses locally. Your team's Clerk credentials and user records are never uploaded to external servers.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript