airbrake_get_notice_status — airbrake MCP Tool
airbrake_get_notice_status
(airbrake get notice status) is one of 13 tools on the
airbrake
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call airbrake_get_notice_status from your client
- Claude Code airbrake airbrake_get_notice_status run in your project directory
- Claude Desktop airbrake airbrake_get_notice_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor airbrake airbrake_get_notice_status ~/.cursor/mcp.json
- VS Code airbrake airbrake_get_notice_status .vscode/mcp.json
- Zed airbrake airbrake_get_notice_status ~/.config/zed/settings.json
- Windsurf airbrake airbrake_get_notice_status ~/.codeium/windsurf/mcp_config.json
- Cline airbrake airbrake_get_notice_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI airbrake airbrake_get_notice_status ~/.gemini/settings.json
- Grok airbrake airbrake_get_notice_status .mcp.json (in your project root)
- ChatGPT airbrake airbrake_get_notice_status Settings → Connectors → Advanced → Developer mode
- Claude.ai airbrake airbrake_get_notice_status Settings → Connectors → Add custom connector
- LangChain airbrake airbrake_get_notice_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http airbrake https://airbrake.usefulapi.io/mcp
Other tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 8 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.