dynamic-discord-bot-api-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | debug, info, warn, error | info |
| DISCORD_BOT_TOKEN | No | Bot token; calls fail safely when absent | |
| DISCORD_SCHEMA_PATH | No | Alternate catalog path | |
| DISCORD_API_BASE_URL | No | Fixed API origin | https://discord.com/api/v10 |
| DISCORD_REQUEST_RETRIES | No | Retry count | 2 |
| DISCORD_LOCAL_FILE_ROOTS | No | Platform-delimited upload roots | |
| DISCORD_MAX_UPLOAD_BYTES | No | Per-file limit | 10485760 |
| DISCORD_RATE_LIMIT_BURST | No | Local burst | 50 |
| DISCORD_ENDPOINT_ALLOWLIST | No | Comma-separated IDs/operation IDs with * globs | * |
| DISCORD_REQUEST_TIMEOUT_MS | No | Per-attempt timeout | 30000 |
| DISCORD_SCHEMA_MAX_AGE_HOURS | No | Refresh threshold | 24 |
| DISCORD_RATE_LIMIT_PER_SECOND | No | Local global safety rate | 45 |
| DISCORD_ALLOW_UNKNOWN_PARAMETERS | No | Validation escape hatch | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| discord_search_endpointsA | Fuzzy-search cataloged Discord Bot HTTP API endpoints. |
| discord_get_endpointA | Return normalized schema for one Discord Bot endpoint. |
| discord_get_typeC | Return one normalized Discord OpenAPI component schema. |
| discord_call_endpointB | Validate and call one cataloged Discord Bot HTTP endpoint. |
| discord_refresh_schemaA | Fetch, validate, filter, and atomically install stable Discord Bot schema. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool serves a distinct function: searching, fetching endpoint schemas, fetching type schemas, calling endpoints, and refreshing the schema. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern with a discord_ prefix, using clear and uniform snake_case. The naming convention is uniform and predictable.
Five tools is an appropriate size for a focused Discord API schema management server. Each tool covers a core operation without unnecessary bloat or sparseness.
The tool set covers the full lifecycle: discovering endpoints, retrieving schemas, calling endpoints, and refreshing the local schema. No critical gaps are apparent for the server's intended purpose.