Discord

tawgroup4stars

Safe Discord administration MCP server for Codex and Claude

1# Discord

README.mdMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

Install from the publisher. Not a PlugMCP endpoint.

Run on PlugMCP

Host a copy with our keys and logs.

No packaged release in the registry yet. Follow the repository README.

RepositoryPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
License: MIT
Last checked: 2026-10-28

Stars: 4
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Discord?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Discord need an API key?

No required environment variable is listed on this record.

What transport does Discord use?

Discord runs locally over stdio.

When was Discord last checked?

Last checked 2026-10-28. Safe Discord administration MCP server for Codex and Claude

From the publisher

Documentation

Discord MCP

Discord administration MCP server for Codex, Claude Code, and other stdio MCP clients.

Tools

Discovery: servers, channels, members, roles, channel access
Messages: read, send, delete
Channels: create, rename, delete
Access: add/remove one member or all human members from a private channel
Roles: add/remove roles from members
Moderation: kick, ban, unban

Destructive tools require confirm: true. The server never returns the Discord token.

Setup

npm install
cp .env.example .env
npm start

The Discord application should enable Server Members Intent and Message Content Intent. Grant only the server permissions needed by the tools you intend to use.

One launcher for every harness

Create a tiny stdio launcher once, then point each client at it (absolute paths, so GUI apps with a minimal PATH can start it too):

# ~/.local/bin/discord-mcp
#!/bin/sh
export PATH="$HOME/.local/bin:/usr/local/bin:/opt/homebrew/bin:$PATH"
exec "$HOME/.local/bin/npm" --prefix "$HOME/discord-mcp" start --silent

Client	How
Claude Code	`claude mcp add --scope user discord -- ~/.local/bin/discord-mcp`
Codex CLI / app	`codex mcp add discord -- ~/.local/bin/discord-mcp` (writes `[mcp_servers.discord]` in `~/.codex/config.toml`)
Claude Desktop	`~/Library/Application Support/Claude/claude_desktop_config.json` → `"mcpServers": { "discord": { "command": "/Users/<you>/.local/bin/discord-mcp" } }`
Cursor / Windsurf / VS Code Copilot	same JSON shape in `~/.cursor/mcp.json`, `~/.codeium/windsurf/mcp_config.json`, `~/Library/Application Support/Code/User/mcp.json` (`"servers"` key for VS Code)
Gemini CLI	same JSON shape under `mcpServers` in `~/.gemini/settings.json`

Without the launcher, the raw command is npm --prefix /path/to/discord-mcp start --silent. --silent matters: plain npm start prints its > pkg start banner on stdout, which strict stdio clients (Oh My Pi, some others) read as a broken JSON-RPC frame and drop the transport (Transport closed). Claude Code and Codex happen to tolerate it.

Oh My Pi (omp) needs no entry of its own: it imports MCP servers from ~/.claude.json, ~/.codex/config.toml, Cursor, Gemini, Windsurf and VS Code configs automatically.

Discord

tawgroup4stars

Safe Discord administration MCP server for Codex and Claude

Communication

Install Run on PlugMCP

GitHub

Run on PlugMCP

1# Discord

README.mdMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

Install from the publisher. Not a PlugMCP endpoint.

Run on PlugMCP

Host a copy with our keys and logs.

No packaged release in the registry yet. Follow the repository README.

RepositoryPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
License: MIT
Last checked: 2026-10-28

Stars: 4
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Discord?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Discord need an API key?

No required environment variable is listed on this record.

What transport does Discord use?

Discord runs locally over stdio.

When was Discord last checked?

Last checked 2026-10-28. Safe Discord administration MCP server for Codex and Claude

From the publisher

Documentation

Discord MCP

Discord administration MCP server for Codex, Claude Code, and other stdio MCP clients.

Tools

Discovery: servers, channels, members, roles, channel access
Messages: read, send, delete
Channels: create, rename, delete
Access: add/remove one member or all human members from a private channel
Roles: add/remove roles from members
Moderation: kick, ban, unban

Destructive tools require confirm: true. The server never returns the Discord token.

Setup

npm install
cp .env.example .env
npm start

The Discord application should enable Server Members Intent and Message Content Intent. Grant only the server permissions needed by the tools you intend to use.

One launcher for every harness

Create a tiny stdio launcher once, then point each client at it (absolute paths, so GUI apps with a minimal PATH can start it too):

# ~/.local/bin/discord-mcp
#!/bin/sh
export PATH="$HOME/.local/bin:/usr/local/bin:/opt/homebrew/bin:$PATH"
exec "$HOME/.local/bin/npm" --prefix "$HOME/discord-mcp" start --silent

Client	How
Claude Code	`claude mcp add --scope user discord -- ~/.local/bin/discord-mcp`
Codex CLI / app	`codex mcp add discord -- ~/.local/bin/discord-mcp` (writes `[mcp_servers.discord]` in `~/.codex/config.toml`)
Claude Desktop	`~/Library/Application Support/Claude/claude_desktop_config.json` → `"mcpServers": { "discord": { "command": "/Users/<you>/.local/bin/discord-mcp" } }`
Cursor / Windsurf / VS Code Copilot	same JSON shape in `~/.cursor/mcp.json`, `~/.codeium/windsurf/mcp_config.json`, `~/Library/Application Support/Code/User/mcp.json` (`"servers"` key for VS Code)
Gemini CLI	same JSON shape under `mcpServers` in `~/.gemini/settings.json`

Oh My Pi (omp) needs no entry of its own: it imports MCP servers from ~/.claude.json, ~/.codex/config.toml, Cursor, Gemini, Windsurf and VS Code configs automatically.