How to connect Hub Planner to Hermes Agent
Connect Hub Planner to Hermes with ClawLink: paste your Hub Planner key once and 122 tools work from chat. No MCP server to run, nothing stored on your machine.
Hub PlannerAPI KEYMCPA Modern and Smart Resource Management, Planning & Scheduling tool with Time Sheets and Powerful Reporting.. Once connected, Hermes Agent can read and act on Hub Planner from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Hub Planner 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 Hub Planner setup: pair once in the browser and your always-on Hermes agent can act on Hub Planner 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 Hub Planner.
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 Hub Planner
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Hub Planner?"
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 Hub Planner in the ClawLink dashboard — paste your Hub Planner API key once.
Verify the connection by asking Hermes:
Use Hub Planner to add clients to project 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 Hub Planner is connected in the dashboard, that agent calls the same 122 Hub Planner tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Hub Planner MCP for Hermes
Looking for a Hub Planner MCP server for Hermes Agent? ClawLink connects Hub Planner to Hermes Agent and exposes 122 Hub Planner tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Hub Planner integration works the same way.
What the Hermes Agent Hub Planner integration can do
122 Hub Planner 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 122.
30 of 122 Hub Planner tools for Hermes
| Tool | What it does |
|---|---|
Add clients to project hub_planner_add_clients_to_project | Add clients to a project by project ID |
Add project custom field choices hub_planner_add_project_custom_field_choices | Add choices to a project custom field template of SELECT, RADIO, or CHECKBOX type |
Add project tags hub_planner_add_project_tags | Add tags to a Hub Planner project |
Add projects to group hub_planner_add_projects_to_group | Add projects to a project group in Hub Planner |
Get billing rate hub_planner_get_billing_rate | Retrieve a specific billing rate by ID from Hub Planner |
Get booking hub_planner_get_booking | Retrieve a specific booking by ID from Hub Planner |
Get booking category hub_planner_get_booking_category | Retrieve a specific booking category by ID from Hub Planner |
Get client hub_planner_get_client | Retrieve a specific client by ID from Hub Planner |
Get cost category hub_planner_get_cost_category | Retrieve a specific project cost category by ID from Hub Planner |
Get event hub_planner_get_event | Retrieve a specific event by ID from Hub Planner |
Get holiday hub_planner_get_holiday | Retrieve a specific holiday by ID from Hub Planner |
Get milestone hub_planner_get_milestone | Retrieve a specific milestone by ID from Hub Planner |
Get project hub_planner_get_project | Retrieve a specific project by ID from Hub Planner |
Get project custom field template hub_planner_get_project_custom_field_template | Retrieve a specific project custom field template by ID |
Get project custom field templates hub_planner_get_project_custom_field_templates | Retrieve all project custom field templates defined for your Hub Planner account |
Get project group hub_planner_get_project_group | Retrieve a specific project group by ID from Hub Planner |
Get project tags hub_planner_get_project_tags | Retrieve all tags associated with a specific Hub Planner project |
Get resource hub_planner_get_resource | Retrieve a specific resource by ID from Hub Planner |
Get resource custom field template hub_planner_get_resource_custom_field_template | Retrieve a specific resource custom field template by ID from Hub Planner |
Get resource custom field templates hub_planner_get_resource_custom_field_templates | Retrieve custom field templates defined for resources in your Hub Planner account |
Get resource tags hub_planner_get_resource_tags | Retrieve all tags associated with a specific resource from Hub Planner |
Get time entry hub_planner_get_time_entry | Retrieve a specific time entry by ID from Hub Planner |
Get vacation hub_planner_get_vacation | Retrieve a specific vacation by ID from Hub Planner |
List billing rates hub_planner_list_billing_rates | Retrieve all billing rates from Hub Planner |
List booking categories hub_planner_list_booking_categories | Retrieve all booking categories from Hub Planner |
List bookings hub_planner_list_bookings | Retrieve all bookings from Hub Planner with pagination support |
List category groups hub_planner_list_category_groups | Get all category groups from Hub Planner |
List clients hub_planner_list_clients | Get all clients from Hub Planner |
List cost categories hub_planner_list_cost_categories | Retrieve all project cost categories from Hub Planner |
List events hub_planner_list_events | Retrieve all events from Hub Planner |
Try it: find the Hub Planner tool you need
Browse the 30 Hub Planner tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Use Hub Planner to add clients to project and walk me through the result in plain English.
Use Hub Planner to add project custom field choices and walk me through the result in plain English.
Use Hub Planner to add projects to group 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 Hub Planner working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Hub Planner API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Hub Planner 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 Hub Planner. | 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 Hub Planner actions to the runtime in a format your agent can reliably use. | 122 tools for Hub Planner are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Hub Planner 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 Hub Planner in the browser, and the 122 tools above work from chat. There is no SDK and no config file, and the Hub Planner 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 Hub Planner
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 Hub Planner 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 Hub Planner tools
Hub Planner 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 Hub Planner 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.
Hub Planner 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 Hub Planner 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 Hub Planner integration?
Yes. ClawLink is the fastest way to connect Hermes to Hub Planner: link your Hub Planner account once in the browser and Hermes Agent can call the Hub Planner API through 122 ready-made tools — no custom code or token handling.
How do I connect Hub Planner 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 Hub Planner in the dashboard and Hermes can use it from the next message — no config files, and the Hub Planner key you paste is stored server-side instead of in your environment.
How long does it take to connect Hub Planner to Hermes Agent?
About two minutes. Sign in, click Connect next to Hub Planner in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Hub Planner 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 Hub Planner working from chat.
Hermes paired but still can't use Hub Planner
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.
