Rollbar MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ROLLBAR_API_BASE | No | Override the Rollbar API base URL (defaults to `https://api.rollbar.com/api/1`). Use this when running against a staging or development Rollbar deployment. | https://api.rollbar.com/api/1 |
| ROLLBAR_ACCESS_TOKEN | Yes | An access token for your Rollbar project with `read` and/or `write` scope |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-item-detailsC | Get item details for a Rollbar item |
| get-deploymentsC | Get deployments data from Rollbar |
| get-versionC | Get version details for a Rollbar project |
| get-top-itemsC | Get list of top items in the Rollbar project |
| list-itemsC | List all items in the Rollbar project with optional search and filtering |
| update-itemC | Update an item in Rollbar (status, level, title, assignment, etc.) |
| get-replayC | Get replay data for a specific session replay in Rollbar |
| list-projectsB | List configured Rollbar projects available to this MCP server |
| list-occurrencesC | List occurrences (instances) for a Rollbar item by counter |
| list-item-eventsA | List an item's history, oldest first, including system events. Requires read scope and project view permission. Omit type for all available event types. Resolve notes are in item_status_history.comment, not item_comment. This lists history, not error occurrences. |
| post-item-commentA | Post a comment as the connected Rollbar user. Requires a configured user token with read and write scope and project comment permission. May notify subscribers. The backend limits the full stored comment data to 65,535 bytes. Do not automatically retry an uncertain result: this operation is not idempotent. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Most tools are clearly distinct (list-item-events vs list-occurrences well-differentiated; get-top-items vs list-items differentiated by ranking/existence). However, get-item-details and list-items could be slightly confused, and get-deployments/get-version are distinct enough.
Mixed conventions: some use hyphens (list-item-events) while others use underscores (update-item, get_deployments—wait, all appear hyphenated in the given list except 'get-top-items' etc. Actually all use hyphens but structure varies: 'list-item-events' vs 'list_items' is not present; the inconsistency is verb_noun vs noun_verb and some use 'item' while others omit. For example: list-item-events, post-item-comment, get-item-details, get-deployments, get-version, get-top-items, list-items, update-item, get-replay, list-projects, list-occurrences. Mostly verb_noun but with inconsistent hyphenation and some use 'item' as a separate token. Still readable.
11 tools is a reasonable count for a Rollbar MCP server, covering key operations. Slightly heavy but each tool addresses a distinct need (items, occurrences, comments, events, deployments, versions, replays, projects).
Covers item lifecycle (list, get details, update, list occurrences, list events, post comment), deployments, versions, top items, replays, projects. Missing explicit create item (but Rollbar items are created by errors, not API) and delete item may be unnecessary. Minor gaps like no bulk update or item creation, but core workflows covered.