How to connect Lucid to Hermes Agent
Connect Lucid to Hermes with ClawLink in one click — 35 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.
LucidOAUTH2MCPLucid MCP lets agents search, retrieve, summarize, share, export, and create authorized Lucid documents, diagrams, mind maps, sequence diagrams, and org charts.. Once connected, Hermes Agent can read and act on Lucid from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Lucid access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Lucid setup: pair once in the browser and your always-on Hermes agent can act on Lucid for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into Hermes to install the plugin and pair your account.
Set up ClawLink for Hermes and tell me when it's ready.
1. Install the plugin:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
2. Start pairing. It prints an approval link, so show me the link and stop, don't wait:
hermes clawlink begin
3. I'll approve it in my browser, then reply "approved".
4. When I say approved, finish setup:
hermes clawlink finish
5. Then run `hermes clawlink test` and tell me whether ClawLink is ready.Setup
It takes three steps to connect Hermes to Lucid.
1Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable- 2
Connect Lucid
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Lucid?"
Install by command
The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin # prints an approval link — open it and approve
hermes clawlink finish # after approving in the browser
hermes clawlink testThen connect Lucid in the ClawLink dashboard — a one-click OAuth approval, no API keys.
Verify the connection by asking Hermes:
Use Lucid to mcp fetch and walk me through the result in plain English.
Using a different agent?
The Hermes 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:
npx -y @useclawlink/cli loginlogin 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.
Lucid MCP for Hermes
Looking for a Lucid MCP server for Hermes Agent? ClawLink connects Lucid to Hermes Agent and exposes 35 Lucid tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Lucid integration works the same way.
What the Hermes Agent Lucid integration can do
35 Lucid tools are ready for Hermes Agent 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 Hermes
| 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 |
Try it: find the Lucid tool you need
Browse the 30 Lucid tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Use Lucid to mcp fetch and walk me through the result in plain English.
Use Lucid to mcp get mcp resource and walk me through the result in plain English.
Use Lucid to mcp list document thread comments and walk me through the result in plain English.
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 Hermes Agent. 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 Hermes Agent 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 comparison.
Troubleshooting
Hermes paired but still can't use Lucid
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
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.
FAQ
Is there a Hermes Agent Lucid integration?
Yes. ClawLink is the fastest way to connect Hermes to Lucid: link your Lucid account once in the browser and Hermes Agent can call the Lucid API through 35 ready-made tools — no custom code or token handling.
How do I connect Lucid to Hermes with ClawLink?
Install the plugin with hermes plugins install ClawLink-HQ/hermes-plugin --enable, then pair once: run hermes clawlink begin, approve the link in your browser, and run hermes clawlink finish. Connect Lucid in the dashboard and Hermes can use it from the next message — no config files or API keys to manage.
How long does it take to connect Lucid to Hermes Agent?
About two minutes. Sign in, click Connect next to Lucid in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Lucid working from chat.
Hermes paired but still can't use Lucid
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
