# Airbrake MCP server > Read Airbrake projects, error groups, notices, deploys and stats; mute or unmute error groups. A hosted remote MCP server by usefulapi.io, an independent service (not affiliated with Airbrake). - Server URL: https://airbrake.usefulapi.io/mcp - Transport: Streamable HTTP, OAuth sign-in - Status: live - Page: https://usefulapi.io/airbrake/ ## Connect - Claude (claude.ai, Desktop): Customize → Connectors → Add custom connector, name Airbrake, URL https://airbrake.usefulapi.io/mcp. Prefilled dialog: https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Airbrake&connectorUrl=https%3A%2F%2Fairbrake.usefulapi.io%2Fmcp - Claude Code: `claude mcp add --transport http airbrake https://airbrake.usefulapi.io/mcp`, then run `/mcp` to log in. As a plugin: `claude plugin marketplace add https://usefulapi.io/claude/marketplace.json`, then `claude plugin install airbrake@usefulapi`. - Codex: `codex mcp add airbrake --url https://airbrake.usefulapi.io/mcp`, then `codex mcp login airbrake`. - ChatGPT: Plugins → Add custom MCP server, authentication OAuth. - Cursor, VS Code and other MCP clients: add the URL as a remote MCP server. Add only the URL. Do not add an `Authorization` header or an API key to the client config. The server signs you in with OAuth: the login page asks for your **Airbrake User API key**. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401. ## Before you connect Find it in Airbrake → your avatar (top right) → **Profile** → **User API key**. Use the permanent User API key: a project key can only report errors, and a temporary user token expires. Your key is used only to call the Airbrake API on your behalf and to derive a private account id; it is never shown to anyone. ## Example requests - Show the error groups in my main project ordered by occurrence count. - Show the latest occurrences of the most frequent error in my main project. - Show recent releases in my main project, including their environment and who made them. - Mute the noisy error about timeout warnings in my web app project. ## Pricing - Free: $0, 50 tool calls / month - Pro: $9/mo · $90/yr per user, 10,000 tool calls / month - Pro+: $39/mo · $390/yr per user, 100,000 tool calls / month Each paid plan covers this Airbrake server only. ## Tools (17) ### Read only (11) - `airbrake_list_projects`: List projects. List the Airbrake projects your user can see, with id, name, last deploy, notice total, rejected count, deploy count and resolved/unresolved error-group counts. Start here to get a project\_id. - `airbrake_get_project`: Get a project. Get one Airbrake project: name, last deploy id/time, notice total, rejection count, deploy count and resolved/unresolved error-group counts. - `airbrake_list_groups`: List error groups. List a project's error groups ("errors" in the Airbrake app): each with id, resolved flag, error type/message/backtrace, context (environment, severity, component/action), last notice time, notice counts and last deploy. Sorted by last notice by default; order by notice\_count, weight or created instead. Filter by deploy, archived or muted groups, or creation time. Backtraces are cut to the first 5 frames (set full\_backtraces for all; airbrake\_get\_group shows one group in full). - `airbrake_get_group`: Get an error group. Get one error group in full: resolved flag, every error with its complete backtrace (file, function, line, column), context, last deploy, last notice id/time, notice counts and creation time. - `airbrake_get_group_stats`: Get error group statistics. Occurrence counts over time for one error group: parallel arrays `time`, `accepted` (notices counted) and `limited` (dropped by rate limits), aggregated per period, from `since` until `until` (default now). Use it to see whether an error is spiking or fading. - `airbrake_list_notices`: List notices of an error group. List the individual occurrences (notices) of one error group, newest first: each with id, deploy, errors and backtrace, context (environment, hostname, app version, user, URL, severity, notifier), environment, session and request params, and created time. Optionally only notices of one app version. Backtraces are cut to the first 10 frames unless full\_backtraces is set. - `airbrake_get_notice_status`: Get a notice's processing status. Check what happened to a reported error, by the notice id that Airbrake's create-notice API returned: code = processed (groupId = its error group), rejected (message = why, e.g. an app-version filter), archived (past retention) or not\_found (unknown or still processing). - `airbrake_list_deploys`: List deploys. List a project's tracked deploys: environment, username/email of the deployer, repository, revision (commit) and version. Use it to correlate new errors with a release. - `airbrake_get_deploy`: Get a deploy. Get one deploy: environment, deployer, repository, revision and version. - `airbrake_list_activities`: List project activity. List a project's activity feed: who did what and when (for example group.resolved), with user name, activity, the affected object (trackableType/trackableId) and timestamps. - `airbrake_get_project_stats`: Get project statistics. Error volume over time for a whole project: parallel arrays `time`, `accepted` (notices counted), `limited` (dropped by rate limits) and `overQuota` (dropped over the plan quota), aggregated per period (1m, 5m, 15m, 30m, 2h, 3h, 6h, 12h, 24h). ### Changes data (2) - `airbrake_mute_group`: Mute an error group. WRITE: mute one error group. Airbrake removes it from the default error list and stops ALL notifications for it (email, Slack and other integrations) until it is unmuted. Notices are still recorded. Reversible with airbrake\_unmute\_group. - `airbrake_unmute_group`: Unmute an error group. WRITE: unmute one error group, so it is back in the default error list and its notifications resume. ### Your usefulapi plan (4) - `airbrake_usage_status`: Usage status (free-tier meter). Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. - `airbrake_request_feature`: Request a missing feature. Tell usefulapi that the user needs something the Airbrake tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. - `airbrake_upgrade`: Upgrade to Pro or Pro+. Get a paid plan for Airbrake (the free tier caps monthly usage). Pro: 10,000 tool calls a month, for normal use — plan "monthly" ($9/month) or "yearly" ($90/year, 2 months free). Pro+: 100,000 tool calls a month, for automations and heavy use — plan "plus" ($39/month) or "plus\_yearly" ($390/year). Without a plan it returns both Pro and Pro+, each with a payment link, for the user to choose; with a plan, one link. An existing Pro subscription changes to Pro+ in place: call without confirm first, as the reply states the exact charge for this account (the price difference for the rest of the period, or in a free Pro trial the full Pro+ price, as the trial ends); then call with confirm: true. Cancel any time: the plan then runs to the end of the paid period, so it also suits a one-time job. A link opens Stripe Checkout in the browser; after payment the account upgrades automatically. Does not count against the meter. - `airbrake_cancel_subscription`: Cancel the Pro subscription. Cancel the caller's Airbrake Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run airbrake\_upgrade later to undo the cancel before the period ends. Does not count against the meter. ## FAQ ### What can I do with Airbrake in Claude or ChatGPT? Find the most frequent errors in a project. Inspect one error and its latest occurrences. Check if an error is spiking or fading. Match new errors to a recent deploy. Mute a noisy error or unmute it again. See [what you can do](https://usefulapi.io/airbrake/#uses) for the details. ### Is this an official Airbrake product? No. usefulapi is an independent service. It is not affiliated with or endorsed by Airbrake. The server calls the Airbrake API with your own Airbrake access, so it sees only the data that your account can see. ### Can I connect Airbrake to Claude or ChatGPT? Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See [the setup steps](https://usefulapi.io/airbrake/#connect). ### What do I need to connect? The login page asks for your **Airbrake User API key**. See [Before you connect](https://usefulapi.io/airbrake/#setup) for where to find it. ### Do I put my Airbrake key or an Authorization header in the client config? No. Add only the URL. Do not add an `Authorization` header or an API key to the client config. The server signs you in with OAuth: the login page asks for your **Airbrake User API key**. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401. ### How do you keep my Airbrake credentials? The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Airbrake API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Airbrake. ### Can the AI change my Airbrake data? Yes, if you approve it. 2 of the 13 Airbrake tools can create or change data. The other 11 are marked read-only. Most MCP clients ask you to approve a tool call before it runs. ### What does it cost? The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with 10,000 tool calls / month. Pro+ costs $39/mo or $390/yr, with 100,000 tool calls / month. Each subscription covers this Airbrake server only. Cancel any time: your paid plan then runs to the end of the paid period. Run `airbrake_usage_status` to see how many calls you used. ### How do I subscribe or cancel? Ask the AI to run `airbrake_upgrade` and choose Pro or Pro+, billed monthly or yearly: it returns a Stripe Checkout link. If you already have Pro, ask to change it to Pro+. After you confirm, your existing subscription changes in place, keeps its billing interval and charges the price difference for the rest of the period immediately. To cancel, run `airbrake_cancel_subscription`. Your paid plan continues to the end of the paid period. ### What if a Airbrake tool that I need is missing? Tell the AI what you wanted to do. It can send the request with `airbrake_request_feature`. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day. ### Which AI clients can I use? Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others. ## Links - [Airbrake MCP server page](https://usefulapi.io/airbrake/) - [All servers](https://usefulapi.io/llms.txt) - [Terms of Service](https://usefulapi.io/terms/) - [Privacy Policy](https://usefulapi.io/privacy/) - Support: support@usefulapi.io