# How to connect Oksign to Hermes Agent (paste one key, 17 tools) > Connect Oksign to Hermes with ClawLink: paste your Oksign key once and 17 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/oksign Most guides for giving Hermes Agent Oksign 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 Oksign setup: pair once in the browser and your always-on Hermes agent can act on Oksign for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect Hermes to Oksign. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Oksign** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **Paste this into Hermes to set up ClawLink:** > 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 with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait. > 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. **Alternative for any agent (no plugin needed):** if the Hermes Agent 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 oksign # connect Oksign (browser OAuth) npx -y @useclawlink/cli actions oksign # list available actions npx -y @useclawlink/cli run oksign --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above walks Hermes through this. By hand, it is four commands and a browser approval: ```bash 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 test ``` Then connect Oksign in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Oksign API key once. Verify the connection by asking Hermes: > Use Oksign to briefcase retrieve 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Oksign is connected in the dashboard, that agent calls the same 17 Oksign 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). ## Oksign MCP for Hermes Looking for a Oksign MCP server for Hermes Agent? ClawLink connects Oksign to Hermes Agent and exposes 17 Oksign 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 OpenClaw instead? The [OpenClaw Oksign integration](https://claw-link.dev/openclaw/oksign) works the same way. ## What the Hermes Agent Oksign integration can do 17 Oksign tools are ready for Hermes Agent once the account is connected. ### All 17 Oksign tools for Hermes | Tool | What it does | |---|---| | **Briefcase retrieve** `oksign_briefcase_retrieve` | Retrieve a previously uploaded briefcase tokeninfo for consultation | | **Contacts retrieve** `oksign_contacts_retrieve` | Retrieve the list of contacts stored in the account | | **Credits retrieve** `oksign_credits_retrieve` | Retrieve account credit balance and storage information | | **Document exists** `oksign_document_exists` | Check if a signed or unsigned document still exists on the OKSign platform | | **Get active documents** `oksign_get_active_documents` | Retrieve all active document IDs and properties from OKsign account | | **Linked list retrieve** `oksign_linked_list_retrieve` | Retrieve the list of linked signed or source document IDs related to a specific document | | **Users retrieve** `oksign_users_retrieve` | Retrieve the list of users associated with the OkSign account | | **Contacts upload** `oksign_contacts_upload` | Insert or update contact information in the account's contact list | | **Document upload** `oksign_document_upload` | Upload a PDF or Word document to OKSign platform for completion and/or signing | | **Editorexpress create** `oksign_editorexpress_create` | Invoke the OKSign Editor Express for modifying documents and form descriptors | | **Formdesc upload** `oksign_formdesc_upload` | Upload form descriptor defining signature fields and other field types to a document | | **Notifications upload** `oksign_notifications_upload` | Upload notifications defining email(s) and/or SMS(es) to be sent to signer(s) with signing links | | **Org token info update** `oksign_org_token_info_update` | Update organizational token information and settings for the account | | **Briefcase remove** `oksign_briefcase_remove` | Remove a previously created briefcase from OKSign platform | | **Contacts remove** `oksign_contacts_remove` | Remove specified contacts from the account's contact list | | **Document remove** `oksign_document_remove` | Remove a signed or unsigned document from the OKSign platform | | **Signexpress remove** `oksign_signexpress_remove` | Remove a previously uploaded SignExpress tokeninfo JSONObject from the OKSign platform | ## Example prompts **Briefcase Retrieve** > Use Oksign to briefcase retrieve and walk me through the result in plain English. **Contacts Retrieve** > Use Oksign to contacts retrieve and walk me through the result in plain English. **Credits Retrieve** > Use Oksign to credits retrieve and walk me through the result in plain English. **Document Exists** > Use Oksign to document exists 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Oksign working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Oksign API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Oksign 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 Oksign. | 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 Oksign actions to the runtime in a format your agent can reliably use. | 17 tools for Oksign are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Oksign 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 Oksign in the browser, and the 17 tools above work from chat. There is no SDK and no config file, and the Oksign 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. ### Hermes paired but still can't use Oksign 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 Oksign 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 Oksign tools Oksign 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 Oksign 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. ### Oksign 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 Oksign has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a Hermes Agent Oksign integration? Yes. ClawLink is the fastest way to connect Hermes to Oksign: link your Oksign account once in the browser and Hermes Agent can call the Oksign API through 17 ready-made tools — no custom code or token handling. ### How do I connect Oksign 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 Oksign in the dashboard and Hermes can use it from the next message — no config files, and the Oksign key you paste is stored server-side instead of in your environment. ### How long does it take to connect Oksign to Hermes Agent? About two minutes. Sign in, click Connect next to Oksign in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Oksign up myself? The alternative to ClawLink is usually manual API key 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 Oksign working from chat. ### Hermes paired but still can't use Oksign 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`. ## Related - [Connect GitHub](https://claw-link.dev/hermes/github) — Manage repositories, issues, pull requests, and workflows - [Connect PagerDuty](https://claw-link.dev/hermes/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture tools](https://claw-link.dev/hermes/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.