Rollbar Mcp Server

A Model Context Protocol (MCP) server forRollbar.

{ "accountToken": "acct_tok_abc123" }

{ "accountToken": "acct_tok_abc123", "projects": [ { "name": "backend", "token": "tok_backend_readwrite" } ] }

Project-token configs are completely unchanged by this feature: if you don't set an account token, nothing about existing single- or multi-project setups behaves any differently. The two modes can also coexist: if aprojectname matches an explicitly configured project that has its own token, that project's own token is always used for that project, even when an account token is also present.

Per-project configuration for more secure access

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

Create.rollbar-mcp.jsonin your working directory or home directory, or setROLLBAR_CONFIG_FILEto point to a custom path. A checked-in template is available atrollbar-mcp-example.json; copy it to.rollbar-mcp.jsonand fill in your real tokens.

{ "token": "tok_abc123" }

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

- ROLLBAR_CONFIG_FILEenv var
- .rollbar-mcp.jsonin current working directory
- ~/.rollbar-mcp.jsonin home directory
- ROLLBAR_ACCESS_TOKENorROLLBAR_ACCOUNT_ACCESS_TOKENenv var (single project or account-wide, 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.

- Read-only tools (get-item-details,get-deployments,get-version,get-top-items,list-items,get-replay,list-projects,list-occurrences) work with aread-scope account token.
- update-itemrequires an account token withboth read and writescope: every account-token call resolves the target project viaGET /projectsfirst (read), then makes thePATCHrequest (write). A write-only token will fail at the project-resolution step before ever reaching the update.
- As with project tokens, prefer a read-scope token unless you specifically needupdate-item.

If the server detects onlyROLLBAR_ACCESS_TOKENis set (no explicit account token), it makes a one-time, cached check againstGET /projectsto see whether that token is actually an account token; if so, account mode activates automatically. A single project-scoped token continues to work exactly as before.

list-projects(): See which Rollbar projects this server can talk to. If you're using a single project token, this just confirms the one project you've configured. If you're using an account token that can reach multiple projects, this is how you find the project name or id to pass into the other tools'projectparameter.

get-item-details(counter, max_tokens?, project?): Get the full picture on a single Rollbar item: its details plus its most recent occurrence, so you don't have to look up the item and then separately fetch the latest error. Give it the item's counter (the number you see in the Rollbar UI).

max_tokens(default 20000) caps how large the occurrence data in the response can get. Some occurrences carry a lot of detail (long stack traces, request data), so this keeps a single item lookup from ballooning the response. Optionalprojectselects which project to use, by configured name or by real project name/id in account-token mode. Example prompt:Diagnose the root cause of Rollbar item #123456

get-deployments(limit, project?): List recent deploys for a project, so you can line up when a deploy went out against when errors started or stopped happening. Optionalprojectwhen multiple projects are configured or in account-token mode. Example prompt:List the last 5 deploymentsorAre there any failed deployments?

get-version(version, environment, project?): Look up how a specific version (like a git SHA) has performed in an environment, including when it first and last showed up in occurrences. Useful for checking whether a particular release introduced or fixed an issue. Optionalprojectwhen multiple projects are configured or in account-token mode.

get-top-items(environment, project?): See what's actually breaking right now. Returns the items with the most occurrences in the last 24 hours for the given environment, so you can triage what to look at first instead of scanning the full item list. Optionalprojectwhen multiple projects are configured or in account-token mode.

list-items(status?, level?, environment?, page?, limit?, query?, project?): Search and filter Rollbar items instead of pulling the whole list. Filter bystatus(defaultactive, so resolved and muted items stay out of your way),level, andenvironment, or search byquerytext. Usepageandlimitto control how much comes back at once. Optionalprojectwhen multiple projects are configured or in account-token mode.

list-occurrences(counter, limit?, page?, last_id?, max_tokens?, project?): Look up the actual occurrences behind a Rollbar item, not just the item summary. Give it the item's counter and it returns the individual instances, each with its own timestamp, environment, and error detail.

Uselimitto control how many occurrences come back (default 3, max 100), andpageorlast_idto move through more of them.last_idis cursor-based pagination: pass theidof the last occurrence you got back, and you'll get the next batch after it. We added this because plain page numbers can skip or repeat results if occurrences shift around between calls, andlast_iddoesn't have that problem, so use it when you're paging through a lot of occurrences. If you pass both,last_idwins. Occurrences within a page are always ordered by timestamp (newest first), so the last one you see is reliably the right one to hand back aslast_id.

Occurrence data can get big fast, especially for errors with large stack traces or request payloads.max_tokens(default 20000, minimum 100) caps roughly how large the whole response can get, in aboutmax_tokens * 4characters. We built this because without a cap, a handful of occurrences could blow way past what fits in a conversation. Every occurrence you asked for still shows up in the response, though. Instead of dropping any of them to stay under budget, the tool shrinks the biggest ones down step by step, keeping the most useful fields (level, environment, exception message, and similar) for as long as it can before falling back to just an id and timestamp. A top-level_truncationfield tells you when this happened. If yourlimitandmax_tokensgenuinely can't fit even a minimal version of every occurrence, you'll get a clear error telling you to lowerlimitor raisemax_tokens, instead of a silently incomplete page.

Some Rollbar items are actually groups of several items bundled together. Rollbar's public API can't correctly list occurrences for these yet, so calling this tool on a group item returns an explicitgroup_item_not_supportedmessage saying so, instead of quietly showing you an empty list that looks like the item has no occurrences at all.

Optionalprojectwhen multiple projects are configured. Example prompt:Show me the last 3 occurrences of item #24265

get-replay(environment, sessionId, replayId, delivery?, project?): Fetch a session replay's metadata and payload for a specific session, so you can see what a user actually did leading up to an error.

By default (delivery="file"), the replay JSON is written to a temp file on disk and the tool returns the file path. This works everywhere, but the file sticks around until you clean it up yourself. Setdelivery="resource"instead to get back arollbar://link that MCP-aware clients can read directly, with no file left behind, but this only works when the server only ever talks to a single project (either single-project-token mode, or account-token mode with exactly one project). If you're set up for multiple projects, stick withdelivery="file"and passprojectexplicitly.

Optionalprojectwhen multiple projects are configured or in account-token mode. Example prompt:Fetch the replay 789 from session abc in staging.

update-item(itemId, status?, level?, title?, assignedUserId?, resolvedInVersion?, snoozed?, teamId?, project?): Change an item's status, level, title, assignee, resolved version, snooze state, or owning team, so you can act on an item directly instead of switching to the Rollbar UI.

This needs write access: a project token withwritescope, or an account token with bothreadandwritescope. A read-only token will fail here even though it works fine for every other tool. Optionalprojectwhen multiple projects are configured or in account-token mode. Example prompt:Mark Rollbar item #123456 as resolvedorAssign item #123456 to user ID 789.

Using an environment variable (single project):

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

Optionally includeROLLBAR_API_BASEin theenvblock to target a non-production API endpoint.

Using an account access token (every project on the account, no per-project tokens needed):

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

Using a config file (single or multiple projects):

{ "mcpServers": { "rollbar": { "type": "stdio", "command": "npx", "args": ["-y", "@rollbar/mcp-server@latest"], "env": { "ROLLBAR_CONFIG_FILE": "/path/to/.rollbar-mcp.json" } } } }

[mcp_servers.rollbar] command = "npx" args = ["-y", "@rollbar/mcp-server@latest"] env = { "ROLLBAR_ACCESS_TOKEN" = "<project read/write access token>" }

[mcp_servers.rollbar] command = "npx" args = ["-y", "@rollbar/mcp-server@latest"] env = { "ROLLBAR_CONFIG_FILE" = "/path/to/.rollbar-mcp.json" }

Configure your.junie/mcp/mcp.jsonas follows (env var orROLLBAR_CONFIG_FILEfor config file):

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

Configure Cursor’s MCP servers (Cursor Settings → Features → MCP, or search for “MCP” in settings). Use either an environment variable or a config file.

With an environment variable (single project):

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

With a config file (single or multiple projects):

{ "mcpServers": { "rollbar": { "type": "stdio", "command": "npx", "args": ["-y", "@rollbar/mcp-server@latest"], "env": { "ROLLBAR_CONFIG_FILE": "/path/to/.rollbar-mcp.json" } } } }

Restart Cursor (or reload the window) after changing MCP settings. To use a local build instead of npx, see CONTRIBUTING.md.

Configure your.vscode/mcp.jsonas follows (env var orROLLBAR_CONFIG_FILEfor config file):

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

Or using a local development installation, see CONTRIBUTING.md.

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

AI-powered live runtime debugging with Lightrun production context.

Run, debug, and triage tests via natural language across HyperExecute, Automation, SmartUI, and Accessibility on the TestMu AI cloud.

Understand, develop, and debug authorization policies in Oso Cloud.

A comprehensive proxy that combines multiple MCP servers into a single MCP. It provides discovery and management of tools, prompts, resources, and templates across servers, plus a playground for debugging when building MCP servers.

Proxyman MCP allows AI to inspect HTTP traffic, create debugging rules, and control Proxyman - all through natural language conversations.

Debug your remote Node.js and Next.js applications directly from your AI IDE like Cursor.

Live browser debugging for AI assistants — DOM, console, network via MCP.

Drives an Android emulator or a real device over adb: screenshots, UI hierarchy with true device-pixel coordinates, tap and type, app lifecycle, logcat, and Gradle builds and tests.

Interact with Android devices using the Android Debug Bridge (ADB).

Policy-gated MCP tools that let coding agents build, flash, stimulate and observe real embedded hardware (OpenOCD, pyOCD, STM32CubeProgrammer, serial, CAN).