Discord Webhook MCP Server
Connect Discord Webhook to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Discord Webhook MCP Server. The discord webhook mcp server is what makes that connection.
Parameters: - content: Message content (required) - username: Display name (optional) - avatar_url: Avatar URL (optional)
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
content — Message content (required)username — Display name (optional)avatar_url — Avatar URL (optional)send_message — Parameters: - content: Message content (required) - username: Display name (optional) - avatar_url: Avatar URL (optional)Configuration is passed through the environment: DISCORD_WEBHOOK_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
@genpm/mcp-server-discord-webhook on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Discord Webhook's toolset — content, username, avatar_url and 1 more — is a fair guide to whether it matches your workflow. It is maintained by genm; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| content | Message content (required) |
| username | Display name (optional) |
| avatar_url | Avatar URL (optional) |
| send_message | Parameters: - content: Message content (required) - username: Display name (optional) - avatar_url: Avatar URL (optional) |
{
"mcpServers": {
"server-discord-webhook": {
"command": "npx",
"args": ["-y", "@genpm/mcp-server-discord-webhook"],
"env": {
"DISCORD_WEBHOOK_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| DISCORD_WEBHOOK_URL | Endpoint or connection string the server talks to. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.