rollbar

This MCP server provides a stdio-based server for interacting with Rollbar data and operations via an MCP-compatible AI tool. It exposes a set of tools that allow you to fetch item details, deployments, version information, and more, by issuing prompts to the connected AI agent. The server runs locally or within an environment where the AI tool can execute the stdio process and exchange prompts and responses directly with the MCP server. Typical usage involves configuring your MCP client to launch the rollbar server via npx and providing a Rollbar access token in the environment so the server can authenticate with the Rollbar API.

Once configured, you can use the available tools by prompting in natural language (for example, asking to fetch the details of a specific Rollbar item, list recent deployments, or retrieve version information) and the MCP server will translate those prompts into the appropriate Rollbar API calls and return structured results. The tools include item detail lookups, deployment listings, version queries, top-item analytics, item listing with filters, replay retrieval, and item updates, enabling both read and write operations when you provide the necessary access scope.

Prerequisites:

• Node.js installed (tested with Node 20/22). If needed, install nvm and use a compatible Node version.
• Internet access to fetch the MCP server package from npm.

Installation steps:

1. Ensure you have a Rollbar access token with the required scopes (read/write as needed).
2. Install and run the MCP server using npx as described in the README example.

Example setup (CLI):

# Ensure you have Node.js installed (recommended: Node 20/22)
node -v

# Run the MCP server for Rollbar using npx (no local installation required)
npx -y @rollbar/mcp-server@latest

Configure your MCP client to point to the stdio server as described in the documentation (see the embedded configuration examples in the README).

Tips and common considerations:

• Provide a valid ROLLBAR_ACCESS_TOKEN with sufficient scope (read and/or write) for the operations you intend to perform.
• If you are targeting a non-production Rollbar instance, set ROLLBAR_API_BASE to the appropriate base URL (e.g., https://rollbar-dev.example.com/api/1).
• The tools support optional parameters, such as max_tokens for item detail expansions and environment filters for item listings and top items.
• When using write operations (e.g., update-item), ensure your token has write scope; otherwise, the request will be rejected.
• The server operates via stdio; your MCP client (Claude, Codex CLI, Junie, VS Code, etc.) should be configured to spawn the npx command with the appropriate environment variables.
• If you encounter authentication or API errors, double-check token validity and API base configuration, and verify network access to the Rollbar API endpoint.
• You can override the API base URL for testing against staging or development environments without changing the client prompts.