# How to connect Swaggerhub to OpenClaw (paste one key, 44 tools) > Connect Swaggerhub to OpenClaw with ClawLink: paste your Swaggerhub key once and 44 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/swaggerhub The usual route to Swaggerhub 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 Swaggerhub setup: install one ClawHub skill, connect Swaggerhub in the browser, and OpenClaw can call real Swaggerhub 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 Swaggerhub. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Swaggerhub** — 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 swaggerhub # connect Swaggerhub (browser OAuth) npx -y @useclawlink/cli actions swaggerhub # list available actions npx -y @useclawlink/cli run swaggerhub --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 Swaggerhub in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Swaggerhub API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Swaggerhub, 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 Swaggerhub is connected in the dashboard, that agent calls the same 44 Swaggerhub 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). ## Swaggerhub MCP for OpenClaw Looking for a Swaggerhub MCP server for OpenClaw? ClawLink connects Swaggerhub to OpenClaw and exposes 44 Swaggerhub 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 Swaggerhub integration](https://claw-link.dev/hermes/swaggerhub) works the same way. ## What the OpenClaw Swaggerhub integration can do 44 Swaggerhub tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 44. ### 30 of 44 Swaggerhub tools for OpenClaw | Tool | What it does | |---|---| | **Get access control users** `swaggerhub_get_access_control_users` | Retrieve the list of users assigned access control on a SwaggerHub resource | | **Get API default version** `swaggerhub_get_api_default_version` | Get the default version identifier of a SwaggerHub API | | **Get API versions** `swaggerhub_get_api_versions` | Retrieve a list of API versions for a specific API in SwaggerHub | | **Get consumer products** `swaggerhub_get_consumer_products` | Get a list of products that are visible to the consumer in a SwaggerHub portal | | **Get definition** `swaggerhub_get_definition` | Get the OpenAPI definition of a specified API version from SwaggerHub | | **Get domain default version** `swaggerhub_get_domain_default_version` | Retrieve the default version identifier of a SwaggerHub domain | | **Get domain definition** `swaggerhub_get_domain_definition` | Retrieve the OpenAPI definition of a specified domain version from SwaggerHub | | **Get domain json definition** `swaggerhub_get_domain_json_definition` | Retrieve the OpenAPI definition for a specified domain version in JSON format | | **Get domain lifecycle settings** `swaggerhub_get_domain_lifecycle_settings` | Get the published status for a specific domain and version in SwaggerHub | | **Get domain private settings** `swaggerhub_get_domain_private_settings` | Retrieve the visibility (public or private) of a domain version in SwaggerHub | | **Get domain versions** `swaggerhub_get_domain_versions` | Get a list of domain versions from SwaggerHub | | **Get domain yaml definition** `swaggerhub_get_domain_yaml_definition` | Retrieve the OpenAPI definition for a specified domain version in YAML format from SwaggerHub | | **Get lifecycle settings** `swaggerhub_get_lifecycle_settings` | Get the published status for the specified API and version | | **Get org projects v2** `swaggerhub_get_org_projects_v2` | Get all projects of an organization in SwaggerHub | | **Get organization members** `swaggerhub_get_organization_members` | Retrieve a list of organization members and their roles from SwaggerHub | | **Get organizations** `swaggerhub_get_organizations` | Get organizations for a user | | **Get owner apis** `swaggerhub_get_owner_apis` | Get a list of APIs for a specified owner in SwaggerHub | | **Get owner domains** `swaggerhub_get_owner_domains` | Retrieve domains owned by a specific SwaggerHub user or organization | | **Get portal** `swaggerhub_get_portal` | Retrieve information about a portal | | **Get portal access requests** `swaggerhub_get_portal_access_requests` | Retrieve access requests for a portal in SwaggerHub | | **Get portal attachment** `swaggerhub_get_portal_attachment` | Get informational attachment metadata from SwaggerHub Portal | | **Get portal product** `swaggerhub_get_portal_product` | Retrieve detailed information about a specific product resource | | **Get portal products** `swaggerhub_get_portal_products` | Get products for a specific portal that match your criteria | | **Get portal templates** `swaggerhub_get_portal_templates` | Get templates for a specific portal that match your criteria | | **Get portals** `swaggerhub_get_portals` | Search for available portals | | **Get private settings** `swaggerhub_get_private_settings` | Get the visibility (public or private) of an API version | | **Get resource types** `swaggerhub_get_resource_types` | List available resource types and assignable roles for each in a SwaggerHub organization | | **Get templates** `swaggerhub_get_templates` | Retrieve a list of templates for an owner in SwaggerHub | | **Get user roles** `swaggerhub_get_user_roles` | Retrieve all roles assigned to a user across organization resources in SwaggerHub | | **Get yaml definition** `swaggerhub_get_yaml_definition` | Get the OpenAPI definition in YAML format for the specified API version from SwaggerHub | ## Example prompts **Get Access Control Users** > Pull the relevant data from Swaggerhub, summarize it in plain English, and point out anything that needs attention. **Get Api Default Version** > Pull the relevant data from Swaggerhub, summarize it in plain English, and point out anything that needs attention. **Get Api Versions** > Pull the relevant data from Swaggerhub, summarize it in plain English, and point out anything that needs attention. **Get Consumer Products** > Pull the relevant data from Swaggerhub, 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 Swaggerhub working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Swaggerhub API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Swaggerhub 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 Swaggerhub. | 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 Swaggerhub actions to the runtime in a format your agent can reliably use. | 44 tools for Swaggerhub are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Swaggerhub 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 Swaggerhub in the browser, and the 44 tools above work from chat. There is no SDK and no config file, and the Swaggerhub 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 Swaggerhub skill but can't call the tools The ClawHub skill teaches OpenClaw about Swaggerhub, but the calls run through the ClawLink plugin and your connected account. Make sure Swaggerhub 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 Swaggerhub 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 Swaggerhub tools Swaggerhub 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 Swaggerhub 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. ### Swaggerhub 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 Swaggerhub has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Swaggerhub integration? Yes. ClawLink is the fastest way to connect OpenClaw to Swaggerhub: link your Swaggerhub account once in the browser and OpenClaw can call the Swaggerhub API through 44 ready-made tools — no custom code or token handling. ### How do I add Swaggerhub to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Swaggerhub skill from ClawHub, then you click Connect in the dashboard to authorize Swaggerhub. OpenClaw calls the tools from the next message — no config files, and the Swaggerhub key you paste is stored server-side instead of in your environment. ### How long does it take to connect Swaggerhub to OpenClaw? About two minutes. Sign in, click Connect next to Swaggerhub in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Swaggerhub 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 Swaggerhub working from chat. ### OpenClaw installed the Swaggerhub skill but can't call the tools The ClawHub skill teaches OpenClaw about Swaggerhub, but the calls run through the ClawLink plugin and your connected account. Make sure Swaggerhub 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 - [GitHub](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [Connect SafetyCulture](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.