rollbar-mcp-server

A Model Context Protocol (MCP) server for Rollbar.

Features

This MCP server implements the stdio server type, which means your AI tool (e.g. Claude, Cursor) will run it directly; you don't run a separate process or connect over http.

Configuration

Single Project: Environment variable (single project, backward compatible)

• ROLLBAR_ACCESS_TOKEN: access token for your Rollbar project.
• ROLLBAR_API_BASE (optional): override the API base URL (defaults to https://api.rollbar.com/api/1).

Multiple Project: Config file (single or multiple projects)

Create .rollbar-mcp.json in your working directory or home directory, or set ROLLBAR_CONFIG_FILE to point to a custom path. A checked-in template is available at rollbar-mcp-example.json; copy it to .rollbar-mcp.json and fill in your real tokens.

Single project shorthand:

{ "token": "tok_abc123" }

Multiple projects:

{
  "projects": [
    { "name": "backend",  "token": "tok_abc123" },
    { "name": "frontend", "token": "tok_xyz789" }
  ]
}

Config file lookup order:

1. ROLLBAR_CONFIG_FILE env var
2. .rollbar-mcp.json in current working directory
3. ~/.rollbar-mcp.json in home directory
4. ROLLBAR_ACCESS_TOKEN env var (single project, backward compatible)

If a config file exists but is invalid, the server exits with an error instead of falling back to a lower-priority config source.

Tools

list-projects(): List configured Rollbar projects (names and apiBase only; tokens are never returned). Use this when multiple projects are configured to see which project names you can pass to other tools.

get-item-details(counter, max_tokens?, project?): Given an item number, fetch the item details and last occurrence details. Supports an optional max_tokens parameter (default: 20000) to automatically truncate large occurrence responses. Optional project selects which configured project to use when multiple are defined. Example prompt: Diagnose the root cause of Rollbar item #123456

get-deployments(limit, project?): List deploy data for the given project. Optional project when multiple projects are configured. Example prompt: List the last 5 deployments or Are there any failed deployments?

get-version(version, environment, project?): Fetch version details for the given version string and environment. Optional project when multiple projects are configured.

get-top-items(environment, project?): Fetch the top items in the last 24 hours for the given environment. Optional project when multiple projects are configured.

list-items(status?, level?, environment?, page?, limit?, query?, project?): List items filtered by status, environment, and search query. Optional project when multiple projects are configured.

get-replay(environment, sessionId, replayId, delivery?, project?): Retrieve session replay metadata and payload for a specific session. By default the tool writes the replay JSON to a temporary file (under your system temp directory) and returns the path. Set delivery="resource" to receive a rollbar://replay/<environment>/<sessionId>/<replayId> link for MCP-aware clients. Optional project when multiple projects are configured. delivery="resource" is only supported in single-project mode; when multiple projects are configured, use delivery="file" with a project parameter instead. Example prompt: Fetch the replay 789 from session abc in staging.

update-item(itemId, status?, level?, title?, assignedUserId?, resolvedInVersion?, snoozed?, teamId?, project?): Update an item's properties including status, level, title, assignment, and more. Optional project when multiple projects are configured. Example prompt: Mark Rollbar item #123456 as resolved or Assign item #123456 to user ID 789. (Requires write scope)

How to Use

Tested with node 20 and 22 (nvm use 22).

Claude Code

Configure your .mcp.json as follows.

Us

... View full README on GitHub