# How to connect Markup AI to OpenClaw (paste one key, 10 tools) > Connect Markup AI to OpenClaw with ClawLink: paste your Markup AI 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/markup-ai The usual route to Markup AI 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 Markup AI setup: install one ClawHub skill, connect Markup AI in the browser, and OpenClaw can call real Markup AI 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 Markup AI. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Markup AI** — 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 markup-ai # connect Markup AI (browser OAuth) npx -y @useclawlink/cli actions markup-ai # list available actions npx -y @useclawlink/cli run markup-ai --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 Markup AI in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Markup AI API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Markup AI, 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 Markup AI is connected in the dashboard, that agent calls the same 10 Markup AI 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). ## Markup AI MCP for OpenClaw Looking for a Markup AI MCP server for OpenClaw? ClawLink connects Markup AI to OpenClaw and exposes 10 Markup AI 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 Markup AI integration](https://claw-link.dev/hermes/markup-ai) works the same way. ## What the OpenClaw Markup AI integration can do 10 Markup AI tools are ready for OpenClaw once the account is connected. ### All 10 Markup AI tools for OpenClaw | Tool | What it does | |---|---| | **Get agent** `markup_ai_get_agent` | Get one agent's metadata and complete runtime input and output JSON Schemas before executing it | | **Get analysis profile** `markup_ai_get_analysis_profile` | Get one persona, brand voice profile, style target, or style guide by ID, including detailed | | **Get workflow** `markup_ai_get_workflow` | Get the current status and result of an asynchronous agent workflow by ID | | **List agent categories** `markup_ai_list_agent_categories` | Return all agent categories available to the connected organization for discovery and | | **List agents** `markup_ai_list_agents` | Discover Markup AI agents available to the connected organization, optionally filtered by | | **List analysis profiles** `markup_ai_list_analysis_profiles` | List selectable persona, brand voice, style guide, style target, or content profile resources | | **List terminology resources** `markup_ai_list_terminology_resources` | List terminology term sets or domains with filters and cursor-controlled pagination | | **List workflows** `markup_ai_list_workflows` | List one cursor-controlled page of agent execution workflows, optionally filtering that page by | | **Search terminology** `markup_ai_search_terminology` | Find organization terminology rules relevant to supplied text, optionally limited to selected | | **Run agent** `markup_ai_run_agent` | Run one selected Markup AI agent against document text, synchronously or asynchronously | ## Example prompts **Get Agent** > Pull the relevant data from Markup AI, summarize it in plain English, and point out anything that needs attention. **Get Analysis Profile** > Pull the relevant data from Markup AI, summarize it in plain English, and point out anything that needs attention. **Get Workflow** > Pull the relevant data from Markup AI, summarize it in plain English, and point out anything that needs attention. **List Agent Categories** > List the relevant items in Markup AI, 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 Markup AI working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Markup AI API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Markup AI 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 Markup AI. | 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 Markup AI actions to the runtime in a format your agent can reliably use. | 10 tools for Markup AI are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Markup AI 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 Markup AI in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the Markup AI 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 Markup AI skill but can't call the tools The ClawHub skill teaches OpenClaw about Markup AI, but the calls run through the ClawLink plugin and your connected account. Make sure Markup AI 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 Markup AI 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 Markup AI tools Markup AI 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 Markup AI 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. ### Markup AI 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 Markup AI has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Markup AI integration? Yes. ClawLink is the fastest way to connect OpenClaw to Markup AI: link your Markup AI account once in the browser and OpenClaw can call the Markup AI API through 10 ready-made tools — no custom code or token handling. ### How do I add Markup AI to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Markup AI skill from ClawHub, then you click Connect in the dashboard to authorize Markup AI. OpenClaw calls the tools from the next message — no config files, and the Markup AI key you paste is stored server-side instead of in your environment. ### How long does it take to connect Markup AI to OpenClaw? About two minutes. Sign in, click Connect next to Markup AI in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Markup AI 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 Markup AI working from chat. ### OpenClaw installed the Markup AI skill but can't call the tools The ClawHub skill teaches OpenClaw about Markup AI, but the calls run through the ClawLink plugin and your connected account. Make sure Markup AI 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 DataRobot integration](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. - [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.