How to connect FeedBear to OpenClaw
Connect FeedBear to OpenClaw 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, OpenClaw can read and act on FeedBear from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to FeedBear access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical FeedBear setup: install one ClawHub skill, connect FeedBear in the browser, and OpenClaw can call real FeedBear actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to FeedBear.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect FeedBear
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with FeedBear?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect FeedBear in the ClawLink dashboard — paste your FeedBear API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from FeedBear, summarize it in plain English, and point out anything that needs attention.
Using a different agent?
The OpenClaw 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 OpenClaw
Looking for a FeedBear MCP server for OpenClaw? ClawLink connects FeedBear to OpenClaw and exposes 10 FeedBear tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes FeedBear integration works the same way.
What the OpenClaw FeedBear integration can do
10 FeedBear tools are ready for OpenClaw 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 OpenClaw
| 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 OpenClaw 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 OpenClaw should do next.
List the relevant items in FeedBear, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in FeedBear, group them by priority, and recommend what OpenClaw 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 OpenClaw. 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 OpenClaw 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
OpenClaw installed the FeedBear skill but can't call the tools
The ClawHub skill teaches OpenClaw about FeedBear, but the calls run through the ClawLink plugin and your connected account. Make sure FeedBear is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
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 OpenClaw FeedBear integration?
Yes. ClawLink is the fastest way to connect OpenClaw to FeedBear: link your FeedBear account once in the browser and OpenClaw can call the FeedBear API through 10 ready-made tools — no custom code or token handling.
How do I add FeedBear to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink FeedBear skill from ClawHub, then you click Connect in the dashboard to authorize FeedBear. OpenClaw calls the tools 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 OpenClaw?
About two minutes. Sign in, click Connect next to FeedBear in the dashboard, authenticate, and OpenClaw 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want FeedBear working from chat.
OpenClaw installed the FeedBear skill but can't call the tools
The ClawHub skill teaches OpenClaw about FeedBear, but the calls run through the ClawLink plugin and your connected account. Make sure FeedBear is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Related
Zendesk tools
Manage support tickets, macros, users, and organizations
Gleap tools
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.
Freshdesk
Handle support tickets, contacts, and helpdesk operations