Skip to main content
Glama
enesjakozh
genm

MCP Server Discord Webhook

by genm
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

MCP Server Discord Webhook

An MCP server for posting messages to Discord webhooks.

日本語のREADME

Installation

npm install @genpm/mcp-server-discord-webhook

Related MCP server: MCP-Discord

Configuration

Add the following to your MCP configuration file:

{
  "mcpServers": {
    "discord-webhook": {
      "command": "npx",
      "args": [
        "-y",
        "@genpm/mcp-server-discord-webhook"
      ],
      "env": {
        "DISCORD_WEBHOOK_URL": "your-discord-webhook-url"
      },
      "alwaysAllow": [
        "send_message"
      ]
    }
  }
}

Features

send_message

Sends a message to Discord.

Parameters:

  • content: Message content (required)

  • username: Display name (optional)

  • avatar_url: Avatar URL (optional)

Example:

<use_mcp_tool>
<server_name>discord-webhook</server_name>
<tool_name>send_message</tool_name>
<arguments>
{
  "content": "Test message",
  "username": "Custom Name"
}
</arguments>
</use_mcp_tool>

Development

This project uses GitHub Actions for continuous integration and automated publishing to npm. When you push a new version tag (e.g., v1.0.0), it will automatically:

  1. Build the package

  2. Run tests

  3. Publish to npm

  4. Create a GitHub release

For more details about the release process, see CHANGELOG.md.

License

MIT

Author

genm

Available Tools

1 tool
send_messageC

Discordにメッセージを送信します

ParametersJSON Schema
NameRequiredDescriptionDefault
contentYes送信するメッセージ内容
usernameNo表示名（オプション）
avatar_urlNoアバターURL（オプション）

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions sending a message but fails to describe critical traits such as authentication requirements, rate limits, error handling, or what happens upon success (e.g., message ID returned). This leaves significant gaps for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence in Japanese that directly states the tool's function without any fluff or redundancy. It is appropriately sized and front-loaded, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral aspects like permissions, side effects, and return values, which are crucial for an agent to use the tool effectively in context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, documenting all three parameters clearly. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline for high schema coverage without compensating value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('send') and target resource ('message to Discord'), making the purpose immediately understandable. However, it doesn't differentiate from any siblings (though none exist) or specify what type of Discord message (e.g., to a channel, user, or webhook), which prevents a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives, prerequisites, or context for invocation. The description merely states what it does without indicating appropriate scenarios or constraints, leaving the agent with minimal usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev0.1.0
    • First observedsend_message
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.1/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'send_message' has a clear, distinct purpose that cannot be confused with any other tool in the set.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name 'send_message' follows a clear verb_noun pattern, and there are no other tools to create inconsistency.

Tool Count2/5

A single tool is too few for a Discord webhook server, which typically involves operations like sending messages, editing messages, deleting messages, or fetching webhook info. The scope feels incomplete with just one basic action.

Completeness2/5

The tool set is severely incomplete for a Discord webhook domain. It only provides 'send_message', missing essential operations like editing, deleting, or retrieving messages, and lacks any management functions for webhooks themselves.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/genm/mcp-server-discord-webhook'

If you have feedback or need assistance with the MCP directory API, please join our Discord server