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 |
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 9 tools
Most tools target distinct resources/actions (deployments, projects, replays, version, occurrences, item details, update). The only mild overlap is list-items vs get-top-items and list-items vs get-item-details, but descriptions differentiate listing, top-ranked, and detail retrieval clearly enough.
All nine tools follow a consistent snake_case verb_noun pattern (get-deployments, list-items, list-projects, get-item-details, update-item, etc.). No mixing of conventions or vague verbs.
Nine tools is well-scoped for an error-tracking/observability server, covering the main read and update operations without bloat.
The surface is read-heavy with a single write tool (update-item); there is no create/delete for items or deployments and no comment/mute operations, which are common Rollbar lifecycle actions. Core retrieval workflows are covered, but notable gaps remain.