# How to connect ONLYOFFICE DocSpace to OpenClaw (paste one key, 10 tools) > Connect ONLYOFFICE DocSpace to OpenClaw with ClawLink: paste your ONLYOFFICE DocSpace 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/onlyoffice-docspace The usual route to ONLYOFFICE DocSpace 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 ONLYOFFICE DocSpace setup: install one ClawHub skill, connect ONLYOFFICE DocSpace in the browser, and OpenClaw can call real ONLYOFFICE DocSpace 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 ONLYOFFICE DocSpace. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect ONLYOFFICE DocSpace** — 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 onlyoffice-docspace # connect ONLYOFFICE DocSpace (browser OAuth) npx -y @useclawlink/cli actions onlyoffice-docspace # list available actions npx -y @useclawlink/cli run onlyoffice-docspace --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 ONLYOFFICE DocSpace in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your ONLYOFFICE DocSpace API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from ONLYOFFICE DocSpace, 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 ONLYOFFICE DocSpace is connected in the dashboard, that agent calls the same 10 ONLYOFFICE DocSpace 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). ## ONLYOFFICE DocSpace MCP for OpenClaw Looking for a ONLYOFFICE DocSpace MCP server for OpenClaw? ClawLink connects ONLYOFFICE DocSpace to OpenClaw and exposes 10 ONLYOFFICE DocSpace 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 ONLYOFFICE DocSpace integration](https://claw-link.dev/hermes/onlyoffice-docspace) works the same way. ## What the OpenClaw ONLYOFFICE DocSpace integration can do 10 ONLYOFFICE DocSpace 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 ONLYOFFICE DocSpace tools for OpenClaw | Tool | What it does | |---|---| | **Get account context** `onlyoffice_docspace_get_account_context` | Return the connected user's identity, non-secret API-key metadata, available key permissions | | **Get file** `onlyoffice_docspace_get_file` | Return metadata, version information, and effective security flags for one file by ID | | **Get room** `onlyoffice_docspace_get_room` | Return detailed metadata and effective security flags for one room by ID | | **List folder items** `onlyoffice_docspace_list_folder_items` | List files and subfolders in My Documents or a folder selected by numeric ID, with optional | | **List groups** `onlyoffice_docspace_list_groups` | List or search DocSpace groups, optionally restricted to groups associated with a user or | | **List people** `onlyoffice_docspace_list_people` | List visible DocSpace users, optionally filtering by text, group membership, or administrator | | **List rooms** `onlyoffice_docspace_list_rooms` | List rooms visible to the connected account, optionally filtering by text and continuing from a | | **Create folder** `onlyoffice_docspace_create_folder` | Create a named subfolder inside an existing DocSpace folder | | **Create text file** `onlyoffice_docspace_create_text_file` | Create a plain-text file with supplied content inside a DocSpace folder | ## Example prompts **Get Account Context** > Pull the relevant data from ONLYOFFICE DocSpace, summarize it in plain English, and point out anything that needs attention. **Get File** > Pull the relevant data from ONLYOFFICE DocSpace, summarize it in plain English, and point out anything that needs attention. **Get Room** > Pull the relevant data from ONLYOFFICE DocSpace, summarize it in plain English, and point out anything that needs attention. **List Folder Items** > List the relevant items in ONLYOFFICE DocSpace, 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 ONLYOFFICE DocSpace working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the ONLYOFFICE DocSpace API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected ONLYOFFICE DocSpace 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 ONLYOFFICE DocSpace. | 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 ONLYOFFICE DocSpace actions to the runtime in a format your agent can reliably use. | 10 tools for ONLYOFFICE DocSpace are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes ONLYOFFICE DocSpace 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 ONLYOFFICE DocSpace in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the ONLYOFFICE DocSpace 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 ONLYOFFICE DocSpace skill but can't call the tools The ClawHub skill teaches OpenClaw about ONLYOFFICE DocSpace, but the calls run through the ClawLink plugin and your connected account. Make sure ONLYOFFICE DocSpace 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 ONLYOFFICE DocSpace 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 ONLYOFFICE DocSpace tools ONLYOFFICE DocSpace 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 ONLYOFFICE DocSpace 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. ### ONLYOFFICE DocSpace 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 ONLYOFFICE DocSpace has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw ONLYOFFICE DocSpace integration? Yes. ClawLink is the fastest way to connect OpenClaw to ONLYOFFICE DocSpace: link your ONLYOFFICE DocSpace account once in the browser and OpenClaw can call the ONLYOFFICE DocSpace API through 10 ready-made tools — no custom code or token handling. ### How do I add ONLYOFFICE DocSpace to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink ONLYOFFICE DocSpace skill from ClawHub, then you click Connect in the dashboard to authorize ONLYOFFICE DocSpace. OpenClaw calls the tools from the next message — no config files, and the ONLYOFFICE DocSpace key you paste is stored server-side instead of in your environment. ### How long does it take to connect ONLYOFFICE DocSpace to OpenClaw? About two minutes. Sign in, click Connect next to ONLYOFFICE DocSpace in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring ONLYOFFICE DocSpace 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 ONLYOFFICE DocSpace working from chat. ### OpenClaw installed the ONLYOFFICE DocSpace skill but can't call the tools The ClawHub skill teaches OpenClaw about ONLYOFFICE DocSpace, but the calls run through the ClawLink plugin and your connected account. Make sure ONLYOFFICE DocSpace 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 Box integration](https://claw-link.dev/openclaw/box) — Store, share, and manage files and folders - [OpenClaw Supabase integration](https://claw-link.dev/openclaw/supabase) — Query and manage Postgres databases - [Dropbox tools](https://claw-link.dev/openclaw/dropbox) — Store, sync, and share files