# How to connect Dynamic Mockups to OpenClaw (paste one key, 10 tools) > Connect Dynamic Mockups to OpenClaw with ClawLink: paste your Dynamic Mockups key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/dynamic-mockups The usual route to Dynamic Mockups 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 Dynamic Mockups setup: install one ClawHub skill, connect Dynamic Mockups in the browser, and OpenClaw can call real Dynamic Mockups 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 Dynamic Mockups. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Dynamic Mockups** — 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 dynamic-mockups # connect Dynamic Mockups (browser OAuth) npx -y @useclawlink/cli actions dynamic-mockups # list available actions npx -y @useclawlink/cli run dynamic-mockups --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 Dynamic Mockups in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Dynamic Mockups API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Dynamic Mockups, 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 Dynamic Mockups is connected in the dashboard, that agent calls the same 10 Dynamic Mockups 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). ## Dynamic Mockups MCP for OpenClaw Looking for a Dynamic Mockups MCP server for OpenClaw? ClawLink connects Dynamic Mockups to OpenClaw and exposes 10 Dynamic Mockups 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 Dynamic Mockups integration](https://claw-link.dev/hermes/dynamic-mockups) works the same way. ## What the OpenClaw Dynamic Mockups integration can do 10 Dynamic Mockups tools are ready for OpenClaw once the account is connected. ### All 10 Dynamic Mockups tools for OpenClaw | Tool | What it does | |---|---| | **Get generation options** `dynamic_mockups_get_generation_options` | Return current MockAnything styles and aspect-ratio support plus MotionMockups models | | **Get mockanything product** `dynamic_mockups_get_mockanything_product` | Get one POD product's supported sizes, colors, and decoration locations before using its UUID | | **Get mockanything status** `dynamic_mockups_get_mockanything_status` | Check one MockAnything task once, typically after Create MockAnything Mockup stops waiting | | **Get motion mockup status** `dynamic_mockups_get_motion_mockup_status` | Check a submitted MotionMockups video job once and return its queue state or completed MP4 | | **List catalogs and collections** `dynamic_mockups_list_catalogs_and_collections` | Return the connected account's catalogs and collections, including the UUIDs used to filter | | **List mockups** `dynamic_mockups_list_mockups` | Find renderable mockup templates and return their mockup, smart-object, text-layer, and | | **Search mockanything products** `dynamic_mockups_search_mockanything_products` | Fuzzy-search POD products that can ground MockAnything generation | | **Create mockanything mockup** `dynamic_mockups_create_mockanything_mockup` | Create and optionally wait for a MockAnything mockup from exactly one prompt, public image URL | | **Render mockups** `dynamic_mockups_render_mockups` | Render one or more explicitly selected mockup templates from public artwork URLs, colors, Beta | | **Submit motion mockup** `dynamic_mockups_submit_motion_mockup` | WARNING: Submit image-to-video generation and return a request ID for later status checks | ## Example prompts **Get Generation Options** > Pull the relevant data from Dynamic Mockups, summarize it in plain English, and point out anything that needs attention. **Get Mockanything Product** > Pull the relevant data from Dynamic Mockups, summarize it in plain English, and point out anything that needs attention. **Get Mockanything Status** > Pull the relevant data from Dynamic Mockups, summarize it in plain English, and point out anything that needs attention. **Get Motion Mockup Status** > Pull the relevant data from Dynamic Mockups, 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 Dynamic Mockups working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Dynamic Mockups API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Dynamic Mockups 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 Dynamic Mockups. | 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 Dynamic Mockups actions to the runtime in a format your agent can reliably use. | 10 tools for Dynamic Mockups are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Dynamic Mockups 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 Dynamic Mockups in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the Dynamic Mockups 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 Dynamic Mockups skill but can't call the tools The ClawHub skill teaches OpenClaw about Dynamic Mockups, but the calls run through the ClawLink plugin and your connected account. Make sure Dynamic Mockups 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 Dynamic Mockups 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 Dynamic Mockups tools Dynamic Mockups 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 Dynamic Mockups 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. ### Dynamic Mockups 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 Dynamic Mockups has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Dynamic Mockups integration? Yes. ClawLink is the fastest way to connect OpenClaw to Dynamic Mockups: link your Dynamic Mockups account once in the browser and OpenClaw can call the Dynamic Mockups API through 10 ready-made tools — no custom code or token handling. ### How do I add Dynamic Mockups to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Dynamic Mockups skill from ClawHub, then you click Connect in the dashboard to authorize Dynamic Mockups. OpenClaw calls the tools from the next message — no config files, and the Dynamic Mockups key you paste is stored server-side instead of in your environment. ### How long does it take to connect Dynamic Mockups to OpenClaw? About two minutes. Sign in, click Connect next to Dynamic Mockups in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Dynamic Mockups 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 Dynamic Mockups working from chat. ### OpenClaw installed the Dynamic Mockups skill but can't call the tools The ClawHub skill teaches OpenClaw about Dynamic Mockups, but the calls run through the ClawLink plugin and your connected account. Make sure Dynamic Mockups 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 - [OpenClaw Cloudinary integration](https://claw-link.dev/openclaw/cloudinary) — Cloudinary is a cloud-based media management platform for uploading, storing, transforming, and delivering images and videos via CDN. - [Connect Penpot](https://claw-link.dev/openclaw/penpot) — Open-source design and prototyping platform for collaborative design workflows. - [Canva tools](https://claw-link.dev/openclaw/canva) — Create designs, upload assets, export content, and manage brand templates