# How to connect Uplisting to OpenClaw (paste one key, 10 tools) > Connect Uplisting to OpenClaw with ClawLink: paste your Uplisting 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/uplisting The usual route to Uplisting 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 Uplisting setup: install one ClawHub skill, connect Uplisting in the browser, and OpenClaw can call real Uplisting 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 Uplisting. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Uplisting** — 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 uplisting # connect Uplisting (browser OAuth) npx -y @useclawlink/cli actions uplisting # list available actions npx -y @useclawlink/cli run uplisting --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 Uplisting in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Uplisting API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Uplisting, 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 Uplisting is connected in the dashboard, that agent calls the same 10 Uplisting 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). ## Uplisting MCP for OpenClaw Looking for a Uplisting MCP server for OpenClaw? ClawLink connects Uplisting to OpenClaw and exposes 10 Uplisting 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 Uplisting integration](https://claw-link.dev/hermes/uplisting) works the same way. ## What the OpenClaw Uplisting integration can do 10 Uplisting tools are ready for OpenClaw once the account is connected. The 9 below are the ones people reach for most; your agent can call all 10. ### 9 of 10 Uplisting tools for OpenClaw | Tool | What it does | |---|---| | **Get calendar** `uplisting_get_calendar` | Return up to 12 months of daily availability, rates, and stay restrictions for one property | | **Get current account** `uplisting_get_current_account` | Return the name and stable UID of the Uplisting account connected by the current API key | | **Get property** `uplisting_get_property` | Return one Uplisting property by ID with the related resources supplied by the API | | **List bookings** `uplisting_list_bookings` | Return one explicitly selected 0-based page of bookings for a property and optional date range | | **List properties** `uplisting_list_properties` | Return all properties in the connected Uplisting account, including the related resources | | **List webhooks** `uplisting_list_webhooks` | Return the webhook subscriptions registered for the connected Uplisting account | | **Search availability** `uplisting_search_availability` | Find Uplisting properties available for optional stay dates, guest count, city, and nightly | | **Create webhook** `uplisting_create_webhook` | Register a public callback URL for one booking or property event and return the new webhook ID | | **Update calendar** `uplisting_update_calendar` | Asynchronously change availability, rates, or stay restrictions for dated days or date ranges | ## Example prompts **Get Calendar** > Pull the relevant data from Uplisting, summarize it in plain English, and point out anything that needs attention. **Get Current Account** > Pull the relevant data from Uplisting, summarize it in plain English, and point out anything that needs attention. **Get Property** > Pull the relevant data from Uplisting, summarize it in plain English, and point out anything that needs attention. **List Bookings** > List the relevant items in Uplisting, 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 Uplisting working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Uplisting API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Uplisting 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 Uplisting. | 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 Uplisting actions to the runtime in a format your agent can reliably use. | 10 tools for Uplisting are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Uplisting 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 Uplisting in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the Uplisting 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 Uplisting skill but can't call the tools The ClawHub skill teaches OpenClaw about Uplisting, but the calls run through the ClawLink plugin and your connected account. Make sure Uplisting 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 Uplisting 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 Uplisting tools Uplisting 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 Uplisting 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. ### Uplisting 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 Uplisting has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Uplisting integration? Yes. ClawLink is the fastest way to connect OpenClaw to Uplisting: link your Uplisting account once in the browser and OpenClaw can call the Uplisting API through 10 ready-made tools — no custom code or token handling. ### How do I add Uplisting to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Uplisting skill from ClawHub, then you click Connect in the dashboard to authorize Uplisting. OpenClaw calls the tools from the next message — no config files, and the Uplisting key you paste is stored server-side instead of in your environment. ### How long does it take to connect Uplisting to OpenClaw? About two minutes. Sign in, click Connect next to Uplisting in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Uplisting 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 Uplisting working from chat. ### OpenClaw installed the Uplisting skill but can't call the tools The ClawHub skill teaches OpenClaw about Uplisting, but the calls run through the ClawLink plugin and your connected account. Make sure Uplisting 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 - [Trello tools](https://claw-link.dev/openclaw/trello) — Manage boards, lists, and cards - [OpenClaw Moco integration](https://claw-link.dev/openclaw/moco) — MOCO is a business management software offering project management, time tracking, and invoicing solutions. - [ClickUp tools](https://claw-link.dev/openclaw/clickup) — Manage tasks, docs, goals, and sprints