How to connect Productboard to Hermes Agent
Connect Productboard to Hermes with ClawLink in one click — 99 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.
ProductboardOAUTH2MCPCollect feedback, prioritize features, and plan product roadmaps. Once connected, Hermes Agent can read and act on Productboard from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Productboard 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 Productboard setup: pair once in the browser and your always-on Hermes agent can act on Productboard 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 Productboard.
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 Productboard
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Productboard?"
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 Productboard in the ClawLink dashboard — a one-click OAuth approval, no API keys.
Verify the connection by asking Hermes:
Pull the relevant data from Productboard, 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 Productboard is connected in the dashboard, that agent calls the same 99 Productboard tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Productboard MCP for Hermes
Looking for a Productboard MCP server for Hermes Agent? ClawLink connects Productboard to Hermes Agent and exposes 99 Productboard tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Productboard integration works the same way.
What the Hermes Agent Productboard integration can do
99 Productboard 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 99.
30 of 99 Productboard tools for Hermes
| Tool | What it does |
|---|---|
Get component productboard_get_component | Retrieve details of a specific component |
Get custom field value productboard_get_custom_field_value | Retrieve a custom field's value for a specific hierarchy entity |
Get entities configurations v2 productboard_get_entities_configurations_v2 | Retrieve entity configuration for a specific type |
Get entities v2 productboard_get_entities_v2 | Retrieve a PM entity using the v2 API |
Get feature release assignment productboard_get_feature_release_assignment | Retrieve a specific feature release assignment |
Get hierarchy entities custom fields productboard_get_hierarchy_entities_custom_fields | Retrieve a specific custom field definition for hierarchy entities |
Get notes configurations v2 productboard_get_notes_configurations_v2 | Retrieve note configuration by type (simple, conversation, or opportunity) |
Get notes v2 productboard_get_notes_v2 | Retrieve a note using the v2 API |
Get objective productboard_get_objective | Retrieve details of a specific objective |
Get release productboard_get_release | Retrieve details of a specific release by ID |
Get release group productboard_get_release_group | Retrieve details of a specific release group |
Get webhooks productboard_get_webhooks | Retrieve details of a specific webhook subscription |
List analytics member activities v2 productboard_list_analytics_member_activities_v2 | Retrieve member activity analytics data from Productboard |
List companies productboard_list_companies | List companies |
List company fields productboard_list_company_fields | Lists all custom field definitions for companies in your Productboard workspace |
List custom field values productboard_list_custom_field_values | Lists custom field values for hierarchy entities (products, components, features) in |
List custom fields productboard_list_custom_fields | Lists custom field definitions for hierarchy entities (Products, Components, Features) |
List entities configurations v2 productboard_list_entities_configurations_v2 | Retrieve configurations for all entity types in Productboard |
List entities relationships v2 productboard_list_entities_relationships_v2 | Retrieve relationships for an entity in Productboard |
List entities v2 productboard_list_entities_v2 | List entities from Productboard using the v2 API |
List feature initiatives productboard_list_feature_initiatives | List initiatives linked to a given feature |
List feature objectives productboard_list_feature_objectives | Lists all objectives (OKRs) linked to a top-level feature |
List feature release assignments productboard_list_feature_release_assignments | List feature–release assignments |
List feature statuses productboard_list_feature_statuses | List feature statuses |
List feedback form configurations productboard_list_feedback_form_configurations | List feedback form configurations |
List initiatives productboard_list_initiatives | List initiatives from Productboard |
List jira integrations productboard_list_jira_integrations | List Jira integrations |
List key results productboard_list_key_results | List key results from Productboard |
List note tags productboard_list_note_tags | Retrieve all tags associated with a specific Productboard note |
List notes configurations v2 productboard_list_notes_configurations_v2 | List note configurations from Productboard v2 API |
Try it: find the Productboard tool you need
Browse the 30 Productboard 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 Productboard, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Productboard, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Productboard, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Productboard, summarize it in plain English, and point out anything that needs attention.
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 Productboard working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a Productboard app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Productboard 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 Productboard. | 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 Productboard actions to the runtime in a format your agent can reliably use. | 99 tools for Productboard are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Productboard 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 Productboard in the browser, and the 99 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 Productboard
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 Productboard 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 Productboard tools
Productboard 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 Productboard 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.
Productboard 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 Productboard 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 Productboard integration?
Yes. ClawLink is the fastest way to connect Hermes to Productboard: link your Productboard account once in the browser and Hermes Agent can call the Productboard API through 99 ready-made tools — no custom code or token handling.
How do I connect Productboard 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 Productboard 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 Productboard to Hermes Agent?
About two minutes. Sign in, click Connect next to Productboard in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Productboard 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 Productboard working from chat.
Hermes paired but still can't use Productboard
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.
