Discord Vencord MCP Bridge

Model Context Protocol (MCP) server for Discord user sessions. Enables Claude Desktop, Antigravity, Cursor, and any MCP-compatible AI agent to interact with Discord directly through your native desktop client.

Why This Exists

Traditional Discord MCP tools require providing a Bot Token or extracting your User Token.

• Bot Tokens cannot send messages in DMs without mutual servers or read your private chats.

• User Tokens in external scripts frequently trigger Cloudflare challenges, phone locks, and account flags due to TLS fingerprint mismatch (JA3/TLS, WebSockets heartbeat, super-properties).

This project routes all actions natively through your active Discord client via a local Vencord userplugin.

• Zero Account Flagging: Runs inside your authentic Discord Electron runtime.

• No Tokens in Config Files: Authenticates automatically using your client's existing session.

• 30+ Tools: Read channels, send replies, react, list DMs, manage servers, kick/ban, and manage roles.

Related MCP server: discord-mcp-server

Architecture

[ AI Assistant (Claude Desktop / Antigravity / Cursor) ]
                         │ (stdio)
                         ▼
        [ Node.js MCP Server (This Repo) ]
        [ WebSocket Server: 127.0.0.1:49152 ]
                         │ (Local WebSocket JSON Bridge)
                         ▼
       [ Vencord UserPlugin (MCPBridge) ]
       [ Inside Discord Desktop (Renderer Context) ]
                         │ (Discord Internal Webpack Stores & RestAPI)
                         ▼
                [ Discord Gateway ]

Quick Start Guide

Step 1: Clone and Build the MCP Server

git clone https://github.com/clawdecode/discord-vencord-mcp.git
cd discord-vencord-mcp
npm install
npm run build

Step 2: Install the Vencord Plugin

1. Ensure you have the Vencord Dev Build (or clone Vencord):

   git clone https://github.com/Vendicated/Vencord.git
   cd Vencord
   pnpm install

2. Copy the plugin file from this repository into Vencord's userplugins directory:

   mkdir src\userplugins\mcpBridge
   copy "path\to\discord-vencord-mcp\vencord-plugin\index.tsx" "src\userplugins\mcpBridge\index.tsx"

3. Build and inject into Discord:

   pnpm build
   pnpm inject

4. Open Discord and verify MCPBridge is visible under User Settings -> Vencord -> Plugins (tagged with the USERPLUGIN badge) and enabled. Press Ctrl + R to reload.

Step 3: Register in Your MCP Client

Add the server to your client configuration file:

Antigravity (~/.gemini/config/mcp_config.json)

{
  "mcpServers": {
    "discord-bridge": {
      "command": "node",
      "args": [
        "C:/path/to/discord-vencord-mcp/dist/mcp-server/index.js"
      ]
    }
  }
}

Claude Desktop (%APPDATA%/Claude/claude_desktop_config.json)

{
  "mcpServers": {
    "discord-bridge": {
      "command": "node",
      "args": [
        "C:/path/to/discord-vencord-mcp/dist/mcp-server/index.js"
      ]
    }
  }
}

Cursor (.cursor/mcp.json)

{
  "mcpServers": {
    "discord-bridge": {
      "command": "node",
      "args": [
        "C:/path/to/discord-vencord-mcp/dist/mcp-server/index.js"
      ]
    }
  }
}

Complete Tools Reference

Identity and Private Messages

Messaging and Reactions

Navigation and UI Control

Server and Channel Administration

Roles and Permissions

Moderation and Invites

Security and Privacy

1. Local-Only Communication: The WebSocket bridge binds strictly to loopback (127.0.0.1:49152) and never accepts outside network connections.

2. Permission Parity: The tools operate under your user account's actual Discord permissions. It cannot bypass server role hierarchies or access channels your account cannot see.

3. No External Telemetry: All data flows exclusively between your local AI agent, the local MCP process, and your local Discord client.

License

Released under the MIT License.