Skip to main content
Glama
pipeworx-io

mcp-discord

by pipeworx-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

mcp-discord

Discord MCP Pack

Part of Pipeworx — an MCP gateway connecting AI agents to 1573+ live data sources.

Tools

Tool

Description

get_me

Get the authorized Discord user's own identity (the connected account). Returns their user id, username, global display name, legacy discriminator, email, verified status, locale, and avatar hash. This is the user's own profile only — not other users or message content.

list_guilds

List the Discord servers (guilds) the authorized user is a member of. Returns each server's id, name, whether the user owns it, the user's permissions bitfield, the server's feature flags, and approximate member count. Covers only the user's own server memberships — it cannot read messages or non-member servers.

get_guild_member

Get the authorized Discord user's own membership details in a specific server (guild): their server nickname, role ids, join date, and Boost (premium) start date. Reads only the connected user's membership in that guild — not other members or message content.

list_connections

List the authorized Discord user's linked external accounts (connections) — e.g. Steam, Twitch, GitHub, YouTube, Spotify. Returns each connection's type, account id, display name, and verified status. Reads only the connected user's own linked accounts.

Related MCP server: Terros MCP Server

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "discord": {
      "url": "https://gateway.pipeworx.io/discord/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/discord/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1573+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "discord": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-discord"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-discord

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Discord data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

This server cannot be deployed

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • discord-user-mcp

    olivier-motium
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables interaction with Discord using personal user tokens instead of bot applications, allowing for seamless message management and server exploration. It provides tools for reading history, sending messages, and searching across channels and DMs directly through MCP-compatible clients.
    9
    MIT

  • poke_discord

    thesammykins
    F
    license
    Not graded
    quality
    C
    maintenance
    Enables interaction with Discord through natural language, including reading and sending messages, managing servers, and user actions.
    -