Discord Decision MCP

Overview Schema Related Servers Score Discussions

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v1.0.0
Disambiguation4/5
Most tools have distinct purposes, but discord_notify and discord_report_progress could be confused as both handle non-blocking notifications. The others clearly target different actions like asking decisions, checking pending items, reading/deleting messages, and clearing inboxes.
Naming Consistency5/5
All tools follow a consistent discord_verb_noun naming pattern with snake_case throughout. The naming is predictable and readable, making it easy to understand each tool's function at a glance.
Tool Count5/5
With 8 tools, this server is well-scoped for Discord interaction and decision management. Each tool serves a specific purpose in the workflow, from asking decisions to managing messages and notifications, without feeling bloated or sparse.
Completeness4/5
The toolset covers core Discord interaction needs well, including decision-making, message management, and notifications. A minor gap exists in message creation/sending tools, but the described domain focuses more on receiving and managing user input, which is adequately covered.
Average 3.8/5 across 8 of 8 tools scored. Lowest: 2.9/5.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 0 commits in the last 12 weeks
- No stable releases found
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI status not available
This repository is licensed under MIT License.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It mentions deletion behavior but lacks critical details: it doesn't specify if this is reversible, what permissions are required, or any rate limits. The description adds minimal context beyond the basic action, leaving significant behavioral gaps for a destructive operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is front-loaded with the core purpose, followed by structured Args and Returns sections. It avoids unnecessary fluff, but the Args section could be more integrated into the main description rather than a separate bullet. Overall, it's efficient and well-organized.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has one parameter with full schema coverage and an output schema, the description is minimally adequate. However, as a destructive tool with no annotations, it should provide more behavioral context (e.g., safety warnings, prerequisites). The output schema handles return values, but the description lacks completeness for informed usage.
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 schema description coverage is 100%, with the parameter 'read_only' fully documented in the schema. The description briefly mentions the parameter in the Args section, but adds no additional meaning or examples beyond what the schema already provides. This meets the baseline for high schema coverage.
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 ('메시지를 삭제한다' - deletes messages) and resource ('Discord inbox'), making the purpose immediately understandable. However, it does not explicitly differentiate from sibling tools like discord_delete_message or discord_delete_messages, which likely handle message deletion in different contexts or scopes.
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?
The description provides no guidance on when to use this tool versus alternatives. With sibling tools like discord_delete_message and discord_delete_messages, there is no indication of how this tool differs (e.g., clearing an entire inbox vs. specific messages), leaving the agent to guess based on naming alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It states the tool reports results to Discord but doesn't disclose behavioral traits like whether it's a read-only operation, if it requires specific permissions, rate limits, or what happens when thread_id is null. The description is minimal and lacks crucial operational context for a tool that interacts with an external service.
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 extremely concise with just two sentences in Korean, front-loaded with the core purpose followed by usage guidance. Every sentence earns its place with no wasted words, making it efficient and easy to parse.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given that an output schema exists (context signals indicate 'Has output schema: true'), the description doesn't need to explain return values. However, for a tool with no annotations and interaction with an external service like Discord, the description is too minimal—it lacks context on authentication, error handling, or integration specifics. It's adequate but has clear gaps in operational completeness.
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?
Schema description coverage is 100%, providing good documentation for all parameters (title, summary, details, thread_id). The description doesn't add any parameter-specific semantics beyond what the schema already explains, such as clarifying the format of details or when to use thread_id. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but also doesn't detract.
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 tool's purpose: '작업 완료 또는 단계 완료 시 결과를 Discord에 리포트한다' (Reports results to Discord when a task or step is completed). It specifies the verb '리포트한다' (reports) and the resource 'Discord', but doesn't explicitly differentiate from siblings like discord_notify or discord_ask_decision beyond a brief usage guideline.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context for when to use this tool: '결정 질문 없이 진행 상황만 공유할 때 사용한다' (Use when sharing progress without decision questions). This distinguishes it from discord_ask_decision (which likely involves questions) and implies it's for progress updates rather than notifications or inbox management, though it doesn't explicitly name alternatives or state when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses that the tool retrieves messages collected by a monitoring daemon and can return read/unread status. However, it doesn't mention behavioral aspects like rate limits, authentication requirements, potential side effects (e.g., marking messages as read via the mark_read parameter), or error handling. The description adds some context but lacks depth on operational traits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is appropriately sized with three sentences plus a Returns section. The first sentence states the purpose, the second provides context, and the third gives usage guidance. The Returns section is front-loaded but could be integrated more seamlessly. Minimal waste, though the structure slightly separates the output example.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's moderate complexity (2 parameters, no annotations, but with output schema), the description is fairly complete. It explains what the tool does, its source, and usage context. The output schema in the description details the return format, reducing the need for further explanation. However, it could better address behavioral aspects like side effects or prerequisites.
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?
Schema description coverage is 100%, with both parameters (unread_only, mark_read) well-documented in the schema. The description doesn't add any parameter-specific information beyond what's in the schema, so it meets the baseline of 3. No compensation is needed since schema coverage is complete.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: '조회한다' (retrieve/query) messages stored in the Discord inbox. It specifies the source ('감시 데몬(discord-watch)이 수집한 Discord 메시지') and distinguishes it from siblings by focusing on reading inbox messages rather than deleting (discord_delete_message), clearing (discord_clear_inbox), or notifying (discord_notify).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage context: 'Claude Code는 이 Tool을 호출하여 사용자가 Discord에서 보낸 메시지를 확인할 수 있습니다' (Claude Code can call this tool to check messages sent by the user on Discord). However, it doesn't explicitly state when to use this tool versus alternatives like discord_check_pending or provide exclusions. The guidance is present but not comprehensive.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden. It clearly discloses the destructive nature ('삭제된 메시지는 복구할 수 없습니다' - deleted messages cannot be recovered) and includes a warning symbol (⚠️). However, it doesn't mention authentication requirements, rate limits, error conditions, or what happens with insufficient permissions.
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?
Extremely concise with just two sentences - one stating the purpose, one providing critical warning. Every element earns its place, and the warning is appropriately highlighted with a symbol. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a destructive operation with 2 parameters, 100% schema coverage, and an output schema (though not shown), the description provides the essential warning about irreversibility. However, as a mutation tool with no annotations, it could benefit from mentioning authentication or permission requirements. The existence of an output schema means return values don't need explanation.
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?
Schema description coverage is 100%, so the schema already fully documents both parameters (channel_id and message_id). The description adds no additional parameter information beyond what's in the schema, meeting the baseline for high schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the specific action ('삭제한다' - deletes) and resource ('메시지' - message) in Discord. It directly distinguishes from sibling tools like discord_delete_messages (plural) by specifying single message deletion.
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 about when to use this tool versus alternatives like discord_delete_messages or other Discord operations. The description doesn't mention prerequisites, permissions needed, or contextual constraints beyond the warning about irreversibility.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden. It discloses a critical behavioral trait: '삭제된 메시지는 복구할 수 없습니다' (deleted messages cannot be recovered), which is essential for a destructive operation. However, it doesn't mention permissions, rate limits, or error conditions, leaving some gaps.
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 two sentences with zero waste: the first states the purpose, and the second provides a critical warning. It's appropriately sized and front-loaded, with every sentence earning its place by adding essential information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (destructive bulk operation), no annotations, and an output schema (which handles return values), the description is fairly complete. It covers the irreversible nature of deletion, but could improve by addressing permissions or error handling. The output schema reduces the need to explain returns.
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?
Schema description coverage is 100%, so the schema already documents both parameters thoroughly. The description adds no additional meaning about parameters beyond what's in the schema (e.g., no extra context on channel_id or message_ids). Baseline 3 is appropriate as the schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('일괄 삭제한다' - bulk delete) and resource ('Discord에서 여러 메시지' - multiple messages in Discord). It distinguishes from sibling 'discord_delete_message' (singular) by specifying bulk deletion, making the purpose specific and differentiated.
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?
The description provides no guidance on when to use this tool versus alternatives like 'discord_delete_message' (for single messages) or 'discord_clear_inbox' (which might clear messages differently). It lacks explicit when/when-not instructions or named alternatives, offering only basic functional context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/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 adds valuable context beyond the schema: it specifies the tool is '논블로킹' (non-blocking), indicating it won't block execution while sending notifications. It also clarifies the tool's purpose is for notifications 'that don't require decisions,' which helps understand its scope. However, it doesn't mention authentication needs, rate limits, or error behavior.
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 extremely concise and well-structured. Two short sentences efficiently communicate the tool's purpose and usage guidelines. Every word earns its place, with no redundant information. The Korean language doesn't affect conciseness scoring.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has an output schema (which means return values are documented elsewhere), no annotations, and 100% schema coverage, the description provides good contextual completeness. It covers purpose, key behavioral trait (non-blocking), and usage guidelines. For a notification tool with structured documentation elsewhere, this is reasonably complete, though it could mention more about error handling or performance characteristics.
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 schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema. It mentions general use cases but doesn't explain parameter meanings or relationships. With complete schema coverage, the baseline score of 3 is appropriate.
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 tool's purpose: '진행 상황을 Discord에 알린다 (논블로킹)' translates to 'Notify progress to Discord (non-blocking).' It specifies the action (notify), target (Discord), and a key behavioral trait (non-blocking). However, it doesn't explicitly differentiate from siblings like discord_report_progress, which might have overlapping functionality.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context for when to use the tool: '결정이 필요 없는 상태 업데이트, 경고, 완료 알림에 사용한다' translates to 'Use for status updates, warnings, and completion notifications that don't require decisions.' This gives good guidance on appropriate use cases. It doesn't explicitly mention when NOT to use it or name alternatives like discord_ask_decision for decision-related notifications.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It describes the tool's purpose and workflow implications, but doesn't disclose behavioral traits like whether it's read-only, authentication needs, rate limits, or error conditions. The description adds context about session timing and mandatory processing, but lacks operational details.
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 efficiently structured with two sentences: one stating the purpose and timing, another establishing the workflow requirement. The return format is clearly documented in a separate section. Every sentence earns its place with no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has 0 parameters, an output schema, and no annotations, the description provides good contextual completeness. It explains when to use the tool and what happens with pending questions. The output schema handles return values, so the description appropriately focuses on purpose and workflow rather than output details.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has 0 parameters with 100% schema description coverage, so the baseline is 4. The description doesn't need to explain parameters, and it appropriately focuses on the tool's purpose and usage instead.
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 tool's purpose: to check for unresolved pending questions at session start. It specifies the verb 'check' and resource 'pending questions', though it doesn't explicitly differentiate from sibling tools like 'discord_read_inbox' or 'discord_clear_inbox' which might handle similar concepts.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit usage guidelines: '세션 시작 시' (at session start) and 'pending이 있으면 반드시 처리 후 새 작업을 시작해야 한다' (if pending exists, must process before starting new work). This clearly defines when to use it and establishes a workflow requirement.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden. It discloses key behavioral traits: blocking behavior ('블로킹 대기'), timeout handling with defaults, and response format details in the Returns section. However, it doesn't mention authentication needs, rate limits, error conditions, or what happens if the thread_id is invalid. It adds useful context but leaves some behavioral aspects unspecified.
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 efficiently structured: a clear purpose statement followed by bullet points explaining key parameters and a Returns section. Every sentence earns its place—no redundant information. It's appropriately sized for a tool with 5 parameters and complex blocking behavior.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (blocking wait, multiple parameters, interaction with Discord), the description is complete. With 100% schema coverage and an output schema provided (the Returns section), the description doesn't need to explain parameter details or return values. It focuses on the higher-level purpose, behavioral context, and usage guidelines, which is exactly what's needed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents all 5 parameters thoroughly. The description adds meaningful semantic context beyond the schema: it explains that timeout_seconds=None means infinite wait (recommended), clarifies options=[] enables free-text response while options=[...] provides choices, and recommends A/B/C format for options. This provides valuable usage guidance that complements the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: '사용자의 결정이 필요할 때 Discord Thread에 질문을 전송하고 응답이 올 때까지 블로킹 대기한다' (sends a question to a Discord Thread when user decision is needed and blocks waiting for response). It specifies the exact action (send question to Discord Thread), resource (Discord Thread), and distinguishes from siblings like discord_notify (notification) or discord_report_progress (progress reporting).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context for when to use this tool: '사용자의 결정이 필요할 때' (when user decision is needed). It implies this is for interactive decision-making scenarios, but doesn't explicitly state when NOT to use it or name alternatives among sibling tools (e.g., discord_notify for one-way notifications). The guidance is helpful but lacks explicit exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![discord-decision-mcp MCP server](https://glama.ai/mcp/servers/yarang/discord-decision-mcp/badges/card.svg)](https://glama.ai/mcp/servers/yarang/discord-decision-mcp)

Score Badge

Copy to your README.md:

[![discord-decision-mcp MCP server](https://glama.ai/mcp/servers/yarang/discord-decision-mcp/badges/score.svg)](https://glama.ai/mcp/servers/yarang/discord-decision-mcp)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/yarang/discord-decision-mcp'

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