{"id":"reesavgupta-discord-mcp-server","name":"discord-mcp-server","homepage":null,"repo_url":"https://github.com/ReesavGupta/discord-mcp-server","category":"communication","subcategories":[],"tags":["mcp","discord","json-rpc-2.0","go","agent-tools","moderation","stdio-transport","authentication","moderation-tools"],"what_it_does":"A Model Context Protocol (MCP) server that lets MCP-compatible clients (e.g., Claude Desktop) interact with Discord via a JSON-RPC 2.0 interface over stdio. It supports Discord bot operations such as sending and retrieving messages, getting channel info, searching messages, and moderation actions, with configurable YAML + environment overrides and options for JWT/API-key authentication.","use_cases":["Automating Discord workflows from an MCP client","Building AI-assisted moderation actions (e.g., delete messages, kick/ban users) through tool calls","Searching and summarizing Discord message history","Channel-aware assistants that can fetch metadata and recent messages","Multi-bot / multi-guild orchestration via a single server"],"not_for":["Publicly exposing raw bot control endpoints without strong operational controls (least-privilege, network isolation)","Use cases requiring a documented, network-based HTTP API for third-party integrations (it is stdio-based MCP)","Production environments that require clearly documented operational reliability guarantees (no SLA/reliability evidence provided here)"],"best_when":"You need an MCP tool interface to interact with Discord from local/desktop or agent frameworks that support MCP over stdio, and you can secure bot credentials and authentication appropriately.","avoid_when":"You cannot securely manage secrets (bot tokens, JWT secret, API keys) or you require fine-grained, formally documented authorization semantics per action/tenant that are not described in the provided README.","alternatives":["Direct Discord bot implementation (discordgo) plus your own tool layer","Other MCP Discord integrations (if available) with clearer auth/authorization documentation","Webhook-based moderation/monitoring pipelines with a separate agent orchestration layer"],"af_score":55.0,"security_score":59.8,"reliability_score":30.0,"package_type":"mcp_server","discovery_source":["github"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T21:21:24.951139+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["JWT authentication","API key authentication"],"oauth":false,"scopes":false,"notes":"README states support for JWT and API keys and an optional audit logging flag, but does not describe scope model/granular permissions or how authorization is enforced per tool/action."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing information provided (appears to be a self-hosted open-source project)."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":55.0,"security_score":59.8,"reliability_score":30.0,"mcp_server_quality":78.0,"documentation_accuracy":55.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":55.0,"rate_limit_clarity":35.0,"tls_enforcement":60.0,"auth_strength":70.0,"scope_granularity":30.0,"dependency_hygiene":55.0,"secret_handling":80.0,"security_notes":"README includes security best practices (don’t commit secrets, use env vars, rotate API keys, enable audit logging, use strong JWT secrets, limit bot permissions). However, provided documentation does not clearly describe transport security for MCP stdio, token validation details, or fine-grained authorization/scope model per tool/action.","uptime_documented":0.0,"version_stability":45.0,"breaking_changes_history":40.0,"error_recovery":35.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Tooling operates through stdio MCP transport; ensure the MCP client/server process lifecycle is stable","Moderation actions (delete/kick/ban) are high-impact—agents should implement explicit confirmation/guardrails client-side","Auth mechanism details (JWT/API key validation specifics and per-tool authorization) are not fully documented in the provided README"]}}