# How to connect Griptape to OpenClaw (paste one key, 143 tools) > Connect Griptape to OpenClaw with ClawLink: paste your Griptape key once and 143 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/griptape The usual route to Griptape 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 Griptape setup: install one ClawHub skill, connect Griptape in the browser, and OpenClaw can call real Griptape actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/griptape ## Setup It takes three steps to connect OpenClaw to Griptape. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Griptape** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect griptape # connect Griptape (browser OAuth) npx -y @useclawlink/cli actions griptape # list available actions npx -y @useclawlink/cli run griptape --input '' # execute (add --confirm for writes) ``` ### 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: ```bash 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 Griptape in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Griptape API key once. Verify the connection by asking OpenClaw: > Use Griptape to assistant creation and walk me through the result in plain English. ### 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Griptape is connected in the dashboard, that agent calls the same 143 Griptape 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). ## Griptape MCP for OpenClaw Looking for a Griptape MCP server for OpenClaw? ClawLink connects Griptape to OpenClaw and exposes 143 Griptape 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 Hermes instead? The [Hermes Griptape integration](https://claw-link.dev/hermes/griptape) works the same way. ## What the OpenClaw Griptape integration can do 143 Griptape tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 143. ### 30 of 143 Griptape tools for OpenClaw | Tool | What it does | |---|---| | **Assistant creation** `griptape_assistant_creation` | Create a new assistant | | **Assistant listing** `griptape_assistant_listing` | List all assistants. Use after authenticating with Griptape Cloud to retrieve available assistants. Supports optional pagination. | | **Assistant run cancellation** `griptape_assistant_run_cancellation` | Cancel an ongoing assistant run | | **Assistant run creation** `griptape_assistant_run_creation` | Creates a new assistant run to execute a conversation turn with a Griptape Cloud assistant | | **Assistant run error details** `griptape_assistant_run_error_details` | Fetch detailed error information for a specific assistant run | | **Assistant run listing** `griptape_assistant_run_listing` | List all runs for a given assistant | | **Assistant run logs retrieval** `griptape_assistant_run_logs_retrieval` | Retrieve the complete execution logs for an assistant run in Griptape Cloud | | **Assistant run retrieval** `griptape_assistant_run_retrieval` | Retrieve an assistant run's status and details | | **Assistant run retry** `griptape_assistant_run_retry` | Attempt retrying a failed assistant run | | **Get API key** `griptape_get_api_key` | Retrieve an API key's details | | **Get assistant** `griptape_get_assistant` | Retrieve a specific assistant's details by ID | | **Get billing management URL** `griptape_get_billing_management_url` | Retrieve the billing management portal URL | | **Get bucket** `griptape_get_bucket` | Retrieve a bucket's details by its ID | | **Get bucket asset** `griptape_get_bucket_asset` | Retrieve a specific asset from a Griptape Cloud bucket | | **Get bucket asset URL** `griptape_get_bucket_asset_url` | Generate a signed URL for accessing or uploading bucket assets | | **Get config** `griptape_get_config` | Retrieve Griptape Cloud configuration | | **Get credits balance** `griptape_get_credits_balance` | Retrieve the current credits balance | | **Get data connector** `griptape_get_data_connector` | Retrieve a data connector's configuration and details from Griptape Cloud | | **Get data job** `griptape_get_data_job` | Retrieve a data job's status and details by its ID | | **Get export job** `griptape_get_export_job` | Retrieve an export job by ID | | **Get function** `griptape_get_function` | Retrieve a function's details | | **Get import job** `griptape_get_import_job` | Retrieve an import job's status and details | | **Get integration** `griptape_get_integration` | Retrieve a specific integration's details by ID | | **Get knowledge base** `griptape_get_knowledge_base` | Retrieve a knowledge base's configuration and details from Griptape Cloud | | **Get knowledge base job** `griptape_get_knowledge_base_job` | Retrieve a knowledge base job's status and details by its ID | | **Get knowledge base search** `griptape_get_knowledge_base_search` | Retrieve details of a specific knowledge base search by its ID | | **Get library** `griptape_get_library` | Retrieve a specific library's details by ID | | **Get message** `griptape_get_message` | Retrieve a specific message's details by ID | | **Get model** `griptape_get_model` | Retrieve a model configuration's details by its ID | | **Get model auth config** `griptape_get_model_auth_config` | Retrieve a model auth config by ID | ## Example prompts **Assistant Creation** > Use Griptape to assistant creation and walk me through the result in plain English. **Assistant Listing** > Use Griptape to assistant listing and walk me through the result in plain English. **Assistant Run Cancellation** > Use Griptape to assistant run cancellation and walk me through the result in plain English. **Assistant Run Creation** > Use Griptape to assistant run creation and walk me through the result in plain English. ## 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 Griptape working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Griptape API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Griptape 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 Griptape. | 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 Griptape actions to the runtime in a format your agent can reliably use. | 143 tools for Griptape are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Griptape 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 Griptape in the browser, and the 143 tools above work from chat. There is no SDK and no config file, and the Griptape 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. ### OpenClaw installed the Griptape skill but can't call the tools The ClawHub skill teaches OpenClaw about Griptape, but the calls run through the ClawLink plugin and your connected account. Make sure Griptape 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 Griptape 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 Griptape tools Griptape 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 Griptape 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. ### Griptape 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 Griptape has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Griptape integration? Yes. ClawLink is the fastest way to connect OpenClaw to Griptape: link your Griptape account once in the browser and OpenClaw can call the Griptape API through 143 ready-made tools — no custom code or token handling. ### How do I add Griptape to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Griptape skill from ClawHub, then you click Connect in the dashboard to authorize Griptape. OpenClaw calls the tools from the next message — no config files, and the Griptape key you paste is stored server-side instead of in your environment. ### How long does it take to connect Griptape to OpenClaw? About two minutes. Sign in, click Connect next to Griptape in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Griptape up myself? 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 Griptape working from chat. ### OpenClaw installed the Griptape skill but can't call the tools The ClawHub skill teaches OpenClaw about Griptape, but the calls run through the ClawLink plugin and your connected account. Make sure Griptape 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. ## Related - [DataRobot](https://claw-link.dev/openclaw/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets. - [Chatbotkit](https://claw-link.dev/openclaw/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. - [Connect ElevenLabs](https://claw-link.dev/openclaw/elevenlabs) — Generate speech and voice cloning