2,500+ MCP servers ready to use
Vinkius

Clerk MCP Server for VS Code Copilot 8 tools — connect in under 2 minutes

Built by Vinkius GDPR 8 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Clerk and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "clerk": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Clerk
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.

GitHub Copilot Agent mode brings Clerk data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 8 tools — Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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 VS Code Copilot 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 VS Code Copilot via MCP

Follow these steps to integrate the Clerk MCP Server with VS Code Copilot.

01

Create MCP config

Create a .vscode/mcp.json file in your project root

02

Add the server config

Paste the JSON configuration above

03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

04

Start using Clerk

Ask Copilot: "Using Clerk, help me..."8 tools available

Why Use VS Code Copilot with the Clerk MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Clerk through the Model Context Protocol.

01

VS Code is used by over 70% of developers — adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Clerk + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Clerk MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Clerk MCP Tools for VS Code Copilot (8)

These 8 tools become available when you connect Clerk to VS Code Copilot via MCP:

01

get_auth_dashboard_summary

Retrieve a summary of user counts and system health

02

get_user_auth_details

Get detailed information for a specific user

03

list_active_sessions

List all active user sessions

04

list_auth_allowlist

List identifiers (emails, domains) on the authentication allowlist

05

list_clerk_clients

List all tracking clients (browser/device instances)

06

list_clerk_organizations

List all organizations (B2B) in the application

07

list_clerk_users

List all users in your Clerk application

08

list_sent_invitations

List all pending and completed user invitations

Example Prompts for Clerk in VS Code Copilot

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

01

"List all my users in Clerk."

02

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

03

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

Troubleshooting Clerk MCP Server with VS Code Copilot

Common issues when connecting Clerk to VS Code Copilot through the Vinkius, and how to resolve them.

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Clerk + VS Code Copilot FAQ

Common questions about integrating Clerk MCP Server with VS Code Copilot.

01

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
02

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
03

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
04

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.

Connect Clerk to VS Code Copilot

Get your token, paste the configuration, and start using 8 tools in under 2 minutes. No API key management needed.