# How to connect Writer to OpenClaw (paste one key, 23 tools) > Connect Writer to OpenClaw with ClawLink: paste your Writer key once and 23 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/writer The usual route to Writer 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 Writer setup: install one ClawHub skill, connect Writer in the browser, and OpenClaw can call real Writer 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 Writer. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Writer** — 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 writer # connect Writer (browser OAuth) npx -y @useclawlink/cli actions writer # list available actions npx -y @useclawlink/cli run writer --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 Writer in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Writer API key once. Verify the connection by asking OpenClaw: > Use Writer to analyze images and walk me through the result in plain English. ### 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 Writer is connected in the dashboard, that agent calls the same 23 Writer 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). ## Writer MCP for OpenClaw Looking for a Writer MCP server for OpenClaw? ClawLink connects Writer to OpenClaw and exposes 23 Writer 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 Writer integration](https://claw-link.dev/hermes/writer) works the same way. ## What the OpenClaw Writer integration can do 23 Writer tools are ready for OpenClaw once the account is connected. The 21 below are the ones people reach for most; your agent can call all 23. ### 21 of 23 Writer tools for OpenClaw | Tool | What it does | |---|---| | **Analyze images** `writer_analyze_images` | Analyze images using Writer's vision capabilities | | **Ask question to knowledge graph** `writer_ask_question_to_knowledge_graph` | Send a question to the knowledge graph and retrieve the answer | | **Chat completion** `writer_chat_completion` | Generate chat-based completions | | **Detect AI content** `writer_detect_ai_content` | Detect whether content was generated by AI | | **Download file** `writer_download_file` | Download the binary content of a file | | **Get file** `writer_get_file` | Retrieve detailed information about a specific file by its ID | | **List applications** `writer_list_applications` | List all no-code agent applications | | **List files** `writer_list_files` | List all uploaded files | | **List graphs** `writer_list_graphs` | Retrieve a list of knowledge graphs | | **List models** `writer_list_models` | List all available language models | | **Medical comprehend** `writer_medical_comprehend` | Extract medical entities and concepts from unstructured clinical text | | **Parse PDF** `writer_parse_pdf` | Parse and extract text content from a previously uploaded PDF file | | **Retrieve graph** `writer_retrieve_graph` | Retrieve a knowledge graph by its ID | | **Text generation** `writer_text_generation` | Generate text based on a given prompt | | **Translate text** `writer_translate_text` | Translate text from one language to another with support for formality, length control, and | | **Web search** `writer_web_search` | Perform a web search | | **Add file to graph** `writer_add_file_to_graph` | Add a file to a knowledge graph for indexing and retrieval | | **Create knowledge graph** `writer_create_knowledge_graph` | Create a new knowledge graph | | **Update graph** `writer_update_graph` | Update an existing knowledge graph | | **Upload file** `writer_upload_file` | Upload a file to Writer | | **Remove file from graph** `writer_remove_file_from_graph` | Remove a file from a Knowledge Graph | ## Example prompts **Analyze Images** > Use Writer to analyze images and walk me through the result in plain English. **Ask Question To Knowledge Graph** > Use Writer to ask question to knowledge graph and walk me through the result in plain English. **Chat Completion** > Use Writer to chat completion and walk me through the result in plain English. **Detect Ai Content** > Use Writer to detect ai content and walk me through the result in plain English. ## 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 Writer working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Writer API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Writer 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 Writer. | 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 Writer actions to the runtime in a format your agent can reliably use. | 23 tools for Writer are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Writer 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 Writer in the browser, and the 23 tools above work from chat. There is no SDK and no config file, and the Writer 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 Writer skill but can't call the tools The ClawHub skill teaches OpenClaw about Writer, but the calls run through the ClawLink plugin and your connected account. Make sure Writer 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 Writer 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 Writer tools Writer 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 Writer 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. ### Writer 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 Writer has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Writer integration? Yes. ClawLink is the fastest way to connect OpenClaw to Writer: link your Writer account once in the browser and OpenClaw can call the Writer API through 23 ready-made tools — no custom code or token handling. ### How do I add Writer to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Writer skill from ClawHub, then you click Connect in the dashboard to authorize Writer. OpenClaw calls the tools from the next message — no config files, and the Writer key you paste is stored server-side instead of in your environment. ### How long does it take to connect Writer to OpenClaw? About two minutes. Sign in, click Connect next to Writer in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Writer 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 Writer working from chat. ### OpenClaw installed the Writer skill but can't call the tools The ClawHub skill teaches OpenClaw about Writer, but the calls run through the ClawLink plugin and your connected account. Make sure Writer 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 - [DataRobot](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. - [Connect 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.