ClawLink

How to connect Griptape to OpenClaw

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.

Get started for free
OpenClaw
OpenClaw
ClawLink
ClawLink
Griptape
Griptape
GriptapeAPI KEYMCP

Griptape is a comprehensive platform offering tools and frameworks for building, deploying, and scaling generative AI applications.. Once connected, OpenClaw can read and act on Griptape from chat — pairing, token refresh, and tool wiring handled for you.

143 tools

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.

Copy this prompt into OpenClaw, or open the Griptape skill on ClawHub.

Prompt for OpenClaw
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Griptape" (hith3sh/griptape-workspace) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/griptape-workspace
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Setup

It takes three steps to connect OpenClaw to Griptape.

  1. 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. 2

    Connect Griptape

    Paste your API key in the dashboard.

  3. 3

    Use it from chat

    Ask OpenClaw: "What can you do with Griptape?"

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 Griptape in the ClawLink 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:

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.

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, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Griptape integration 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

ToolWhat it does
Assistant creation griptape_assistant_creationCreate a new assistant
Assistant listing griptape_assistant_listingList all assistants. Use after authenticating with Griptape Cloud to retrieve available assistants. Supports optional pagination.
Assistant run cancellation griptape_assistant_run_cancellationCancel an ongoing assistant run
Assistant run creation griptape_assistant_run_creationCreates a new assistant run to execute a conversation turn with a Griptape Cloud assistant
Assistant run error details griptape_assistant_run_error_detailsFetch detailed error information for a specific assistant run
Assistant run listing griptape_assistant_run_listingList all runs for a given assistant
Assistant run logs retrieval griptape_assistant_run_logs_retrievalRetrieve the complete execution logs for an assistant run in Griptape Cloud
Assistant run retrieval griptape_assistant_run_retrievalRetrieve an assistant run's status and details
Assistant run retry griptape_assistant_run_retryAttempt retrying a failed assistant run
Get API key griptape_get_api_keyRetrieve an API key's details
Get assistant griptape_get_assistantRetrieve a specific assistant's details by ID
Get billing management URL griptape_get_billing_management_urlRetrieve the billing management portal URL
Get bucket griptape_get_bucketRetrieve a bucket's details by its ID
Get bucket asset griptape_get_bucket_assetRetrieve a specific asset from a Griptape Cloud bucket
Get bucket asset URL griptape_get_bucket_asset_urlGenerate a signed URL for accessing or uploading bucket assets
Get config griptape_get_configRetrieve Griptape Cloud configuration
Get credits balance griptape_get_credits_balanceRetrieve the current credits balance
Get data connector griptape_get_data_connectorRetrieve a data connector's configuration and details from Griptape Cloud
Get data job griptape_get_data_jobRetrieve a data job's status and details by its ID
Get export job griptape_get_export_jobRetrieve an export job by ID
Get function griptape_get_functionRetrieve a function's details
Get import job griptape_get_import_jobRetrieve an import job's status and details
Get integration griptape_get_integrationRetrieve a specific integration's details by ID
Get knowledge base griptape_get_knowledge_baseRetrieve a knowledge base's configuration and details from Griptape Cloud
Get knowledge base job griptape_get_knowledge_base_jobRetrieve a knowledge base job's status and details by its ID
Get knowledge base search griptape_get_knowledge_base_searchRetrieve details of a specific knowledge base search by its ID
Get library griptape_get_libraryRetrieve a specific library's details by ID
Get message griptape_get_messageRetrieve a specific message's details by ID
Get model griptape_get_modelRetrieve a model configuration's details by its ID
Get model auth config griptape_get_model_auth_configRetrieve a model auth config by ID

Try it: find the Griptape tool you need

Browse the 30 Griptape tools

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

Example prompts

Use Griptape to assistant creation and walk me through the result in plain English.

Use Griptape to assistant listing and walk me through the result in plain English.

Use Griptape to assistant run cancellation and walk me through the result in plain English.

Use Griptape to assistant run creation and walk me through the result in plain English.

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.

ManualClawLink
Credential handlingCollect, 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 maintenanceYou 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 usabilityYou 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.

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

Troubleshooting

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.

FAQ

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.