# How to connect Bugherd to OpenClaw (paste one key, 26 tools) > Connect Bugherd to OpenClaw with ClawLink: paste your Bugherd key once and 26 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/bugherd The usual route to Bugherd 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 Bugherd setup: install one ClawHub skill, connect Bugherd in the browser, and OpenClaw can call real Bugherd 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 Bugherd. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Bugherd** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect bugherd # connect Bugherd (browser OAuth) npx -y @useclawlink/cli actions bugherd # list available actions npx -y @useclawlink/cli run bugherd --input '' # execute (add --confirm for writes) ``` ### 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: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then 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 Bugherd in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Bugherd API key once. Verify the connection by asking OpenClaw: > List the relevant items in Bugherd, group them by priority, and recommend what OpenClaw should do next. ### 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: ```bash 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](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Bugherd MCP for OpenClaw Looking for a Bugherd MCP server for OpenClaw? ClawLink connects Bugherd to OpenClaw and exposes 26 Bugherd tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Bugherd integration](https://claw-link.dev/hermes/bugherd) works the same way. ## What the OpenClaw Bugherd integration can do 26 Bugherd tools are ready for OpenClaw 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 OpenClaw | Tool | What it does | |---|---| | **List active projects** `bugherd_list_active_projects` | List all active projects in your BugHerd account | | **List attachments** `bugherd_list_attachments` | List all attachments for a task | | **List columns** `bugherd_list_columns` | List all columns for a project | | **List project tasks** `bugherd_list_project_tasks` | List tasks within a specific BugHerd project with optional server-side filters (status/column | | **List projects** `bugherd_list_projects` | Retrieves a paginated list of all projects in your BugHerd account | | **List users** `bugherd_list_users` | List all users in your account | | **List webhooks** `bugherd_list_webhooks` | List all installed webhooks | | **Show attachment** `bugherd_show_attachment` | Retrieve details of a specific attachment | | **Show column** `bugherd_show_column` | Show details of a specific column | | **Show organization** `bugherd_show_organization` | Retrieve your BugHerd organization details | | **Show project** `bugherd_show_project` | Retrieves full details of a specific BugHerd project by ID | | **Show user projects** `bugherd_show_user_projects` | List all projects a specific user has access to | | **Show user tasks** `bugherd_show_user_tasks` | Retrieves all tasks created by or assigned to a specific user, grouped by project | | **Add guest to project** `bugherd_add_guest_to_project` | Add a guest (client) to a project | | **Add member to project** `bugherd_add_member_to_project` | Add a member to a project in BugHerd | | **Create attachment** `bugherd_create_attachment` | Add a new attachment to a task using an existing URL | | **Create column** `bugherd_create_column` | Create a new column in a project | | **Create comment** `bugherd_create_comment` | Add a new comment to a task | | **Create project** `bugherd_create_project` | Create a new project | | **Create task** `bugherd_create_task` | Add a new task in a project | | **Create webhook** `bugherd_create_webhook` | Create a new webhook for real-time event notifications | | **Update column** `bugherd_update_column` | Update a column in a project | | **Update project** `bugherd_update_project` | Update settings for an existing BugHerd project | | **Update task** `bugherd_update_task` | Update a task in a project | | **Upload attachment** `bugherd_upload_attachment` | Upload a new attachment and add it to a specific task | ## Example prompts **List Active Projects** > List the relevant items in Bugherd, group them by priority, and recommend what OpenClaw should do next. **List Attachments** > List the relevant items in Bugherd, group them by priority, and recommend what OpenClaw should do next. **List Columns** > List the relevant items in Bugherd, group them by priority, and recommend what OpenClaw should do next. **List Project Tasks** > List the relevant items in Bugherd, 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 Bugherd working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, 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 maintenance** | You 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 usability** | You 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. | ## ClawLink vs. Composio 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 OpenClaw 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](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Bugherd skill but can't call the tools The ClawHub skill teaches OpenClaw about Bugherd, but the calls run through the ClawLink plugin and your connected account. Make sure Bugherd 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 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. ### Is there a OpenClaw Bugherd integration? Yes. ClawLink is the fastest way to connect OpenClaw to Bugherd: link your Bugherd account once in the browser and OpenClaw can call the Bugherd API through 26 ready-made tools — no custom code or token handling. ### How do I add Bugherd to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Bugherd skill from ClawHub, then you click Connect in the dashboard to authorize Bugherd. OpenClaw calls the tools 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 OpenClaw? About two minutes. Sign in, click Connect next to Bugherd in the dashboard, authenticate, and OpenClaw 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Bugherd working from chat. ### OpenClaw installed the Bugherd skill but can't call the tools The ClawHub skill teaches OpenClaw about Bugherd, but the calls run through the ClawLink plugin and your connected account. Make sure Bugherd 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 - [OpenClaw GitHub integration](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [Connect PagerDuty](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.