Discord Integration

Deploy your AI as a Discord bot that responds to slash commands, mentions, and direct messages.

March 22, 2026 | 1 min read

# integrations # discord # deployment # bot

Deploy your Chipp AI as a Discord bot. Users interact with your agent through slash commands, @mentions in server channels, and direct messages — bringing your AI directly into your community.

ℹ️

Discord integration requires a Builder plan or higher.

Upgrade to Builder →

What the Discord Bot Can Do

Slash commands — /ask with a question, /help for information
@mentions — @YourBot How can you help? in any server channel
Direct messages — Private conversations with the bot
Conversational memory — Maintains context within session timeouts
Knowledge base access — Uses your app’s knowledge sources for informed responses
Human takeover — Builders can take over conversations in real-time

Getting Started

1

Create a Discord Application

Visit the Discord Developer Portal and click New Application. Give it a name.

Go to the Bot section and click Add Bot
Click Reset Token to reveal your bot token (save it securely)
Enable Message Content Intent under Privileged Gateway Intents
Go to General Information and copy your Application ID and Public Key

2

Connect in Chipp

In your app’s settings, find the Discord configuration and paste:

Bot Token (from step 1)
Application ID (from step 1)
Public Key (from step 1)

Chipp will test the connection and register slash commands automatically.

3

Invite Bot to Your Server

Use the invite URL provided after connecting. Select the server(s) where you want the bot active. The bot receives permissions to send messages, embed links, read message history, and use slash commands.

4

Test It Out

Try these in your server:

Slash command: /ask What can you help me with?
Mention: @YourBot Tell me about your capabilities
Direct message: Send any message to the bot privately
Help: /help to see available commands

How Conversations Work

Session Management

The bot maintains conversation context within session timeouts:

Channel Type	Session Timeout	Scope
Server channels	30 minutes	Per user, per channel
Direct messages	60 minutes	Per user

After the timeout, a new conversation starts fresh. Your app’s knowledge sources provide persistent context across sessions.

Response Format

Responses are sent as Discord embeds with your app’s branding. Long responses (over 2,000 characters) are automatically split across multiple messages at natural breakpoints.

Slash Commands vs. Mentions

Method	How It Works	Best For
`/ask`	Deferred response (shows “thinking” status)	Structured queries
@mention	Real-time response via Gateway	Conversational flow
Direct message	Private 1:1 conversation	Sensitive topics

Configuration

The bot inherits your app’s full configuration:

LLM Model — Which AI model powers responses
System prompt — Custom personality and instructions
Knowledge sources — Documents and data the bot can reference
Custom tools — Any HTTP actions or integrations you’ve configured
Temperature — Creativity level for responses

No Discord-specific configuration is needed beyond the initial connection.

Billing

Discord uses your standard LLM token billing. There’s no separate per-message fee. Each bot response consumes tokens based on the model and conversation length.

Troubleshooting

Bot not responding to mentions?

Verify Message Content Intent is enabled in the Discord Developer Portal
Confirm the bot is installed in the server
Check the bot has permission to send messages in the channel
Test the connection via the settings panel

Slash commands not appearing?

Commands register globally and can take up to an hour to propagate
Try the command in a different channel or server

Long response times?

Slash commands show “thinking” status while processing
Complex queries with large knowledge bases take longer
Consider using a faster model for simpler use cases

Session history not persisting?

Sessions time out after 30 minutes (channels) or 60 minutes (DMs)
Start a new conversation by mentioning the bot or using /ask

ℹ️

MCP server access requires a Builder plan or higher. See the MCP Setup Guide to get started.