Discord MCP - Discord server management MCP for AI agents

Update server

update_server

Edits Discord server settings such as name, description, icon, banner, AFK behavior, channels, verification, media filter, and notifications; lowers protection only after confirmation.

Instructions

Edit server settings: name, description, icon, banner, invite background, AFK behavior, system and rules channels, verification level, explicit media filter, and default notifications. Images come from public URLs. Only passed fields change. Descriptions need a Community server; the banner and invite background need boosts. A lower verification level, a weaker media filter, or turning Community off lowers the server's protection, so that needs confirming: the first call changes nothing and returns a preview and a confirm_token, and repeating the call with the token makes the change. Raising them, and every other setting, happens at once.

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": "update_server"
  }
}

Input Schema

Name	Required	Description
`name`	No
`guild`	No	Guild (server) name or ID. Omit to use the default guild.
`dry_run`	No
`icon_url`	No	Public URL of the new server icon (png, jpeg, gif, webp), or none to remove it. A gif needs the animated icon feature.
`community`	No	Enable or disable the Community feature. Enabling needs rules_channel and public_updates_channel.
`banner_url`	No	Public URL of the banner shown at the top of the channel list, or none. Needs boost level 2.
`afk_channel`	No	Voice channel name or ID, or none to clear.
`description`	No
`confirm_token`	No	The token from this exact action's preview. Where the app can show a confirmation dialog, calling with it asks the user there, and it happens only if they agree.
`rules_channel`	No	Text channel for the rules, when enabling Community.
`system_channel`	No	Channel for join notices, or none to clear.
`verification_level`	No
`afk_timeout_seconds`	No
`default_notifications`	No	What new members are notified of by default.
`explicit_media_filter`	No	Which members' images Discord scans for explicit content.
`invite_background_url`	No	Public URL of the invite page background (the splash), or none. Needs boost level 1.
`public_updates_channel`	No	Text channel for Discord's mod updates, when enabling Community.
`discovery_background_url`	No	Public URL of the Server Discovery background, or none. Needs a discoverable server.

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 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"

addedInput schema / properties / banner_url

Added value: +{
+  "description": "Public URL of the banner shown at the top of the channel list, or none. Needs boost level 2.",
+  "type": "string"
+}

addedInput schema / properties / confirm_token

Added value: +{
+  "description": "The token from this exact action's preview. Where the app can show a confirmation dialog, calling with it asks the user there, and it happens only if they agree.",
+  "type": "string"
+}

addedInput schema / properties / default_notifications

Added value: +{
+  "description": "What new members are notified of by default.",
+  "enum": [
+    "all_messages",
+    "only_mentions"
+  ],
+  "type": "string"
+}

addedInput schema / properties / discovery_background_url

Added value: +{
+  "description": "Public URL of the Server Discovery background, or none. Needs a discoverable server.",
+  "type": "string"
+}

addedInput schema / properties / explicit_media_filter

Added value: +{
+  "description": "Which members' images Discord scans for explicit content.",
+  "enum": [
+    "off",
+    "members_without_roles",
+    "all_members"
+  ],
+  "type": "string"
+}

addedInput schema / properties / icon_url

Added value: +{
+  "description": "Public URL of the new server icon (png, jpeg, gif, webp), or none to remove it. A gif needs the animated icon feature.",
+  "type": "string"
+}

addedInput schema / properties / invite_background_url

Added value: +{
+  "description": "Public URL of the invite page background (the splash), or none. Needs boost level 1.",
+  "type": "string"
+}

Changed1 schema field changedv1.3.0Aug 12, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedv1.0.2Jun 14, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare readOnly=false and destructive=false; the description goes much further by disclosing partial-update semantics ("Only passed fields change"), a two-step preview/confirm_token protocol for protection-lowering changes, and the fact that all other changes apply immediately. The distinction between the first no-op preview call and the token-bearing call is exactly the behavioral detail an agent needs to avoid an accidental security downgrade.

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 field inventory is front-loaded and the risk/confirmation explanation follows in the right order. The closing sentence ("Raising them, and every other setting, happens at once") is grammatically awkward and slightly obscures the contrast between gated and immediate changes, which is the one bit of friction in an otherwise tight description.

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?

For an 18-parameter mutation tool with no output schema, the description covers everything an agent must know before calling: partial-update semantics, feature prerequisites, and the preview/confirm protocol. Nothing essential is left to inference from the schema alone.

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 coverage is 72%, so the schema carries most per-parameter meaning, but the description adds cross-field context the schema lacks: that images must be public URLs, that description requires Community, and which specific parameters trigger the confirmation flow. It stops short of mapping every one of the 18 parameters, so not a 5.

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 opens with a specific verb-and-resource pair ("Edit server settings") and enumerates the editable surface: name, description, icon, banner, invite background, AFK behavior, system/rules channels, verification level, media filter, notifications. That enumeration lets an agent separate it from sibling update tools like update_channel or update_role without opening a schema.

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?

It clearly states the preconditions that gate individual settings (Community required for descriptions, boost level for banner/invite background) and describes exactly when the confirmation path applies: lowering verification level, weakening the media filter, or turning Community off. It does not explicitly contrast with sibling tools, which keeps it below a 5.

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

Deploy Server