# How to connect Meshy to OpenClaw (paste one key, 27 tools) > Connect Meshy to OpenClaw with ClawLink: paste your Meshy key once and 27 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/meshy The usual route to Meshy 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 Meshy setup: install one ClawHub skill, connect Meshy in the browser, and OpenClaw can call real Meshy 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 Meshy. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Meshy** — 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 meshy # connect Meshy (browser OAuth) npx -y @useclawlink/cli actions meshy # list available actions npx -y @useclawlink/cli run meshy --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 Meshy in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Meshy API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Meshy, 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Meshy is connected in the dashboard, that agent calls the same 27 Meshy 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). ## Meshy MCP for OpenClaw Looking for a Meshy MCP server for OpenClaw? ClawLink connects Meshy to OpenClaw and exposes 27 Meshy 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 Meshy integration](https://claw-link.dev/hermes/meshy) works the same way. ## What the OpenClaw Meshy integration can do 27 Meshy tools are ready for OpenClaw once the account is connected. The 26 below are the ones people reach for most; your agent can call all 27. ### 26 of 27 Meshy tools for OpenClaw | Tool | What it does | |---|---| | **Get credit balance** `meshy_get_credit_balance` | Return the connected Meshy account's available credit balance before starting paid generation | | **Get task** `meshy_get_task` | Retrieve current status, errors, and available outputs for one task from a selected Meshy task | | **List animation library** `meshy_list_animation_library` | Search or filter Meshy's unpaginated animation catalog and return action IDs for use when | | **List tasks** `meshy_list_tasks` | Return one page of tasks for one selected Meshy task family, with an opaque cursor for safe | | **List usage records** `meshy_list_usage_records` | Return one page of terminal API-task usage and consumed credits for the connected Meshy team | | **Create animation task** `meshy_create_animation_task` | Start a 3-credit task that applies either a selected library animation or a succeeded Text to | | **Create auto split task** `meshy_create_auto_split_task` | Split a succeeded untextured Meshy 6 or Meshy 7 model into separately printable parts and | | **Create collapsible fidget task** `meshy_create_collapsible_fidget_task` | Start an entitled 6-credit task that generates a collapsible fidget directly from an image and | | **Create convert task** `meshy_create_convert_task` | Start a 1-credit task that converts a model into one or more requested formats; returns the | | **Create creative lab build** `meshy_create_creative_lab_build` | Start a 3D build from a succeeded matching Creative Lab prototype | | **Create creative lab prototype** `meshy_create_creative_lab_prototype` | Start an entitled image-to-prototype task for a fixed Creative Lab product | | **Create image to 3d task** `meshy_create_image_to_3d_task` | Start a 3D generation task from one to four views of one object or a prior task's input images | | **Create image to image task** `meshy_create_image_to_image_task` | Start a credit-consuming task that edits or restyles one to five reference images from a text | | **Create multi color print task** `meshy_create_multi_color_print_task` | Start a 10-credit task that converts a GLB or FBX model from a prior Meshy task or direct URL | | **Create print analysis task** `meshy_create_print_analysis_task` | Start a free task that analyzes a GLB, GLTF, OBJ, FBX, or STL model from a prior Meshy task or | | **Create print repair task** `meshy_create_print_repair_task` | Start a 10-credit task that repairs a GLB, GLTF, OBJ, FBX, or STL model from a prior Meshy task | | **Create remesh task** `meshy_create_remesh_task` | Start a 5-credit task that remeshes a model to the requested topology and polygon count | | **Create resize task** `meshy_create_resize_task` | Start a 1-credit task that scales a model by height, longest side, or automatic sizing and | | **Create retexture task** `meshy_create_retexture_task` | Start a credit-consuming task that applies one text, image, or multiview style source to an | | **Create rigging task** `meshy_create_rigging_task` | Start a 5-credit task that rigs a GLB character with a biped or quadruped skeleton and return | | **Create text to 3d task** `meshy_create_text_to_3d_task` | Start a new Text to 3D preview or fused geometry-and-texture task and return its task ID | | **Create text to image task** `meshy_create_text_to_image_task` | Start a credit-consuming 2D image generation task from a text prompt | | **Create text to motion task** `meshy_create_text_to_motion_task` | Start an entitled motion-generation task from a text prompt and return its task ID | | **Create uv unwrap task** `meshy_create_uv_unwrap_task` | Start a 5-credit task that generates UV coordinates for a GLB model and return the task ID | | **Refine text to 3d task** `meshy_refine_text_to_3d_task` | Apply texture to a succeeded Text to 3D preview and return the new refine task ID | | **Cancel creative lab task** `meshy_cancel_creative_lab_task` | Cancel a Creative Lab task only while it is PENDING or IN_PROGRESS | ## Example prompts **Get Credit Balance** > Pull the relevant data from Meshy, summarize it in plain English, and point out anything that needs attention. **Get Task** > Pull the relevant data from Meshy, summarize it in plain English, and point out anything that needs attention. **List Animation Library** > List the relevant items in Meshy, group them by priority, and recommend what OpenClaw should do next. **List Tasks** > List the relevant items in Meshy, 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 Meshy working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Meshy API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Meshy 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 Meshy. | 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 Meshy actions to the runtime in a format your agent can reliably use. | 27 tools for Meshy are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Meshy 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 Meshy in the browser, and the 27 tools above work from chat. There is no SDK and no config file, and the Meshy 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 Meshy skill but can't call the tools The ClawHub skill teaches OpenClaw about Meshy, but the calls run through the ClawLink plugin and your connected account. Make sure Meshy 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 Meshy 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 Meshy tools Meshy 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 Meshy 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. ### Meshy 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 Meshy has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Meshy integration? Yes. ClawLink is the fastest way to connect OpenClaw to Meshy: link your Meshy account once in the browser and OpenClaw can call the Meshy API through 27 ready-made tools — no custom code or token handling. ### How do I add Meshy to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Meshy skill from ClawHub, then you click Connect in the dashboard to authorize Meshy. OpenClaw calls the tools from the next message — no config files, and the Meshy key you paste is stored server-side instead of in your environment. ### How long does it take to connect Meshy to OpenClaw? About two minutes. Sign in, click Connect next to Meshy in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Meshy 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 Meshy working from chat. ### OpenClaw installed the Meshy skill but can't call the tools The ClawHub skill teaches OpenClaw about Meshy, but the calls run through the ClawLink plugin and your connected account. Make sure Meshy 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 Just One API](https://claw-link.dev/openclaw/just-one-api) — Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.