Discord MCP - Discord server management MCP for AI agents

Run setup check

run_setup_check

Read-only

Check the Discord MCP setup end-to-end to diagnose token, intent, guild, cache, and confirmation problems, with fix instructions for any failed check.

Instructions

End-to-end health check of the discord-mcp setup: token presence and validity, privileged gateway intent toggles, Discord's growth thresholds (App Verification by servers, intent review by users), default guild membership, whether this install runs from npm's temporary npx cache, how destructive actions get confirmed in this app, and leftovers from before the 2.0 rename. Every failed check comes with instructions for fixing it. With more than one bot configured, pass bot to check a specific one. Run this first when anything misbehaves.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "run_setup_check"
  }
}

Input Schema

Name	Required	Description	Default
`bot`	No	Which bot to act as, by name, when more than one is configured. Omit to use the default bot, or with a server, the bot that handles it.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.4.2Nov 12, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedInput schema / properties / bot / description

Previous value: -"Which bot to act as, by name, when more than one is configured. Omit to use the default bot."New value: +"Which bot to act as, by name, when more than one is configured. Omit to use the default bot, or with a server, the bot that handles it."

Changed1 schema field changedv1.3.0Aug 12, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```

Changed3 schema fields changedv1.2.0Jul 15, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / bot

Added value: +{
+  "description": "Which bot to act as, by name, when more than one is configured. Omit to use the default bot.",
+  "type": "string"
+}

First observedv1.0.2Jun 14, 2026

TDQS

A4.1/5.0

Behavior4/5

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

readOnlyHint=true already signals a safe read operation, and the description adds meaningful behavior beyond that: every failed check returns fix instructions, it inspects install provenance (npx temp cache), and it flags legacy pre-2.0 artifacts. It does not describe the overall report structure or whether the check is fast/rate-limited, but the diagnostic contract is well disclosed.

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?

Purpose and the key behavior (fix instructions per failure) are front-loaded, and the long enumeration of checks is dense but each item is concrete. The check list could be trimmed slightly, though it earns most of its length by telling the agent what a result will contain.

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 zero-required-param read-only diagnostic with no output schema, the definition covers what is inspected, what a failure yields, and when to reach for it. A brief note on the shape of a passing report or runtime cost would make it fully self-sufficient.

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?

Only one optional parameter with 100% schema description coverage, so the schema already carries the meaning of 'bot'. The description's note that you pass bot when more than one is configured largely restates the schema, adding context but no new syntax or fallback nuance.

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?

Opens with a specific verb and object ('End-to-end health check of the discord-mcp setup') and then enumerates the concrete checks performed: token validity, privileged intents, growth thresholds, guild membership, npx cache install, confirmation flow, and pre-2.0 rename leftovers. Nothing about the tool's purpose is left to inference, and 'health check' is clearly distinct from any action-performing sibling.

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?

Gives a clear triggering condition — 'Run this first when anything misbehaves' — and a scoping rule for multi-bot installs. It does not name a specific alternative diagnostic tool or state when-not to run it, so it stops short of explicit alternatives, but the context for use is unambiguous.

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

Deploy Server