How to connect FeedBear to Hermes Agent
Connect FeedBear to Hermes with ClawLink: paste your FeedBear key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine.
FeedBearAPI KEYMCPFeedBear helps product teams collect, organize, and act on customer feedback, feature requests, comments, and changelog updates.. Once connected, Hermes Agent can read and act on FeedBear from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent FeedBear 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 FeedBear setup: pair once in the browser and your always-on Hermes agent can act on FeedBear 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 FeedBear.
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 FeedBear
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with FeedBear?"
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 FeedBear in the ClawLink dashboard — paste your FeedBear API key once.
Verify the connection by asking Hermes:
Pull the relevant data from FeedBear, 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 FeedBear is connected in the dashboard, that agent calls the same 10 FeedBear tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
FeedBear MCP for Hermes
Looking for a FeedBear MCP server for Hermes Agent? ClawLink connects FeedBear to Hermes Agent and exposes 10 FeedBear tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw FeedBear integration works the same way.
What the Hermes Agent FeedBear integration can do
10 FeedBear tools are ready for Hermes Agent once the account is connected. The 9 below are the ones people reach for most; your agent can call all 10.
9 of 10 FeedBear tools for Hermes
| Tool | What it does |
|---|---|
Get board item feedbear_get_board_item | Get the full details of one feedback item from a FeedBear board |
List board items feedbear_list_board_items | List or search feedback items on a FeedBear board, with optional status and sort filters |
List boards feedbear_list_boards | List boards in the connected FeedBear project, optionally including private team-only boards |
List changelog entries feedbear_list_changelog_entries | List published FeedBear changelog entries newest first |
List item comments feedbear_list_item_comments | List non-spam comments on a FeedBear item, newest first, including reply relationships |
List statuses feedbear_list_statuses | List the statuses configured for the connected FeedBear project |
Add item comment feedbear_add_item_comment | Publish a public comment on a FeedBear item as the API key creator |
Create board item feedbear_create_board_item | Create a feedback item on a FeedBear board without notifying users |
Update board item feedbear_update_board_item | Update selected fields of an existing FeedBear board item without notifying voters |
Try it: find the FeedBear tool you need
Browse the 9 FeedBear 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 FeedBear, summarize it in plain English, and point out anything that needs attention.
List the relevant items in FeedBear, group them by priority, and recommend what Hermes should do next.
List the relevant items in FeedBear, group them by priority, and recommend what Hermes should do next.
List the relevant items in FeedBear, group them by priority, and recommend what Hermes should do next.
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 FeedBear working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the FeedBear API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected FeedBear 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 FeedBear. | 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 FeedBear actions to the runtime in a format your agent can reliably use. | 10 tools for FeedBear are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes FeedBear 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 FeedBear in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the FeedBear 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 FeedBear
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 FeedBear 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 FeedBear tools
FeedBear 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 FeedBear 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.
FeedBear 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 FeedBear 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 FeedBear integration?
Yes. ClawLink is the fastest way to connect Hermes to FeedBear: link your FeedBear account once in the browser and Hermes Agent can call the FeedBear API through 10 ready-made tools — no custom code or token handling.
How do I connect FeedBear 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 FeedBear in the dashboard and Hermes can use it from the next message — no config files, and the FeedBear key you paste is stored server-side instead of in your environment.
How long does it take to connect FeedBear to Hermes Agent?
About two minutes. Sign in, click Connect next to FeedBear in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring FeedBear 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 FeedBear working from chat.
Hermes paired but still can't use FeedBear
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
Hermes Zendesk integration
Manage support tickets, macros, users, and organizations
Gleap
Gleap is an all-in-one customer feedback tool for apps and websites, enabling direct communication with users to build better software by discovering their everyday pain points.
Hermes Freshdesk integration
Handle support tickets, contacts, and helpdesk operations