ClawLink

How to connect Bugherd to Hermes Agent

Connect Bugherd to Hermes with ClawLink: paste your Bugherd key once and 26 tools work from chat. No MCP server to run, nothing stored on your machine.

Get started for free
Hermes Agent
Hermes Agent
ClawLink
ClawLink
Bugherd
Bugherd
BugherdAPI KEYMCP

BugHerd is a visual feedback and bug tracking tool for websites, allowing clients and teams to report issues directly on live sites.. Once connected, Hermes Agent can read and act on Bugherd from chat — pairing, token refresh, and tool wiring handled for you.

26 tools

Most guides for giving Hermes Agent Bugherd 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 Bugherd setup: pair once in the browser and your always-on Hermes agent can act on Bugherd 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 Bugherd.

  1. 1

    Install and pair

    Install the ClawLink plugin, then pair Hermes with a one-time browser approval:

    hermes plugins install ClawLink-HQ/hermes-plugin --enable
  2. 2

    Connect Bugherd

    Paste your API key in the dashboard.

  3. 3

    Use it from chat

    Ask Hermes Agent: "What can you do with Bugherd?"

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 test

Then connect Bugherd in the ClawLink dashboard — paste your Bugherd API key once.

Verify the connection by asking Hermes:

List the relevant items in Bugherd, group them by priority, and recommend what Hermes should do next.

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 login

login opens the same browser approval and stores a credential locally. Once Bugherd is connected in the dashboard, that agent calls the same 26 Bugherd tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.

Bugherd MCP for Hermes

Looking for a Bugherd MCP server for Hermes Agent? ClawLink connects Bugherd to Hermes Agent and exposes 26 Bugherd tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Bugherd integration works the same way.

What the Hermes Agent Bugherd integration can do

26 Bugherd tools are ready for Hermes Agent once the account is connected. The 25 below are the ones people reach for most; your agent can call all 26.

25 of 26 Bugherd tools for Hermes

ToolWhat it does
List active projects bugherd_list_active_projectsList all active projects in your BugHerd account
List attachments bugherd_list_attachmentsList all attachments for a task
List columns bugherd_list_columnsList all columns for a project
List project tasks bugherd_list_project_tasksList tasks within a specific BugHerd project with optional server-side filters (status/column
List projects bugherd_list_projectsRetrieves a paginated list of all projects in your BugHerd account
List users bugherd_list_usersList all users in your account
List webhooks bugherd_list_webhooksList all installed webhooks
Show attachment bugherd_show_attachmentRetrieve details of a specific attachment
Show column bugherd_show_columnShow details of a specific column
Show organization bugherd_show_organizationRetrieve your BugHerd organization details
Show project bugherd_show_projectRetrieves full details of a specific BugHerd project by ID
Show user projects bugherd_show_user_projectsList all projects a specific user has access to
Show user tasks bugherd_show_user_tasksRetrieves all tasks created by or assigned to a specific user, grouped by project
Add guest to project bugherd_add_guest_to_projectAdd a guest (client) to a project
Add member to project bugherd_add_member_to_projectAdd a member to a project in BugHerd
Create attachment bugherd_create_attachmentAdd a new attachment to a task using an existing URL
Create column bugherd_create_columnCreate a new column in a project
Create comment bugherd_create_commentAdd a new comment to a task
Create project bugherd_create_projectCreate a new project
Create task bugherd_create_taskAdd a new task in a project
Create webhook bugherd_create_webhookCreate a new webhook for real-time event notifications
Update column bugherd_update_columnUpdate a column in a project
Update project bugherd_update_projectUpdate settings for an existing BugHerd project
Update task bugherd_update_taskUpdate a task in a project
Upload attachment bugherd_upload_attachmentUpload a new attachment and add it to a specific task

Try it: find the Bugherd tool you need

Browse the 25 Bugherd tools

Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.

Example prompts

List the relevant items in Bugherd, group them by priority, and recommend what Hermes should do next.

List the relevant items in Bugherd, group them by priority, and recommend what Hermes should do next.

List the relevant items in Bugherd, group them by priority, and recommend what Hermes should do next.

List the relevant items in Bugherd, group them by priority, and recommend what Hermes should do next.

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 Bugherd working from chat.

ManualClawLink
Credential handlingCollect, validate, store, and rotate the Bugherd API key yourself, then make sure every tool call uses the right account.Users complete the hosted ClawLink setup once and the connected Bugherd account becomes available to the agent without you building credential management.
Ongoing maintenanceYou own refresh logic, permission debugging, environment config, and every provider-specific edge case for Bugherd.ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure.
Agent usabilityYou still need to expose the right Bugherd actions to the runtime in a format your agent can reliably use.26 tools for Bugherd are already exposed through ClawLink, so the agent can read and act from chat immediately.

Composio also exposes Bugherd 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 Bugherd in the browser, and the 26 tools above work from chat. There is no SDK and no config file, and the Bugherd 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 Bugherd

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 Bugherd 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 Bugherd tools

Bugherd 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 Bugherd 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.

Bugherd 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 Bugherd 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 Bugherd integration?

Yes. ClawLink is the fastest way to connect Hermes to Bugherd: link your Bugherd account once in the browser and Hermes Agent can call the Bugherd API through 26 ready-made tools — no custom code or token handling.

How do I connect Bugherd 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 Bugherd in the dashboard and Hermes can use it from the next message — no config files, and the Bugherd key you paste is stored server-side instead of in your environment.

How long does it take to connect Bugherd to Hermes Agent?

About two minutes. Sign in, click Connect next to Bugherd in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

Why use ClawLink instead of wiring Bugherd 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 Bugherd working from chat.

Hermes paired but still can't use Bugherd

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.