# How to connect Siteleaf to OpenClaw (paste one key, 35 tools) > Connect Siteleaf to OpenClaw with ClawLink: paste your Siteleaf key once and 35 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/siteleaf The usual route to Siteleaf 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 Siteleaf setup: install one ClawHub skill, connect Siteleaf in the browser, and OpenClaw can call real Siteleaf 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 Siteleaf. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Siteleaf** — 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 siteleaf # connect Siteleaf (browser OAuth) npx -y @useclawlink/cli actions siteleaf # list available actions npx -y @useclawlink/cli run siteleaf --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 Siteleaf in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Siteleaf API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Siteleaf, 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 Siteleaf is connected in the dashboard, that agent calls the same 35 Siteleaf 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). ## Siteleaf MCP for OpenClaw Looking for a Siteleaf MCP server for OpenClaw? ClawLink connects Siteleaf to OpenClaw and exposes 35 Siteleaf 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 Siteleaf integration](https://claw-link.dev/hermes/siteleaf) works the same way. ## What the OpenClaw Siteleaf integration can do 35 Siteleaf tools are ready for OpenClaw once the account is connected. The 29 below are the ones people reach for most; your agent can call all 35. ### 29 of 35 Siteleaf tools for OpenClaw | Tool | What it does | |---|---| | **Get collection** `siteleaf_get_collection` | Get a collection by site ID and collection path | | **Get current user** `siteleaf_get_current_user` | Return the Siteleaf user authenticated by the connected API key | | **Get document** `siteleaf_get_document` | Get a Siteleaf document by ID | | **Get job** `siteleaf_get_job` | Get the complete buffered status stream for a Siteleaf job, including all status events and the | | **Get page** `siteleaf_get_page` | Get a Siteleaf page by ID | | **Get role** `siteleaf_get_role` | Get a Siteleaf site-access role by ID | | **Get site** `siteleaf_get_site` | Get one Siteleaf site by ID, including its settings and current or most recent preview | | **Get site taxonomy** `siteleaf_get_site_taxonomy` | Return the unique post tags and categories used by a Siteleaf site | | **Get source** `siteleaf_get_source` | Get raw source-file metadata or list a source directory for a Siteleaf site | | **List collection files** `siteleaf_list_collection_files` | Search and list static files in a Siteleaf collection with sorting and agent-controlled | | **List collections** `siteleaf_list_collections` | List content collections in a Siteleaf site with agent-controlled pagination | | **List documents** `siteleaf_list_documents` | Search and list documents in a Siteleaf collection with visibility, extension, sorting, and | | **List pages** `siteleaf_list_pages` | Search and list pages in a Siteleaf site with visibility, extension, sorting, and pagination | | **List site users** `siteleaf_list_site_users` | List users who have access to a Siteleaf site with agent-controlled pagination | | **List sites** `siteleaf_list_sites` | List sites accessible to the connected Siteleaf account, with optional sorting and | | **Create collection** `siteleaf_create_collection` | Create a content collection in a Siteleaf site | | **Create collection file** `siteleaf_create_collection_file` | Upload one static file to a Siteleaf collection identified by its path | | **Create document** `siteleaf_create_document` | Create a document in a Siteleaf collection with content, taxonomy, metadata, and visibility | | **Create page** `siteleaf_create_page` | Create a page in a Siteleaf site | | **Create role** `siteleaf_create_role` | Grant a Siteleaf user an admin, publisher, or writer role on a site | | **Create site** `siteleaf_create_site` | Create a Siteleaf site with its domain, timezone, metadata, and defaults | | **Update collection** `siteleaf_update_collection` | Update at least one of a collection's title, path, permalink, output behavior, or metadata | | **Update document** `siteleaf_update_document` | Update at least one of a document's content, path, taxonomy, visibility, metadata, or date | | **Update page** `siteleaf_update_page` | Update at least one of a page's content, path, visibility, metadata, or publication date | | **Update role** `siteleaf_update_role` | Change an existing Siteleaf role to admin, publisher, or writer | | **Update site** `siteleaf_update_site` | Update at least one of a site's title, domain, timezone, metadata, or Jekyll content defaults | | **Upsert source** `siteleaf_upsert_source` | Create or replace one raw source file in a Siteleaf site | | **Cancel job** `siteleaf_cancel_job` | Cancel an active Siteleaf job by job ID | | **Publish site** `siteleaf_publish_site` | Start an asynchronous compile-and-publish job for a Siteleaf site and return its job ID | ## Example prompts **Get Collection** > Pull the relevant data from Siteleaf, summarize it in plain English, and point out anything that needs attention. **Get Current User** > Pull the relevant data from Siteleaf, summarize it in plain English, and point out anything that needs attention. **Get Document** > Pull the relevant data from Siteleaf, summarize it in plain English, and point out anything that needs attention. **Get Job** > Pull the relevant data from Siteleaf, 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 Siteleaf working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Siteleaf API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Siteleaf 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 Siteleaf. | 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 Siteleaf actions to the runtime in a format your agent can reliably use. | 35 tools for Siteleaf are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Siteleaf 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 Siteleaf in the browser, and the 35 tools above work from chat. There is no SDK and no config file, and the Siteleaf 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 Siteleaf skill but can't call the tools The ClawHub skill teaches OpenClaw about Siteleaf, but the calls run through the ClawLink plugin and your connected account. Make sure Siteleaf 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 Siteleaf 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 Siteleaf tools Siteleaf 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 Siteleaf 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. ### Siteleaf 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 Siteleaf has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Siteleaf integration? Yes. ClawLink is the fastest way to connect OpenClaw to Siteleaf: link your Siteleaf account once in the browser and OpenClaw can call the Siteleaf API through 35 ready-made tools — no custom code or token handling. ### How do I add Siteleaf to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Siteleaf skill from ClawHub, then you click Connect in the dashboard to authorize Siteleaf. OpenClaw calls the tools from the next message — no config files, and the Siteleaf key you paste is stored server-side instead of in your environment. ### How long does it take to connect Siteleaf to OpenClaw? About two minutes. Sign in, click Connect next to Siteleaf in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Siteleaf 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 Siteleaf working from chat. ### OpenClaw installed the Siteleaf skill but can't call the tools The ClawHub skill teaches OpenClaw about Siteleaf, but the calls run through the ClawLink plugin and your connected account. Make sure Siteleaf 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 tools](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [Connect 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.