Discord Mcp

Created By
SaseQa year ago
A MCP server for the Discord integration. Enable your AI assistants to seamlessly interact with Discord. Enhance your Discord experience with powerful automation capabilities.
Overview

What is Discord MCP?

Discord MCP is a Model Context Protocol (MCP) server designed for seamless integration of Discord bots with MCP-compatible applications like Claude Desktop.

How to use Discord MCP?

To use Discord MCP, clone the repository from GitHub, build the project using Maven, and configure it with your Discord bot token. You can also install it automatically via Smithery.

Key features of Discord MCP?

  • Integration with Discord API (JDA) for bot functionality
  • Message management tools for sending messages to channels and users
  • Easy setup and configuration for developers

Use cases of Discord MCP?

  1. Creating interactive Discord bots that utilize AI capabilities.
  2. Managing messages and interactions within Discord channels.
  3. Integrating with applications like Claude Desktop for enhanced functionality.

FAQ from Discord MCP?

  • What is the purpose of Discord MCP?

It allows developers to create Discord bots that can interact with MCP-compatible applications.

  • How do I get a Discord bot token?

You can obtain a Discord bot token by visiting the Discord Developer Portal.

  • Is there documentation available?

Yes, detailed examples and documentation can be found in the project's Wiki on GitHub.

Server Config

{
  "mcpServers": {
    "discord-mcp": {
      "command": "java",
      "args": [
        "-jar",
        "/absolute/path/to/discord-mcp-0.0.1-SNAPSHOT.jar"
      ],
      "env": {
        "DISCORD_TOKEN": "YOUR_DISCORD_BOT_TOKEN",
        "DISCORD_GUILD_ID": "OPTIONAL_DEFAULT_SERVER_ID"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
10 months ago
Author Name
SaseQ
Star
22
Language
Java
License
MIT license
Category
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago