# How to connect ElevenLabs to Grok Bot (paste one key, 155 tools) > Connect ElevenLabs to Grok Bot with ClawLink: paste your ElevenLabs key once and 155 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/grokbot/elevenlabs Grok Bot runs on its own cloud computer, so most ElevenLabs guides send you to register an OAuth app and paste keys into a sandbox that resets. ClawLink gives Grok Bot a more practical ElevenLabs setup: it runs one CLI command, you approve once in the browser, and Grok Bot can call real ElevenLabs 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 elevenlabs` > 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 ElevenLabs. 1. **Pair from the terminal** — ask Grok Bot to run `npx -y @useclawlink/cli login` and approve the link it prints. 2. **Connect ElevenLabs** — `npx -y @useclawlink/cli connect elevenlabs`, 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 elevenlabs # connect ElevenLabs (browser OAuth) npx -y @useclawlink/cli actions elevenlabs # list available actions npx -y @useclawlink/cli run elevenlabs --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 elevenlabs ``` 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: > Create it in ElevenLabs for me, then confirm the important fields before you finish. ### 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 ElevenLabs is connected in the dashboard, that agent calls the same 155 ElevenLabs 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). ## ElevenLabs MCP for Grok Bot Looking for a ElevenLabs MCP server for Grok Bot? ClawLink connects ElevenLabs to Grok Bot and exposes 155 ElevenLabs 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 ElevenLabs integration](https://claw-link.dev/openclaw/elevenlabs) and the [Hermes ElevenLabs integration](https://claw-link.dev/hermes/elevenlabs) connect the same ClawLink account the same way. ## What the Grok Bot ElevenLabs integration can do 155 ElevenLabs 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 155. ### 30 of 155 ElevenLabs tools for Grok Bot | Tool | What it does | |---|---| | **Create conversational agent** `elevenlabs_create_conversational_agent` | Create a conversational AI agent | | **Download history items** `elevenlabs_download_history_items` | Download audio from history | | **Generate a random voice** `elevenlabs_generate_a_random_voice` | Generate a unique random voice | | **Get convai agents summaries** `elevenlabs_get_convai_agents_summaries` | List conversational AI agents | | **Get dubbing project metadata** `elevenlabs_get_dubbing_project_metadata` | Get dubbing project metadata | | **Get history item by ID** `elevenlabs_get_history_item_by_id` | Get a history audio item | | **Get models** `elevenlabs_get_models` | List available models | | **Get project by ID** `elevenlabs_get_project_by_id` | Get a specific project | | **Get projects** `elevenlabs_get_projects` | List ElevenLabs projects | | **Get user subscription info** `elevenlabs_get_user_subscription_info` | Get subscription usage and limits | | **Get voice** `elevenlabs_get_voice` | Get details for a specific voice | | **Get voices** `elevenlabs_get_voices` | List available ElevenLabs voices | | **List dubs** `elevenlabs_list_dubs` | List dubbing projects | | **Speech to speech** `elevenlabs_speech_to_speech` | Transform audio from one voice to another | | **Text to speech** `elevenlabs_text_to_speech` | Convert text to speech using ElevenLabs voices | | **Calculate convai agent llm usage** `elevenlabs_calculate_convai_agent_llm_usage` | Calculate expected number of LLM tokens needed for a conversational AI agent | | **Calculate convai llm usage** `elevenlabs_calculate_convai_llm_usage` | Calculate expected LLM usage costs for conversational AI agents | | **Create music plan** `elevenlabs_create_music_plan` | Generate a music composition plan from a text prompt using ElevenLabs Music API | | **Create similar voices** `elevenlabs_create_similar_voices` | Returns a list of shared voices similar to the provided audio sample | | **Get a profile page** `elevenlabs_get_a_profile_page` | Retrieves the profile information for the authenticated ElevenLabs user (identified by API key) | | **Get agent details** `elevenlabs_get_agent_details` | Retrieve available Conversational AI agents and outbound-capable Twilio phone numbers | | **Get agent link** `elevenlabs_get_agent_link` | Get the current shareable link for a Conversational AI agent | | **Get audio from history item** `elevenlabs_get_audio_from_history_item` | Retrieves the audio content for a specific history item from ElevenLabs, using a | | **Get audio from sample** `elevenlabs_get_audio_from_sample` | Retrieves the audio for a given `sample_id` that must belong to the specified `voice_id` | | **Get audio native settings** `elevenlabs_get_audio_native_settings` | Retrieve player settings for a specific Audio Native project | | **Get chapter by ID** `elevenlabs_get_chapter_by_id` | Fetches comprehensive details for a specific chapter within a given project, including its | | **Get chapter snapshots** `elevenlabs_get_chapter_snapshots` | Retrieves all saved version snapshots for a specific chapter within a given project, enabling | | **Get chapters** `elevenlabs_get_chapters` | Retrieves a list of all chapters, their details, and conversion status for a project, useful | | **Get convai agent** `elevenlabs_get_convai_agent` | Retrieve the complete configuration for a specific Conversational AI agent by ID | | **Get convai agent knowledge base size** `elevenlabs_get_convai_agent_knowledge_base_size` | Retrieve the number of pages in a conversational AI agent's knowledge base | ## Example prompts **Create Conversational Agent** > Create it in ElevenLabs for me, then confirm the important fields before you finish. **Download History Items** > Use ElevenLabs to download history items and walk me through the result in plain English. **Generate A Random Voice** > Use ElevenLabs to generate a random voice and walk me through the result in plain English. **Get Convai Agents Summaries** > Pull the relevant data from ElevenLabs, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key 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 ElevenLabs working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the ElevenLabs API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected ElevenLabs account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for ElevenLabs. | 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 ElevenLabs actions to the runtime in a format your agent can reliably use. | 155 tools for ElevenLabs are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes ElevenLabs 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 ElevenLabs in the browser, and the 155 tools above work from chat. There is no SDK and no config file, and the ElevenLabs key you paste at setup is stored server-side rather than kept in your environment. 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 ElevenLabs 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 ElevenLabs tools ElevenLabs 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 ElevenLabs 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. ### ElevenLabs 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. ### API key setup works but results look incomplete Double-check that the API key for ElevenLabs has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a Grok Bot ElevenLabs integration? Yes. ClawLink is the fastest way to connect Grok Bot to ElevenLabs: link your ElevenLabs account once in the browser and Grok Bot can call the ElevenLabs API through 155 ready-made tools — no custom code or token handling. ### How do I connect ElevenLabs 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 elevenlabs` to authorize ElevenLabs. 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, and the ElevenLabs key you paste is stored server-side instead of in your environment. ### How long does it take to connect ElevenLabs to Grok Bot? About two minutes. Sign in, click Connect next to ElevenLabs in the dashboard, authenticate, and Grok Bot can use it from the next chat message. ### Why use ClawLink instead of wiring ElevenLabs up myself? The alternative to ClawLink is usually manual API key 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 ElevenLabs 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 - [Grok Bot DataRobot integration](https://claw-link.dev/grokbot/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets. - [Grok Bot Chatbotkit integration](https://claw-link.dev/grokbot/chatbotkit) — ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications. - [Griptape](https://claw-link.dev/grokbot/griptape) — Griptape is a comprehensive platform offering tools and frameworks for building, deploying, and scaling generative AI applications.