How to connect Grok to OpenClaw (paste one key, 8 tools)

The usual route to Grok access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Grok setup: install one ClawHub skill, connect Grok in the browser, and OpenClaw can call real Grok actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.

Setup

It takes three steps to connect OpenClaw to Grok.

1
Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin
2
Connect Grok
Paste your API key in the dashboard.
3
Use it from chat
Ask OpenClaw: "What can you do with Grok?"

Install by command

The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:

openclaw plugins install clawhub:clawlink-plugin

Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Grok in the ClawLink dashboard — paste your Grok API key once.

Verify the connection by asking OpenClaw:

Pull the relevant data from Grok, summarize it in plain English, and point out anything that needs attention.

Using a different agent?

The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:

npx -y @useclawlink/cli login

login opens the same browser approval and stores a credential locally. Once Grok is connected in the dashboard, that agent calls the same 8 Grok tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.

Grok MCP for OpenClaw

Looking for a Grok MCP server for OpenClaw? ClawLink connects Grok to OpenClaw and exposes 8 Grok tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Grok integration works the same way.

What the OpenClaw Grok integration can do

8 Grok tools are ready for OpenClaw once the account is connected.

All 8 Grok tools for OpenClaw

Tool	What it does
Get API key info `grok_get_api_key_info`	Inspect the connected xAI API key's identity, wildcard or granular ACLs, and key or team
Get current account `grok_get_current_account`	Verify the connected xAI credential and return the caller, team, zero-data-retention status
Get video `grok_get_video`	Check an asynchronous xAI video request
List models `grok_list_models`	List models available to the connected xAI key, including model IDs and published pricing
Create embeddings `grok_create_embeddings`	Create vector embeddings for one or more text inputs with an xAI embedding model
Create response `grok_create_response`	Generate a bounded, non-streaming Grok response from text or structured multimodal input, with
Generate image `grok_generate_image`	Generate one or more images from a text prompt with an xAI image-generation model
Generate video `grok_generate_video`	Start asynchronous xAI video generation from a text prompt, optionally conditioned on an image

Try it: find the Grok tool you need

Browse the 8 Grok tools

Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.

Example prompts

Pull the relevant data from Grok, summarize it in plain English, and point out anything that needs attention.

List the relevant items in Grok, group them by priority, and recommend what OpenClaw should do next.

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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Grok working from chat.

	Manual	ClawLink
Credential handling	Collect, validate, store, and rotate the Grok API key yourself, then make sure every tool call uses the right account.	Users complete the hosted ClawLink setup once and the connected Grok 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 Grok.	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 Grok actions to the runtime in a format your agent can reliably use.	8 tools for Grok are already exposed through ClawLink, so the agent can read and act from chat immediately.

ClawLink vs. Composio

Composio also exposes Grok 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 OpenClaw users instead. You install the plugin once, connect Grok in the browser, and the 8 tools above work from chat. There is no SDK and no config file, and the Grok key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.

Troubleshooting

OpenClaw installed the Grok skill but can't call the tools

The ClawHub skill teaches OpenClaw about Grok, but the calls run through the ClawLink plugin and your connected account. Make sure Grok is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.

Connection succeeds but no tools appear

Reconnect Grok 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 Grok tools

Grok 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 Grok 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.

Grok 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 Grok has the right scopes or account access. A valid key can still be too limited for some reads or writes.

FAQ

Is there a OpenClaw Grok integration?

Yes. ClawLink is the fastest way to connect OpenClaw to Grok: link your Grok account once in the browser and OpenClaw can call the Grok API through 8 ready-made tools — no custom code or token handling.

How do I add Grok to OpenClaw with ClawLink?

Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Grok skill from ClawHub, then you click Connect in the dashboard to authorize Grok. OpenClaw calls the tools from the next message — no config files, and the Grok key you paste is stored server-side instead of in your environment.

How long does it take to connect Grok to OpenClaw?

About two minutes. Sign in, click Connect next to Grok in the dashboard, authenticate, and OpenClaw can use it from the next chat message.

Why use ClawLink instead of wiring Grok up myself?

OpenClaw installed the Grok skill but can't call the tools

How to connect Grok to OpenClaw

Setup

Install the plugin

Connect Grok

Use it from chat