How to connect Modelry to OpenClaw
Connect Modelry to OpenClaw with ClawLink: paste your Modelry key once and 14 tools work from chat. No MCP server to run, nothing stored on your machine.
ModelryAPI KEYMCPModelry is a 3D visualization platform for eCommerce that creates custom 3D product models, AR experiences, and digital asset management.. Once connected, OpenClaw can read and act on Modelry from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Modelry 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 Modelry setup: install one ClawHub skill, connect Modelry in the browser, and OpenClaw can call real Modelry 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 Modelry.
1Install 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 Modelry
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Modelry?"
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-pluginThen 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 Modelry in the ClawLink dashboard — paste your Modelry API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Modelry, 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 loginlogin opens the same browser approval and stores a credential locally. Once Modelry is connected in the dashboard, that agent calls the same 14 Modelry tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Modelry MCP for OpenClaw
Looking for a Modelry MCP server for OpenClaw? ClawLink connects Modelry to OpenClaw and exposes 14 Modelry tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Modelry integration works the same way.
What the OpenClaw Modelry integration can do
14 Modelry tools are ready for OpenClaw once the account is connected. The 10 below are the ones people reach for most; your agent can call all 14.
10 of 14 Modelry tools for OpenClaw
| Tool | What it does |
|---|---|
Get embed modelry_get_embed | Retrieve details of a specific Modelry embed (3D viewer or AR experience for eCommerce) |
Get workspace modelry_get_workspace | Retrieves details for a specific Modelry workspace by its ID or name |
List embeds modelry_list_embeds | List embeds in Modelry |
List modeling requests modelry_list_modeling_requests | List all 3D modeling requests in a workspace |
List product repositories modelry_list_product_repositories | List all product repositories in a workspace |
List products modelry_list_products | List all products in Modelry |
List workspaces modelry_list_workspaces | List all workspaces in Modelry |
Track modeling progress modelry_track_modeling_progress | Track the progress of a 3D modeling request |
Create workspace modelry_create_workspace | Create a new workspace or return an existing one with the same name |
Order modeling service modelry_order_modeling_service | Place an order for 3D modeling services |
Try it: find the Modelry tool you need
Browse the 10 Modelry 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 Modelry, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Modelry, summarize it in plain English, and point out anything that needs attention.
List the relevant items in Modelry, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in Modelry, 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 Modelry working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Modelry API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Modelry 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 Modelry. | 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 Modelry actions to the runtime in a format your agent can reliably use. | 14 tools for Modelry are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Modelry 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 Modelry in the browser, and the 14 tools above work from chat. There is no SDK and no config file, and the Modelry 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 Modelry skill but can't call the tools
The ClawHub skill teaches OpenClaw about Modelry, but the calls run through the ClawLink plugin and your connected account. Make sure Modelry 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 Modelry 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 Modelry tools
Modelry 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 Modelry 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.
Modelry 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 Modelry 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 Modelry integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Modelry: link your Modelry account once in the browser and OpenClaw can call the Modelry API through 14 ready-made tools — no custom code or token handling.
How do I add Modelry to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Modelry skill from ClawHub, then you click Connect in the dashboard to authorize Modelry. OpenClaw calls the tools from the next message — no config files, and the Modelry key you paste is stored server-side instead of in your environment.
How long does it take to connect Modelry to OpenClaw?
About two minutes. Sign in, click Connect next to Modelry in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Modelry 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 Modelry working from chat.
OpenClaw installed the Modelry skill but can't call the tools
The ClawHub skill teaches OpenClaw about Modelry, but the calls run through the ClawLink plugin and your connected account. Make sure Modelry 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
Connect Cloudcart
CloudCart is an e-commerce platform that enables businesses to create and manage online stores efficiently.
Wix
Manage sites, products, orders, and bookings
OpenClaw Baselinker integration
BaseLinker is a comprehensive e-commerce management platform that integrates with various marketplaces, online stores, carriers, and accounting systems to streamline order processing, inventory management, and sales automation.