Rollbar

You run a Rollbar MCP server in stdio mode so your AI tools can interact directly with Rollbar data through a lightweight, local process. This setup lets you fetch item details, deployments, versions, top items, and replays, and update item properties without managing HTTP servers or separate services.

How to use

Once you have the MCP server configured, connect your MCP client to the stdio server that runs locally. The server exposes a set of tools you can invoke by name to perform common Rollbar data queries and actions. You can drive workflows like diagnosing item roots causes, listing recent deployments, inspecting version histories, and retrieving session replays. Use descriptive prompts to trigger the corresponding tool, for example asking to fetch item details or to update an item’s status.

Typical usage patterns include: asking for item details and last occurrence, listing deployments, checking top items for a given environment, and retrieving or inspecting a specific replay. You can also update an item’s status or assign it to a user. Make sure you supply your Rollbar access token via the configured environment variable so the server can authenticate requests.

How to install

Prerequisites: You need a working Node.js environment. The setup has been tested with Node 20 and 22.

Create your MCP client configuration to connect to the local stdio server. Use the following configuration for the Claude code client setup as an example.

{
  "mcpServers": {
    "rollbar": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@rollbar/mcp-server@latest"
      ],
      "env": {
        "ROLLBAR_ACCESS_TOKEN": "<project read/write access token>"
      }
    }
  }
}

Additional configuration and notes

Environment variable you must provide is the Rollbar access token. This token should have read and/or write scope for the project you’re querying. If you have a staging or development Rollbar deployment, you can override the API base URL with the ROLLBAR_API_BASE variable.

Examples show how to configure this MCP server with different clients. For example, you can place the same settings into other client configs (Codex, Junie, VS Code) by using the matching MCP server block and environment variable.

The server implements a complete set of tools for interacting with Rollbar data, including fetching item details, deployments, versions, and top items, listing items by environment and status, retrieving session replays, and updating items. Ensure you supply the token before starting interactions.

Available tools

get-item-details

Fetch item details and last occurrence details for a given item number. Supports an optional max_tokens parameter to truncate large responses.

get-deployments

List deployment data for the configured project. Useful for quick checks on recent or failed deployments.

get-version

Fetch version details for a specific version string and environment within the configured project.

get-top-items

Retrieve the top items in the last 24 hours for the given environment and project.

list-items

List items filtered by status, environment, and a search query.

get-replay

Retrieve session replay metadata and payload for a specific session and replay ID. Returns a path to a temporary file or a rollbar:// link depending on delivery mode.

update-item

Update an item’s properties such as status, level, title, assignment, and other fields. Requires write scope.