# How to connect Lucid to OpenClaw (no API keys) > Connect Lucid to OpenClaw with ClawLink in one click — 35 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/openclaw/lucid The usual route to Lucid 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 Lucid setup: install one ClawHub skill, connect Lucid in the browser, and OpenClaw can call real Lucid 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 Lucid. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Lucid** — 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 lucid # connect Lucid (browser OAuth) npx -y @useclawlink/cli actions lucid # list available actions npx -y @useclawlink/cli run lucid --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 Lucid in the [ClawLink dashboard](https://claw-link.dev/dashboard) — a one-click OAuth approval, no API keys. Verify the connection by asking OpenClaw: > Use Lucid to mcp fetch 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 Lucid is connected in the dashboard, that agent calls the same 35 Lucid 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). ## Lucid MCP for OpenClaw Looking for a Lucid MCP server for OpenClaw? ClawLink connects Lucid to OpenClaw and exposes 35 Lucid 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 Lucid integration](https://claw-link.dev/hermes/lucid) works the same way. ## What the OpenClaw Lucid integration can do 35 Lucid 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 35. ### 30 of 35 Lucid tools for OpenClaw | Tool | What it does | |---|---| | **Mcp fetch** `lucid_mcp_fetch` | Retrieves the structured content of a specific Lucid document by its ID | | **Mcp get mcp resource** `lucid_mcp_get_mcp_resource` | Reads a resource from this MCP server by URI | | **Mcp list document thread comments** `lucid_mcp_list_document_thread_comments` | List comments on a specific collaboration thread of a Lucid document | | **Mcp list document threads** `lucid_mcp_list_document_threads` | List collaboration threads on a Lucid document | | **Mcp lucid export document as png** `lucid_mcp_lucid_export_document_as_png` | Exports a Lucid document page as a PNG image | | **Mcp lucid fetch item image** `lucid_mcp_lucid_fetch_item_image` | Fetches the source image attached to a specific item in a Lucid document | | **Mcp lucid get document metadata** `lucid_mcp_lucid_get_document_metadata` | Get metadata for a Lucid document | | **Mcp lucid list folder contents** `lucid_mcp_lucid_list_folder_contents` | List the documents and subfolders inside a Lucid folder | | **Mcp lucid list integrations** `lucid_mcp_lucid_list_integrations` | List the user's available card integrations and their connection status | | **Mcp lucid search document** `lucid_mcp_lucid_search_document` | Locates regions of a Lucid document that contain specific text | | **Mcp lucid shape details** `lucid_mcp_lucid_shape_details` | Get default size, colors, and advanced/text-area properties for one or more shape classes | | **Mcp lucid shape library** `lucid_mcp_lucid_shape_library` | Discover shapes/blocks available to INSERT into a Lucid document | | **Mcp search** `lucid_mcp_search` | Search the user's Lucid account for documents by title/keyword | | **Mcp lucid create embed** `lucid_mcp__lucid_create_embed` | Internal tool for MCP Apps extension only | | **Mcp lucid create embed session token** `lucid_mcp__lucid_create_embed_session_token` | Internal tool for MCP Apps extension only | | **Mcp lucid add block** `lucid_mcp_lucid_add_block` | Add a new block (shape) to a Lucid document | | **Mcp lucid add dynamic table** `lucid_mcp_lucid_add_dynamic_table` | Add a dynamic table to a Lucid document | | **Mcp lucid add items to dynamic table** `lucid_mcp_lucid_add_items_to_dynamic_table` | Add existing canvas blocks to a dynamic table | | **Mcp lucid add line** `lucid_mcp_lucid_add_line` | Add a new line to a Lucid document, connecting two points or shapes | | **Mcp lucid create diagram from specification** `lucid_mcp_lucid_create_diagram_from_specification` | Creates a Lucid document using the Standard Import format (.lucid file) | | **Mcp lucid create document share link** `lucid_mcp_lucid_create_document_share_link` | Creates a new share link for a document with specified permissions | | **Mcp lucid create erd** `lucid_mcp_lucid_create_erd` | Creates a Lucid document containing a data-backed Entity Relationship Diagram (ERD) | | **Mcp lucid create folder** `lucid_mcp_lucid_create_folder` | Create a new folder in the user's Lucid account | | **Mcp lucid create mind map** `lucid_mcp_lucid_create_mind_map` | Creates a Lucid document containing a mind map from structured node data | | **Mcp lucid create org chart** `lucid_mcp_lucid_create_org_chart` | Creates a Lucidchart document containing an org chart from structured node data | | **Mcp lucid create sequence diagram** `lucid_mcp_lucid_create_sequence_diagram` | Creates a Lucid document containing a UML sequence diagram from PlantUML markup | | **Mcp lucid import integration cards** `lucid_mcp_lucid_import_integration_cards` | Import records from a third-party integration as linked cards | | **Mcp lucid submit feedback** `lucid_mcp_lucid_submit_feedback` | Submits user feedback about the Lucid MCP server to the product team | | **Mcp post document thread comment** `lucid_mcp_post_document_thread_comment` | Post a new comment to an existing thread on a Lucid document | | **Mcp share document with collaborators** `lucid_mcp_share_document_with_collaborators` | Share a Lucid document with collaborators by granting them access | ## Example prompts **Mcp Fetch** > Use Lucid to mcp fetch and walk me through the result in plain English. **Mcp Get Mcp Resource** > Use Lucid to mcp get mcp resource and walk me through the result in plain English. **Mcp List Document Thread Comments** > Use Lucid to mcp list document thread comments and walk me through the result in plain English. **Mcp List Document Threads** > Use Lucid to mcp list document threads and walk me through the result in plain English. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual OAuth app 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 Lucid working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Lucid app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Lucid through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Lucid. | 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 Lucid actions to the runtime in a format your agent can reliably use. | 35 tools for Lucid are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Lucid 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 Lucid in the browser, and the 35 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Lucid skill but can't call the tools The ClawHub skill teaches OpenClaw about Lucid, but the calls run through the ClawLink plugin and your connected account. Make sure Lucid 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 Lucid 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 Lucid tools Lucid 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 Lucid 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. ### Lucid 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. ### OAuth finished in the browser but the account is still missing Try reconnecting Lucid and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete. ### Is there a OpenClaw Lucid integration? Yes. ClawLink is the fastest way to connect OpenClaw to Lucid: link your Lucid account once in the browser and OpenClaw can call the Lucid API through 35 ready-made tools — no custom code or token handling. ### How do I add Lucid to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Lucid skill from ClawHub, then you click Connect in the dashboard to authorize Lucid. OpenClaw calls the tools from the next message — no config files or API keys to manage. ### How long does it take to connect Lucid to OpenClaw? About two minutes. Sign in, click Connect next to Lucid in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Lucid up myself? The alternative to ClawLink is usually manual OAuth app 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 Lucid working from chat. ### OpenClaw installed the Lucid skill but can't call the tools The ClawHub skill teaches OpenClaw about Lucid, but the calls run through the ClawLink plugin and your connected account. Make sure Lucid 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](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. - [OpenClaw ClickUp integration](https://claw-link.dev/openclaw/clickup) — Manage tasks, docs, goals, and sprints