# How to connect Handwrytten to OpenClaw (paste one key, 48 tools) > Connect Handwrytten to OpenClaw with ClawLink: paste your Handwrytten key once and 48 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/handwrytten The usual route to Handwrytten 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 Handwrytten setup: install one ClawHub skill, connect Handwrytten in the browser, and OpenClaw can call real Handwrytten 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 Handwrytten. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Handwrytten** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **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 handwrytten # connect Handwrytten (browser OAuth) npx -y @useclawlink/cli actions handwrytten # list available actions npx -y @useclawlink/cli run handwrytten --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 Handwrytten in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Handwrytten API key once. Verify the connection by asking OpenClaw: > Use Handwrytten to calculate order taxes 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 Handwrytten is connected in the dashboard, that agent calls the same 48 Handwrytten 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). ## Handwrytten MCP for OpenClaw Looking for a Handwrytten MCP server for OpenClaw? ClawLink connects Handwrytten to OpenClaw and exposes 48 Handwrytten 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 Handwrytten integration](https://claw-link.dev/hermes/handwrytten) works the same way. ## What the OpenClaw Handwrytten integration can do 48 Handwrytten 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 48. ### 30 of 48 Handwrytten tools for OpenClaw | Tool | What it does | |---|---| | **Calculate order taxes** `handwrytten_calculate_order_taxes` | Calculate taxes for Handwrytten basket orders | | **Check auth** `handwrytten_check_auth` | Verify API key authentication validity for Handwrytten | | **Get basket all new** `handwrytten_get_basket_all_new` | Retrieve the user's basket using the new method | | **Get basket count** `handwrytten_get_basket_count` | Retrieve the count of items currently in the basket | | **Get basket item** `handwrytten_get_basket_item` | Retrieve a basket item by its ID from Handwrytten | | **Get card details** `handwrytten_get_card_details` | Get detailed information about a specific card in the Handwrytten catalog | | **Get list addresses** `handwrytten_get_list_addresses` | Retrieve a list of all addresses associated with the user's account | | **Get random cards** `handwrytten_get_random_cards` | Retrieve random cards from Handwrytten | | **Get template details** `handwrytten_get_template_details` | Get detailed information about a card text template in the Handwrytten catalog | | **Get user** `handwrytten_get_user` | Retrieve information about the currently authenticated user | | **Get user address** `handwrytten_get_user_address` | Retrieve the authenticated user's address and billing information | | **List basket orders grouped** `handwrytten_list_basket_orders_grouped` | List all basket orders grouped by basket | | **List baskets** `handwrytten_list_baskets` | Retrieve a list of user's past baskets | | **List cards** `handwrytten_list_cards` | Retrieve a list of available Handwrytten cards with optional filtering and pagination | | **List categories** `handwrytten_list_categories` | Retrieve the list of available card categories from Handwrytten | | **List countries** `handwrytten_list_countries` | Retrieve the list of countries available in Handwrytten | | **List credit cards** `handwrytten_list_credit_cards` | List all credit cards associated with the Handwrytten account | | **List fonts** `handwrytten_list_fonts` | Retrieve the list of available handwriting fonts | | **List fonts for customizer** `handwrytten_list_fonts_for_customizer` | List fonts available for use with the card customizer | | **List gcards** `handwrytten_list_gcards` | Retrieve the list of available gift cards with their denominations and pricing | | **List images** `handwrytten_list_images` | Retrieve a list of custom user images uploaded to Handwrytten | | **List inserts** `handwrytten_list_inserts` | Retrieve a list of available inserts from Handwrytten | | **List orders** `handwrytten_list_orders` | Retrieve a list of user's past orders from Handwrytten | | **List orders grouped** `handwrytten_list_orders_grouped` | Retrieve the user's order history grouped by basket | | **List past orders** `handwrytten_list_past_orders` | Retrieve a list of user's past orders from Handwrytten API | | **List recipients** `handwrytten_list_recipients` | Retrieve a list of recipient addresses that the user has previously saved | | **List signatures** `handwrytten_list_signatures` | Retrieve the list of available signatures for use in card orders | | **List states** `handwrytten_list_states` | Retrieve the list of states/provinces available in Handwrytten | | **List template categories** `handwrytten_list_template_categories` | Retrieve the list of available template categories from Handwrytten | | **List templates** `handwrytten_list_templates` | Retrieve a list of card text templates from Handwrytten | ## Example prompts **Calculate Order Taxes** > Use Handwrytten to calculate order taxes and walk me through the result in plain English. **Check Auth** > Use Handwrytten to check auth and walk me through the result in plain English. **Get Basket All New** > Pull the relevant data from Handwrytten, summarize it in plain English, and point out anything that needs attention. **Get Basket Count** > Pull the relevant data from Handwrytten, 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Handwrytten working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Handwrytten API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Handwrytten 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 Handwrytten. | 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 Handwrytten actions to the runtime in a format your agent can reliably use. | 48 tools for Handwrytten are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Handwrytten 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 Handwrytten in the browser, and the 48 tools above work from chat. There is no SDK and no config file, and the Handwrytten 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 Handwrytten skill but can't call the tools The ClawHub skill teaches OpenClaw about Handwrytten, but the calls run through the ClawLink plugin and your connected account. Make sure Handwrytten 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 Handwrytten 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 Handwrytten tools Handwrytten 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 Handwrytten 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. ### Handwrytten 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 Handwrytten has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Handwrytten integration? Yes. ClawLink is the fastest way to connect OpenClaw to Handwrytten: link your Handwrytten account once in the browser and OpenClaw can call the Handwrytten API through 48 ready-made tools — no custom code or token handling. ### How do I add Handwrytten to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Handwrytten skill from ClawHub, then you click Connect in the dashboard to authorize Handwrytten. OpenClaw calls the tools from the next message — no config files, and the Handwrytten key you paste is stored server-side instead of in your environment. ### How long does it take to connect Handwrytten to OpenClaw? About two minutes. Sign in, click Connect next to Handwrytten in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Handwrytten 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 Handwrytten working from chat. ### OpenClaw installed the Handwrytten skill but can't call the tools The ClawHub skill teaches OpenClaw about Handwrytten, but the calls run through the ClawLink plugin and your connected account. Make sure Handwrytten 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 - [ActiveCampaign tools](https://claw-link.dev/openclaw/activecampaign) — Marketing automation, CRM, and email marketing - [OpenClaw Benchmark Email integration](https://claw-link.dev/openclaw/benchmark-email) — Benchmark Email is a comprehensive email marketing platform offering tools for creating, sending, and analyzing email campaigns. - [Connect Mailchimp](https://claw-link.dev/openclaw/mailchimp) — Create email campaigns and manage audiences