Discord MCP

io.github.cappyeoPublished by GitHub account cappyeov0.32.1Updated Oct 24, 2026

Caller-owned Discord operations for AI agents with 222 typed tools and verifiable guild builds.

VerifiedSTDIODesktop onlyCommunication & Collaboration

Overview

AI-generated overview

A local MCP server that gives an AI assistant 222 typed tools for caller-owned Discord operations, with verifiable guild builds.

What you can do
Run Discord operations through 222 typed tools, grouped by the Discord objects they act on, such as guilds, channels, messages and members, as described in the registry entry. Build and verify guild structures against the guilds the deployment is allowed to operate on. Bind the deployment to a specific bot identity so startup fails if the token belongs to another bot.
When to use it
Use it when an assistant should perform Discord server administration or messaging tasks on servers you own, and you want a broad typed tool surface rather than a few ad hoc commands.
Requirements
Runs as a local process over stdio, installed from the npm package. Needs a Discord bot token in DISCORD_TOKEN (an optional Bot prefix is accepted), the expected bot ID in DISCORD_EXPECTED_BOT_ID, and a comma-separated list of guild IDs in ALLOWED_GUILDS. Desktop only.
Before you install
The bot token in DISCORD_TOKEN is a secret granting the bot's Discord permissions; keep it out of logs and shared configs. The tools can change Discord data, so scope ALLOWED_GUILDS tightly and review write actions before running them. The manifest lists no tools, so confirm the exact operations before installing.

Installation

In SourceWeft

  1. Open Discord MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

6
  1. v0.32.1LatestOct 19, 2026
  2. v0.32.0Oct 14, 2026
  3. v0.31.1Oct 2, 2026
  4. v0.31.0Oct 1, 2026
  5. v0.30.0Sep 30, 2026
  6. v0.28.0Sep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.