Discord Bot MCP integration for AI agents.
Connect AI agents to Discord Bot through 15 structured actions, including get application, create message, delete message, and test auth. Review authenticati…
- ACTION CONTRACTS
- 15
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Discord Bot integration exposes
The Discord Bot Agent App exposes 15 provider-backed actions for communication and developer tools work. Its current contract lets an authorized agent get a discord application by id, create a discord message in a channel, and delete a discord message from a channel. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Discord Bot account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Discord Bot capabilities.
Showing 12 of 15 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_applicationREADGet a Discord application by ID.
INPUTS: application_id
create_messageWRITECreate a Discord message in a channel.
INPUTS: channel_id / content / embeds / components / allowed_mentions
delete_messageHIGH IMPACTDelete a Discord message from a channel.
INPUTS: channel_id / message_id
test_authREVIEWCheck whether the configured Discord bot token can call the current application endpoint.
get_bot_gatewayREADGet the recommended Discord Gateway URL and sharding metadata for the bot.
get_channelREADGet a Discord channel by ID.
INPUTS: channel_id
get_gatewayREADGet the public Discord Gateway URL.
get_guildREADGet a Discord guild by ID.
INPUTS: guild_id
get_guild_widget_pngREADGet a Discord guild widget PNG.
INPUTS: guild_id / style
get_my_applicationREADGet the Discord application associated with the configured bot token.
get_public_keysREADGet Discord OAuth2 public keys.
get_userREADGet a Discord user by ID.
INPUTS: user_id
INPUT CONTRACTS
Know what the action needs before it runs.
get_application
application_idREQUIRED- A Discord snowflake identifier.
create_message
channel_idREQUIRED- A Discord snowflake identifier.
contentOPTIONAL- The message content.
embedsOPTIONAL- The embeds to include.
componentsOPTIONAL- The components to include.
allowed_mentionsOPTIONAL- A raw Discord API object.
delete_message
channel_idREQUIRED- A Discord snowflake identifier.
message_idREQUIRED- A Discord snowflake identifier.
get_channel
channel_idREQUIRED- A Discord snowflake identifier.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Application
Get a Discord application by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_applicationControl Create Message
Create a Discord message in a channel. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_messageVerify with Get Bot Gateway
Get the recommended Discord Gateway URL and sharding metadata for the bot. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_bot_gatewaySAFETY BOUNDARY
Operate Discord Bot with explicit limits
- Authorize Discord Bot with API key and grant only the provider access required by the selected actions.
- 2 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_message` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Discord Bot rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Discord Bot task completed successfully.
CONNECTION MODEL
API key
Discord bot token sent as Authorization: Bot <token>. Create a bot in the Discord Developer Portal and invite it to the guilds you want to manage.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 12
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Discord Bot.