Discord

Communication

Discord for AI agents. Managed auth, ready-made tools.

Read channels, post messages and start threads in the Discord servers your users connect.

About Discord

With the Discord connector, your agent reads and posts in the servers your users connect. It can summarize a channel, answer in a thread, post an announcement or react to a message, using only the tools your project allows.

Discord is a chat platform for communities, built around servers with text and voice channels.

Tools

What your agent can do in Discord.

Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Discord connection.

  • List servers

    Read
    discord_list_servers

    List the servers the user belongs to.

  • List channels

    Read
    discord_list_channels

    List the channels in a server.

  • Read a channel

    Read
    discord_get_messages

    Read recent messages in a channel.

  • Send a message

    Write
    discord_send_message

    Post a message in a channel, or reply to one.

  • Edit a message

    Write
    discord_edit_message

    Change a message the connection posted earlier.

  • Start a thread

    Write
    discord_create_thread

    Start a thread from a message or in a channel.

  • Add a reaction

    Write
    discord_add_reaction

    React to a message with an emoji.

Control

Limits you can set.

You decide what your agent may do in Discord, and Agent200 runs every call within those limits.

  • Turn single tools on or off

    Let the agent read channels and keep discord_send_message off until you want it to post.

  • Restrict what the agent reaches

    Choose the endpoints and scopes a project may use. A call outside them is refused.

Get started

Connect Discord
in three steps.

  1. 1

    Set up the SDK

    Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

    agent.js
    Conceptual example
    Set up the SDK with the Agent200 API key
    // One Agent200 API key covers every connector enabled for the project.
    const agent200 = new Agent200({
      apiKey: process.env.AGENT200_API_KEY,
    });
  2. 2

    Let your user connect Discord

    Each end user authorizes their own Discord account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

    connect.js
    Conceptual example
    Let an end user connect their account (managed OAuth)
    // Each end user authorizes their own Discord account, once.
    const connection = await agent200
      .user("user_123")
      .connect("discord");
    
    if (connection.authorizationUrl) {
      // Show this link to your user; Agent200 handles the rest.
      console.log(connection.authorizationUrl);
    }
  3. 3

    Run with the Discord tools

    Name the user, the model and the tools. The model decides which Discord tools to call, and Agent200 executes them with that user's connection.

    run.js
    Conceptual example
    Run a request with the connector's tools
    const result = await agent200
      .user("user_123")
      .run({
        model: "openai/gpt-5.6-sol",
        input: "What questions came up in #support today?",
        tools: ["discord"],
      });
    
    console.log(result.output);

Access

Sign-in and permissions.

  • Who signs in

    Each of your users, on Discord's own authorization page. To add the connection to a server, they need permission to manage that server. You never see their Discord password.

  • What access is requested

    Discord lists the requested scopes, such as reading the user's server list, and the permissions the connection gets in the server, such as reading and sending messages. Server admins can change or remove them in the server's Integrations settings.

For agents

Instructions for AI agents.

Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Discord connector and how to use it.

Agent brief
Connector: Discord, through Agent200. In code: "discord".
What it does: Read channels, post messages and start threads in the Discord servers your users connect.
Page: https://www.agent200.com/tools/discord/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Sign-in is managed OAuth. Each end user approves access once, on Discord's own page, through the authorization link Agent200 returns. Never ask a user for a Discord password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: discord_list_servers, discord_list_channels, discord_get_messages. Write tools: discord_send_message, discord_edit_message, discord_create_thread, discord_add_reaction. Name "discord" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/tools/discord/framework/claude/
   https://www.agent200.com/tools/discord/framework/chatgpt/
   https://www.agent200.com/tools/discord/framework/claude-code/
   https://www.agent200.com/tools/discord/framework/muse/
   https://www.agent200.com/tools/discord/framework/grok-bot/
   https://www.agent200.com/tools/discord/framework/openai-dots/
   https://www.agent200.com/tools/discord/framework/claude-duet/
   https://www.agent200.com/tools/discord/framework/hermes-agent/
   https://www.agent200.com/tools/discord/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

This page is also available as Markdown, for agents and LLMs: /tools/discord.md

Guides

Use Discord with the AI you build on.

Step-by-step setup for Discord with a specific model, assistant or agent framework.

FAQ

Discord and Agent200, answered.

Who handles the Discord OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Discord.

Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Discord connection, never another user's. It cannot reach anything the user or Discord has not authorized.

Can I limit what my agent can do in Discord?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

  • Slack

    Slack

    Search conversations and post messages in the workspaces your users connect.

    Managed OAuth Communication
  • Microsoft Teams

    Microsoft Teams

    Read channels and chats, post messages and set up meetings in Microsoft Teams on behalf of each of your users.

    Managed OAuth Communication
  • Zoom

    Zoom

    Schedule, update and review Zoom meetings and their cloud recordings on behalf of each of your users.

    Managed OAuth Communication
  • Telegram

    Telegram

    Send and receive messages, post in groups and channels, and share files through the Telegram bots your users connect.

    Managed OAuth Communication
200 OK

Start with Discord.
Your agent does the rest.

Your users connect their own Discord accounts. Agent200 handles the OAuth, the tokens and every tool call.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)