> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tess.im/llms.txt
> Use this file to discover all available pages before exploring further.

# Discord

The **Discord** connector integrates Tess with Discord. Once connected, the AI can help read accessible channels, summarize community discussions, and support messaging workflows inside chats and agents.

Discord is part of the Tess [Connectors](/en/connectors) ecosystem and uses **OAuth** authentication for Apps connectors.

## Prerequisites

<Info>
  * A Discord account with access to the servers/channels you need.
  * Permission to authorize the Discord app for those servers.
</Info>

## How to connect

<Tip>
  On some Apps connectors, the OAuth consent screen may show a third-party connection bridge name rather than Tess. That is normal—review the requested permissions and continue if they match what you expect.
</Tip>

<Steps>
  <Step title="Open the Connectors panel">
    In chat, click the **+** next to the message box and select **Connectors**. You can also manage connectors while editing an agent in Agent Studio.

    <Frame>
      <img src="https://mintlify.s3.us-west-1.amazonaws.com/tess-dfe1edf0/images/connectors/discord/01-connect-panel.png" alt="PRINT: (Connectors panel with Discord highlighted and the Connect button visible)" />
    </Frame>
  </Step>

  <Step title="Find Discord and click Connect">
    Under **Apps**, locate **Discord** and click **Connect** to start authentication.

    <Frame>
      <img src="https://mintlify.s3.us-west-1.amazonaws.com/tess-dfe1edf0/images/connectors/discord/02-oauth-consent.png" alt="PRINT: (Provider authorization / consent screen for Discord)" />
    </Frame>
  </Step>

  <Step title="Authorize access">
    Sign in with the account you want to use and review the requested permissions before confirming.
  </Step>

  <Step title="Confirm it is active">
    Back in Tess, **Discord** should appear under **Connected**, ready for chats and agents.

    <Frame>
      <img src="https://mintlify.s3.us-west-1.amazonaws.com/tess-dfe1edf0/images/connectors/discord/03-connected.png" alt="PRINT: (Tess callback or Connectors list showing Discord as Connected with a success state)" />
    </Frame>
  </Step>
</Steps>

## What you can do

* **Find channels and recent messages** the account can access
* **Summarize community discussions** into decisions and action items
* **Support moderation and community ops** with clearer context
* **Help draft or send updates** when write permissions are available
* **Keep community signal close to your Tess workflows**

## Example prompts

> 1. Summarize the last day of discussion in #product-feedback and list top requests.
> 2. What announcements were posted this week in the community server?
> 3. Draft a release update for #announcements and show it before sending.
> 4. Find messages mentioning onboarding friction and group them by theme.

## Best practices

* Mention the server/channel when names collide.
* Ask for a draft before posting to public channels.
* In agents, define whether Discord is for listening, summarization, or posting.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Missing server access" icon="circle-question">
    Reconnect with an account that belongs to the target server and has the needed channel permissions.
  </Accordion>

  <Accordion title="401 / connection dropped" icon="circle-question">
    Reconnect Discord in Connectors after app removal or token revocation.
  </Accordion>

  <Accordion title="Cannot post to a channel" icon="circle-question">
    The connected account may be read-only there. Check Discord roles/permissions.
  </Accordion>
</AccordionGroup>

<Note>
  Tess uses the permissions of the connected account. It does not expand access beyond what that account can already do.

  Connectors involve access to external systems. Only connect accounts that fit the usage context, and review permissions carefully.
</Note>