How to connect Worksnaps to Hermes Agent
Connect Worksnaps to Hermes with ClawLink: paste your Worksnaps key once and 14 tools work from chat. No MCP server to run, nothing stored on your machine.
WorksnapsAPI KEYMCPWorksnaps is a time-tracking service designed for remote work that offers detailed project and user activity insights.. Once connected, Hermes Agent can read and act on Worksnaps from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Worksnaps 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 Worksnaps setup: pair once in the browser and your always-on Hermes agent can act on Worksnaps 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 Worksnaps.
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 Worksnaps
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Worksnaps?"
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 Worksnaps in the ClawLink dashboard — paste your Worksnaps API key once.
Verify the connection by asking Hermes:
Pull the relevant data from Worksnaps, summarize it in plain English, and point out anything that needs attention.
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 Worksnaps is connected in the dashboard, that agent calls the same 14 Worksnaps tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Worksnaps MCP for Hermes
Looking for a Worksnaps MCP server for Hermes Agent? ClawLink connects Worksnaps to Hermes Agent and exposes 14 Worksnaps tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Worksnaps integration works the same way.
What the Hermes Agent Worksnaps integration can do
14 Worksnaps tools are ready for Hermes Agent once the account is connected. The 13 below are the ones people reach for most; your agent can call all 14.
13 of 14 Worksnaps tools for Hermes
| Tool | What it does |
|---|---|
Get project details worksnaps_get_project_details | Retrieve details of a specific project |
Get project report worksnaps_get_project_report | Retrieves time entries for a specific project using the Worksnaps Time Entries API |
Get projects worksnaps_get_projects | Retrieve a paginated list of projects |
Get task details worksnaps_get_task_details | Retrieve details of a specific task within a project |
Get tasks worksnaps_get_tasks | Retrieve tasks for a specific project |
Get user account worksnaps_get_user_account | Retrieve information about a specific user account |
Get user assignments worksnaps_get_user_assignments | Retrieve a list of all user assignments for a specific project |
Get users worksnaps_get_users | Retrieves a list of all users in the Worksnaps account |
Create project worksnaps_create_project | Creates a new project in Worksnaps for tracking time and tasks |
Create task worksnaps_create_task | Create a new task in a specified project |
Put update project worksnaps_put_update_project | Update an existing project |
Put update task worksnaps_put_update_task | Update details of an existing task |
Put update user account worksnaps_put_update_user_account | Update information for a specific user account |
Try it: find the Worksnaps tool you need
Browse the 13 Worksnaps tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Worksnaps, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Worksnaps, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Worksnaps, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Worksnaps, summarize it in plain English, and point out anything that needs attention.
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 Worksnaps working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Worksnaps API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Worksnaps 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 Worksnaps. | 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 Worksnaps actions to the runtime in a format your agent can reliably use. | 14 tools for Worksnaps are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Worksnaps 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 Worksnaps in the browser, and the 14 tools above work from chat. There is no SDK and no config file, and the Worksnaps key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
Hermes paired but still can't use Worksnaps
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 Worksnaps 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 Worksnaps tools
Worksnaps 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 Worksnaps 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.
Worksnaps 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 Worksnaps has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a Hermes Agent Worksnaps integration?
Yes. ClawLink is the fastest way to connect Hermes to Worksnaps: link your Worksnaps account once in the browser and Hermes Agent can call the Worksnaps API through 14 ready-made tools — no custom code or token handling.
How do I connect Worksnaps 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 Worksnaps in the dashboard and Hermes can use it from the next message — no config files, and the Worksnaps key you paste is stored server-side instead of in your environment.
How long does it take to connect Worksnaps to Hermes Agent?
About two minutes. Sign in, click Connect next to Worksnaps in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Worksnaps 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 Worksnaps working from chat.
Hermes paired but still can't use Worksnaps
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.
