Rollbar

What it is

Rollbar's own stdio server, launched by your client through npx. It reads a project's items, occurrences, deployments and session replays over the Rollbar API, and can write an item's status back.

What you get

• The items with the most occurrences in the last 24 hours for an environment, so triage starts with the worst one
• An item's full detail together with its most recent occurrence, from the counter shown in the Rollbar UI
• The individual occurrences behind an item, each with its own timestamp, environment and error detail
• Item search and filtering by status, level, environment or free text, with resolved and muted items out of the way by default
• Recent deployments, to line a release up against when errors started or stopped
• How one version — a git SHA — has behaved in an environment, including when it first and last appeared
• A session replay for a session, written to a temp file or returned as a rollbar:// link
• Status, level, title, assignee, resolved version, snooze state and owning team, changed from the conversation
• The list of Rollbar projects this server can reach, to pass into the other tools

Requirements

A Rollbar token. ROLLBAR_ACCOUNT_ACCESS_TOKEN reaches every project on the account; ROLLBAR_ACCESS_TOKEN covers a single project. For several projects with different tokens, point ROLLBAR_CONFIG_FILE at a .rollbar-mcp.json listing them, or drop that file in the working directory or your home directory. Read scope covers every tool except update-item, which needs read and write. Runs over stdio through npx — no separate process to keep alive. ROLLBAR_API_BASE overrides the default https://api.rollbar.com/api/1.

Setup effort

One command plus a key — npx -y @rollbar/mcp-server@latest, then supply credentials

Tools you get

9 tools when we connected. update-item needs an account token with both read and write scope; a read-only token works for every other tool. Tool names are kebab-case, such as get-item-details.

Requires

• npx on PATH
• One of ROLLBAR_ACCESS_TOKEN (one project) or ROLLBAR_ACCOUNT_ACCESS_TOKEN (every project on the account) in your environment, or ROLLBAR_CONFIG_FILE pointing at a .rollbar-mcp.json that lists project tokens

Where it runs

All 6 documented setups run the server on your machine.