# How to connect Discord Bot to Grok Bot (no API keys) > Connect Discord Bot to Grok Bot with ClawLink in one click — 165 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/grokbot/discord-bot Grok Bot runs on its own cloud computer, so most Discord Bot guides send you to register an OAuth app and paste keys into a sandbox that resets. ClawLink gives Grok Bot a more practical Discord Bot setup: it runs one CLI command, you approve once in the browser, and Grok Bot can call real Discord Bot actions from chat with no auth, token refresh, or tool wiring to build yourself. **Start here — paste this into Grok Bot to set up ClawLink:** > 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-bot` > 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 Bot. 1. **Pair from the terminal** — ask Grok Bot to run `npx -y @useclawlink/cli login` and approve the link it prints. 2. **Connect Discord Bot** — `npx -y @useclawlink/cli connect discord-bot`, then approve in the browser. 3. **Use it from chat** — ask Grok Bot in plain English. **The same CLI works from any agent with shell access:** ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect discord-bot # connect Discord Bot (browser OAuth) npx -y @useclawlink/cli actions discord-bot # list available actions npx -y @useclawlink/cli run discord-bot --input '' # execute (add --confirm for writes) ``` ### 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: ```bash npx -y @useclawlink/cli login # prints an approval link, approve it in your browser npx -y @useclawlink/cli connect discord-bot ``` Pair 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 Bot to discordbot get active guild threads 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Discord Bot is connected in the dashboard, that agent calls the same 165 Discord Bot tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Discord Bot MCP for Grok Bot Looking for a Discord Bot MCP server for Grok Bot? ClawLink connects Discord Bot to Grok Bot and exposes 165 Discord Bot tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using a different agent? The [OpenClaw Discord Bot integration](https://claw-link.dev/openclaw/discord-bot) and the [Hermes Discord Bot integration](https://claw-link.dev/hermes/discord-bot) connect the same ClawLink account the same way. ## What the Grok Bot Discord Bot integration can do 165 Discord Bot tools are ready for Grok Bot once the account is connected. The 30 below are the ones people reach for most; your agent can call all 165. ### 30 of 165 Discord Bot tools for Grok Bot | Tool | What it does | |---|---| | **Get active guild threads** `discordbot_get_active_guild_threads` | Retrieves all active (non-archived) threads in a Discord guild that the bot can access | | **Get application** `discordbot_get_application` | Retrieves the full details of a Discord application by its application_id | | **Get application command** `discordbot_get_application_command` | Retrieves a specific global application command by its application ID and command ID | | **Get application role connections metadata** `discordbot_get_application_role_connections_metadata` | Retrieves all role connection metadata records for a Discord application | | **Get application user role connection** `discordbot_get_application_user_role_connection` | Fetches the role connection object for the current user for a specified Discord application | | **Get auto moderation rule** `discordbot_get_auto_moderation_rule` | Retrieves the complete configuration of a specific auto moderation rule within a Discord guild | | **Get bot gateway** `discordbot_get_bot_gateway` | Retrieves the WSS URL, recommended shard count, and session start limits for connecting a bot | | **Get channel** `discordbot_get_channel` | Retrieves detailed metadata for a specific Discord channel by its channel_id | | **Get gateway** `discordbot_get_gateway` | Retrieves the WebSocket URL to connect to Discord's Gateway for receiving real-time events | | **Get guild** `discordbot_get_guild` | Retrieves detailed information for a specified Discord guild (server) by its guild_id | | **Get guild application command** `discordbot_get_guild_application_command` | Retrieves detailed information for a specific application command within a Discord guild | | **Get guild application command permissions** `discordbot_get_guild_application_command_permissions` | Retrieves the permissions for a specific application command within a guild | | **Get guild ban** `discordbot_get_guild_ban` | Fetches the ban details for a specific user in a Discord guild, if that user is currently banned | | **Get guild emoji** `discordbot_get_guild_emoji` | Retrieves details for a specific custom emoji within a specified Discord guild, requiring valid | | **Get guild member** `discordbot_get_guild_member` | Retrieves detailed information for a specific member of a Discord guild, provided the bot | | **Get guild preview** `discordbot_get_guild_preview` | Fetches a public preview of a Discord guild by its ID, if the guild has the preview feature | | **Get guild scheduled event** `discordbot_get_guild_scheduled_event` | Retrieves a specific scheduled event from a Discord guild by its ID, optionally including the | | **Get guild sticker** `discordbot_get_guild_sticker` | Retrieves a specific sticker from a Discord guild using the guild and sticker IDs; requires the | | **Get guild template** `discordbot_get_guild_template` | Retrieves the complete structure and details of a Discord guild template using its unique code | | **Get guild vanity URL** `discordbot_get_guild_vanity_url` | Retrieves the vanity URL invite code and usage count for a Discord guild | | **Get guild webhooks** `discordbot_get_guild_webhooks` | Retrieves all webhooks for a specified Discord guild, requiring MANAGE_WEBHOOKS permission | | **Get guild welcome screen** `discordbot_get_guild_welcome_screen` | Retrieves the welcome screen configuration for a Discord guild with the Community feature | | **Get guild widget** `discordbot_get_guild_widget` | Retrieves the public JSON widget data for a Discord guild, if the widget is enabled for that | | **Get guild widget png** `discordbot_get_guild_widget_png` | Retrieve a PNG image widget for a Discord guild | | **Get guild widget settings** `discordbot_get_guild_widget_settings` | Retrieves the widget settings for a specified Discord guild, indicating if the widget is | | **Get guilds onboarding** `discordbot_get_guilds_onboarding` | Retrieves the onboarding settings for a specified Discord guild, including prompts, options | | **Get message** `discordbot_get_message` | Retrieves a specific message from a Discord channel by channel and message ID | | **Get my application** `discordbot_get_my_application` | Retrieves detailed information about the current authenticated Discord application via | | **Get my oauth2 application** `discordbot_get_my_oauth2_application` | Retrieves detailed information about the OAuth2 application associated with the current | | **Get original webhook message** `discordbot_get_original_webhook_message` | Retrieves the original (@original) message from a Discord webhook or interaction response | ## Example prompts **Discordbot Get Active Guild Threads** > Use Discord Bot to discordbot get active guild threads and walk me through the result in plain English. **Discordbot Get Application** > Use Discord Bot to discordbot get application and walk me through the result in plain English. **Discordbot Get Application Command** > Use Discord Bot to discordbot get application command and walk me through the result in plain English. **Discordbot Get Application Role Connections Metadata** > Use Discord Bot to discordbot get application role connections metadata and walk me through the result in plain English. ## 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 Bot working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Discord Bot app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Discord Bot 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 Bot. | 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 Bot actions to the runtime in a format your agent can reliably use. | 165 tools for Discord Bot are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Discord Bot 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 Bot in the browser, and the 165 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](https://claw-link.dev/hub/composio-alternatives) comparison. ### 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 Bot 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 Bot tools Discord Bot 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 Bot 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 Bot 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 Bot and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete. ### Is there a Grok Bot Discord Bot integration? Yes. ClawLink is the fastest way to connect Grok Bot to Discord Bot: link your Discord Bot account once in the browser and Grok Bot can call the Discord Bot API through 165 ready-made tools — no custom code or token handling. ### How do I connect Discord Bot 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-bot` to authorize Discord Bot. 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 Bot to Grok Bot? About two minutes. Sign in, click Connect next to Discord Bot in the dashboard, authenticate, and Grok Bot can use it from the next chat message. ### Why use ClawLink instead of wiring Discord Bot 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 Bot 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. ## Related - [Connect SendGrid](https://claw-link.dev/grokbot/sendgrid) — Deliver transactional and marketing emails - [Dialpad tools](https://claw-link.dev/grokbot/dialpad) — Business phone, messaging, and video conferencing - [Grok Bot Slack integration](https://claw-link.dev/grokbot/slack) — Post messages and browse Slack channels