How to connect Discord to Grok Bot
Connect Discord to Grok Bot with ClawLink in one click — 27 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.
DiscordOAUTH2MCPSend messages, manage channels, and automate server actions. Once connected, Grok Bot can read and act on Discord from chat — pairing, token refresh, and tool wiring handled for you.
Grok Bot runs on its own cloud computer, so most Discord guides send you to register an OAuth app and paste keys into a sandbox that resets. ClawLink gives Grok Bot a more practical Discord setup: it runs one CLI command, you approve once in the browser, and Grok Bot can call real Discord actions from chat with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into Grok Bot. It runs the ClawLink CLI in its own terminal and pairs your account.
Set up ClawLink for me and tell me when it's ready.
1. Pair this machine. It prints an approval link, so show me the link and stop, don't wait:
npx -y @useclawlink/cli login
2. I'll approve it in my browser, then reply "approved".
3. When I say approved, connect the app:
npx -y @useclawlink/cli connect discord
4. Then run `npx -y @useclawlink/cli whoami` and tell me whether ClawLink is ready.Setup
It takes three steps to connect Grok Bot to Discord.
1Pair from the terminal
Ask Grok Bot to run the ClawLink CLI. It prints a link you approve once in your browser:
npx -y @useclawlink/cli login- 2
Connect Discord
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask Grok Bot: "What can you do with Discord?"
Install by command
The prompt above does all of this. By hand, it is two commands Grok Bot runs in its own terminal, and one browser approval:
npx -y @useclawlink/cli login # prints an approval link, approve it in your browser
npx -y @useclawlink/cli connect discordPair once and it sticks: the key is written to ~/.clawlink/credentials.json inside Grok Bot's sandbox, so it survives between sessions. Prefer native tools over shell commands? Add https://claw-link.dev/api/mcp as a custom connector at grok.com/connectors and approve the ClawLink sign-in. Same account, no CLI.
Verify the connection by asking Grok Bot:
Use Discord to consume entitlement and walk me through the result in plain English.
Using a different agent?
The CLI above is not specific to Grok Bot. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account the same way:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Discord is connected in the dashboard, that agent calls the same 27 Discord tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Discord MCP for Grok Bot
Looking for a Discord MCP server for Grok Bot? ClawLink connects Discord to Grok Bot and exposes 27 Discord tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using a different agent? The OpenClaw Discord integration and the Hermes Discord integration connect the same ClawLink account the same way.
What the Grok Bot Discord integration can do
27 Discord tools are ready for Grok Bot once the account is connected. The 25 below are the ones people reach for most; your agent can call all 27.
25 of 27 Discord tools for Grok Bot
| Tool | What it does |
|---|---|
Consume entitlement discord_consume_entitlement | Marks a one-time purchase consumable entitlement as consumed for a given application. Only applicable to entitlements backed by one-time purchase consumable SKUs. |
Edit application command permissions discord_edit_application_command_permissions | Edits the permissions for a specific application command in a guild. Requires OAuth2 Bearer token (bot tokens will error). |
Get application command permissions discord_get_application_command_permissions | Retrieves the permissions for a specific application command in a guild. Requires OAuth2 Bearer token (bot tokens will error). |
Get batch application command permissions discord_get_batch_application_command_permissions | Retrieves permissions for all commands of an application in a guild. Returns a list of permission objects for each command. Requires OAuth2 Bearer token (Bot tokens will error). |
Get current user application entitlements discord_get_current_user_application_entitlements | Tool to retrieve entitlements for the current user for a given application. Use when you need to check what premium offerings or subscriptions the authenticated user has access to. |
Get gateway discord_get_gateway | Tool to retrieve a valid WebSocket (wss) URL for establishing a Gateway connection to Discord. Use when you need to connect to the Discord Gateway for real-time events. |
Get guild template discord_get_guild_template | Tool to retrieve information about a Discord guild template using its unique template code. Use when you need to get details about a guild template for creating new servers. |
Get guild widget discord_get_guild_widget | Tool to retrieve the guild widget in JSON format. Use when you need to get public information about a Discord guild's widget that can be displayed on external websites. |
Get guild widget png discord_get_guild_widget_png | Tool to retrieve a PNG image widget for a Discord guild. Use when you need a visual representation of the guild widget that can be displayed on external websites. |
Get my guild member discord_get_my_guild_member | Retrieves the guild member object for the currently authenticated user within a specified guild, including roles, nickname, join date, and permissions. |
Get my oauth2 authorization discord_get_my_oauth2_authorization | Retrieves current OAuth2 authorization details for the application, including app info, scopes |
Get my user discord_get_my_user | Fetches comprehensive profile information for the currently authenticated Discord user |
Get openid connect userinfo discord_get_openid_connect_userinfo | Retrieve OpenID Connect compliant user information for the authenticated user |
Get public keys discord_get_public_keys | Retrieve Discord OAuth2 public keys |
Get sku subscription discord_get_sku_subscription | Retrieves a specific subscription by ID for a given SKU |
Get user discord_get_user | Retrieve information about a Discord user |
Get user application role connection discord_get_user_application_role_connection | Retrieves the application role connection for the currently authenticated user for a specified |
Invite resolve discord_invite_resolve | Resolve and retrieve information about a Discord invite code |
List my connections discord_list_my_connections | Retrieves a list of the authenticated user's connected third-party accounts on Discord |
List my guilds discord_list_my_guilds | Lists the current user's guilds, returning partial data for each; primarily used for displaying |
List sku subscriptions discord_list_sku_subscriptions | Lists all subscriptions for a given SKU |
List sticker packs discord_list_sticker_packs | Retrieve all available Discord Nitro sticker packs |
Modify current user discord_modify_current_user | Modifies the currently authenticated Discord user's profile |
Update user application role connection discord_update_user_application_role_connection | Updates the application role connection for the currently authenticated user for a specified |
Leave guild discord_leave_guild | Leaves a Discord guild (server) on behalf of the currently authenticated user |
Try it: find the Discord tool you need
Browse the 25 Discord tools
Click any tool to see exactly what Grok Bot can do and copy a ready-to-use prompt.
Example prompts
Use Discord to consume entitlement and walk me through the result in plain English.
Use Discord to edit application command permissions and walk me through the result in plain English.
Pull the relevant data from Discord, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Discord, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want Discord working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a Discord app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Discord through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Discord. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Discord actions to the runtime in a format your agent can reliably use. | 27 tools for Discord are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Discord to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Grok Bot users instead. You install the plugin once, connect Discord in the browser, and the 27 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
Grok Bot says it cannot add ClawLink as an MCP server
Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run npx -y @useclawlink/cli login in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add https://claw-link.dev/api/mcp as a custom connector at grok.com/connectors and approve the ClawLink sign-in.
Connection succeeds but no tools appear
Reconnect Discord from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Discord tools
Discord tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Discord call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Discord returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
OAuth finished in the browser but the account is still missing
Try reconnecting Discord and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.
FAQ
Is there a Grok Bot Discord integration?
Yes. ClawLink is the fastest way to connect Grok Bot to Discord: link your Discord account once in the browser and Grok Bot can call the Discord API through 27 ready-made tools — no custom code or token handling.
How do I connect Discord to Grok Bot with ClawLink?
Ask Grok Bot to run npx -y @useclawlink/cli login in its terminal and approve the link it prints, then npx -y @useclawlink/cli connect discord to authorize Discord. Grok Bot calls the tools from the next message, and the pairing persists in its sandbox, so this is a one-time step: no config files or API keys to manage.
How long does it take to connect Discord to Grok Bot?
About two minutes. Sign in, click Connect next to Discord in the dashboard, authenticate, and Grok Bot can use it from the next chat message.
Why use ClawLink instead of wiring Discord up myself?
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want Discord working from chat.
Grok Bot says it cannot add ClawLink as an MCP server
Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run npx -y @useclawlink/cli login in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add https://claw-link.dev/api/mcp as a custom connector at grok.com/connectors and approve the ClawLink sign-in.
