# How to connect Bugsnag to OpenClaw (paste one key, 60 tools) > Connect Bugsnag to OpenClaw with ClawLink: paste your Bugsnag key once and 60 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/bugsnag The usual route to Bugsnag 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 Bugsnag setup: install one ClawHub skill, connect Bugsnag in the browser, and OpenClaw can call real Bugsnag 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 Bugsnag. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Bugsnag** — 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 bugsnag # connect Bugsnag (browser OAuth) npx -y @useclawlink/cli actions bugsnag # list available actions npx -y @useclawlink/cli run bugsnag --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 Bugsnag in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Bugsnag API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Bugsnag, 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Bugsnag is connected in the dashboard, that agent calls the same 60 Bugsnag 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). ## Bugsnag MCP for OpenClaw Looking for a Bugsnag MCP server for OpenClaw? ClawLink connects Bugsnag to OpenClaw and exposes 60 Bugsnag 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 Bugsnag integration](https://claw-link.dev/hermes/bugsnag) works the same way. ## What the OpenClaw Bugsnag integration can do 60 Bugsnag tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 60. ### 30 of 60 Bugsnag tools for OpenClaw | Tool | What it does | |---|---| | **Get configured integration** `bugsnag_get_configured_integration` | Retrieve details of a specific configured integration by its ID | | **Get org data deletion** `bugsnag_get_org_data_deletion` | Check the status of an organization event data deletion request in Bugsnag | | **Get organization by ID** `bugsnag_get_organization_by_id` | View an organization by its ID | | **Get organization collaborator project access counts** `bugsnag_get_organization_collaborator_project_access_counts` | View the project count of collaborators in an organization | | **Get organization collaborator projects** `bugsnag_get_organization_collaborator_projects` | View projects a collaborator has access to in an organization | | **Get organization event data request** `bugsnag_get_organization_event_data_request` | Check the status of an organization event data request | | **Get organization team** `bugsnag_get_organization_team` | Show the details of a team in an organization | | **Get pivot values on a project** `bugsnag_get_pivot_values_on_a_project` | List pivot values for a project, showing how events are distributed across different values of | | **Get project data deletion** `bugsnag_get_project_data_deletion` | Check the status of a project event data deletion request in Bugsnag | | **Get project event data request** `bugsnag_get_project_event_data_request` | Check the status of a project event data request | | **Get project network grouping ruleset** `bugsnag_get_project_network_grouping_ruleset` | Retrieve a project's network grouping ruleset | | **Get saved search** `bugsnag_get_saved_search` | Retrieves the details of a specific saved search by its unique ID | | **Get saved search usage summary** `bugsnag_get_saved_search_usage_summary` | Retrieves usage statistics for a saved search, showing how it is being used across the project | | **List collaborator access details for projects** `bugsnag_list_collaborator_access_details_for_projects` | List summary details of the projects a collaborator has access to | | **List collaborators** `bugsnag_list_collaborators` | List collaborators in an organization | | **List collaborators on project** `bugsnag_list_collaborators_on_project` | List collaborators on a project | | **List configured integrations for project** `bugsnag_list_configured_integrations_for_project` | Retrieves all configured integrations for a Bugsnag project | | **List errors on project** `bugsnag_list_errors_on_project` | List all errors in a Bugsnag project with optional filtering and sorting | | **List event fields for project** `bugsnag_list_event_fields_for_project` | Lists all event fields available for filtering and pivoting in a Bugsnag project | | **List events for error** `bugsnag_list_events_for_error` | Lists individual error event occurrences for a specific error group | | **List events on project** `bugsnag_list_events_on_project` | List all error events for a Bugsnag project | | **List organization teams** `bugsnag_list_organization_teams` | List teams in an organization | | **List organizations** `bugsnag_list_organizations` | List organizations for the authenticated user | | **List pivots on project** `bugsnag_list_pivots_on_project` | Lists all pivot field definitions for a Bugsnag project | | **List project feature flag summaries** `bugsnag_list_project_feature_flag_summaries` | List feature flag summaries for a Bugsnag project with optional search filtering | | **List project feature flags** `bugsnag_list_project_feature_flags` | List feature flags on a Bugsnag project for a specific release stage | | **List projects** `bugsnag_list_projects` | List projects in an organization | | **List release groups** `bugsnag_list_release_groups` | List release groups for a project | | **List releases** `bugsnag_list_releases` | List all releases (deployed versions) of a Bugsnag project | | **List saved searches on project** `bugsnag_list_saved_searches_on_project` | Lists all saved searches for a Bugsnag project | ## Example prompts **Get Configured Integration** > Pull the relevant data from Bugsnag, summarize it in plain English, and point out anything that needs attention. **Get Org Data Deletion** > Pull the relevant data from Bugsnag, summarize it in plain English, and point out anything that needs attention. **Get Organization By Id** > Pull the relevant data from Bugsnag, summarize it in plain English, and point out anything that needs attention. **Get Organization Collaborator Project Access Counts** > Pull the relevant data from Bugsnag, summarize it in plain English, and point out anything that needs attention. ## 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 Bugsnag working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Bugsnag API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Bugsnag 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 Bugsnag. | 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 Bugsnag actions to the runtime in a format your agent can reliably use. | 60 tools for Bugsnag are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Bugsnag 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 Bugsnag in the browser, and the 60 tools above work from chat. There is no SDK and no config file, and the Bugsnag 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 Bugsnag skill but can't call the tools The ClawHub skill teaches OpenClaw about Bugsnag, but the calls run through the ClawLink plugin and your connected account. Make sure Bugsnag 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 Bugsnag 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 Bugsnag tools Bugsnag 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 Bugsnag 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. ### Bugsnag 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 Bugsnag has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Bugsnag integration? Yes. ClawLink is the fastest way to connect OpenClaw to Bugsnag: link your Bugsnag account once in the browser and OpenClaw can call the Bugsnag API through 60 ready-made tools — no custom code or token handling. ### How do I add Bugsnag to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Bugsnag skill from ClawHub, then you click Connect in the dashboard to authorize Bugsnag. OpenClaw calls the tools from the next message — no config files, and the Bugsnag key you paste is stored server-side instead of in your environment. ### How long does it take to connect Bugsnag to OpenClaw? About two minutes. Sign in, click Connect next to Bugsnag in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Bugsnag 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 Bugsnag working from chat. ### OpenClaw installed the Bugsnag skill but can't call the tools The ClawHub skill teaches OpenClaw about Bugsnag, but the calls run through the ClawLink plugin and your connected account. Make sure Bugsnag 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 - [Connect GitHub](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [OpenClaw SafetyCulture integration](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.