Rollbar MCP Server
The Rollbar MCP Server allows LLMs to interact with Rollbar error tracking data, providing features for monitoring and managing errors, deployments, and users.
Capabilities include:
List and filter error items by status, level, environment, with pagination options
Get detailed error information by item ID, project counter, or occurrence UUID
List and examine error occurrences with filtering options
Manage projects - list all or get specific project details
Access environments for specific projects
View user information - list all or get specific user details
Track deployments - list by project/environment or get specific deployment details
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Rollbar MCP Server list the most recent critical errors in production"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Rollbar MCP Server
A dynamic MCP server implementation for Rollbar API integration, enabling LLMs to interact with Rollbar error tracking data.
Features
List and filter error items
Get detailed error information
View error occurrences
Access project and environment details
Track deployments
List users and teams
Related MCP server: agentvet-mcp
Configuration
Environment Variables
ROLLBAR_PROJECT_TOKEN: Rollbar Project Access Token - Required for APIs to retrieve project error and deployment informationROLLBAR_ACCOUNT_TOKEN: Rollbar Account Access Token - Required for APIs to access account-wide project and user informationROLLBAR_PROJECT_ID: Default project ID (used when not specified in requests) - OptionalROLLBAR_PROJECT_NAME: Default project name for reference - Optional
Note: Depending on the features you use, you'll need either
ROLLBAR_PROJECT_TOKEN,ROLLBAR_ACCOUNT_TOKEN, or both. For full functionality, it's recommended to configure both tokens, but the service will work with only the relevant token for specific APIs.
Required Tokens and API Correspondence Table
API | Required Token |
| ROLLBAR_PROJECT_TOKEN |
| ROLLBAR_PROJECT_TOKEN |
| ROLLBAR_PROJECT_TOKEN |
| ROLLBAR_PROJECT_TOKEN |
| ROLLBAR_PROJECT_TOKEN |
| ROLLBAR_PROJECT_TOKEN |
| ROLLBAR_PROJECT_TOKEN |
| ROLLBAR_PROJECT_TOKEN |
| ROLLBAR_ACCOUNT_TOKEN |
| ROLLBAR_ACCOUNT_TOKEN |
| ROLLBAR_ACCOUNT_TOKEN |
| ROLLBAR_ACCOUNT_TOKEN |
You can obtain Rollbar access tokens as follows:
Log in to your Rollbar account (https://rollbar.com/)
For project tokens: Settings -> Project Access Tokens (for project-level access)
For account tokens: Settings -> Account Access Tokens (for account-level access)
Create a new token with "read" scope
How to use
Cursor Integration
Add to your ~/.cursor/mcp.json:
{
"mcpServers": {
"rollbar-mcp": {
"command": "npx",
"args": ["-y", "@hiyorineko/mcp-rollbar-server"],
"env": {
"ROLLBAR_PROJECT_TOKEN": "YOUR_PROJECT_ACCESS_TOKEN",
"ROLLBAR_ACCOUNT_TOKEN": "YOUR_ACCOUNT_ACCESS_TOKEN",
"ROLLBAR_PROJECT_ID": "YOUR_PROJECT_ID",
"ROLLBAR_PROJECT_NAME": "YOUR_PROJECT_NAME"
}
}
}
}Locally
After cloning this repository, follow these steps to set up the MCP client:
$ cd mcp-rollbar-server
$ npm install
$ npm run buildAdd to your ~/.cursor/mcp.json:
{
"mcpServers": {
"rollbar-mcp": {
"command": "YOUR_NODE_PATH",
"args": ["YOUR_PROJECT_PATH/mcp-rollbar-server/dist/src/index.js"],
"env": {
"ROLLBAR_PROJECT_TOKEN": "YOUR_PROJECT_ACCESS_TOKEN",
"ROLLBAR_ACCOUNT_TOKEN": "YOUR_ACCOUNT_ACCESS_TOKEN",
"ROLLBAR_PROJECT_ID": "YOUR_PROJECT_ID",
"ROLLBAR_PROJECT_NAME": "YOUR_PROJECT_NAME"
}
}
}
}To find the value for "YOUR_NODE_PATH", run which node in your terminal.
Usage Examples
List the most recent errors in my production environment.View Error Details
Get detailed information for error item with ID 12345, including stack trace and recent occurrences.Track Deployments
Show me the recent deployments for project 67890.Filter Errors by Level
List all critical errors that occurred in the last week.Tools
rollbar_list_items
List items (errors) from Rollbar
Input:
status(string, optional): Filter by status (active, resolved, muted, etc.)level(string, optional): Filter by level (critical, error, warning, info, debug)environment(string, optional): Filter by environment (production, staging, etc.)limit(number, optional): Maximum number of items to return (default: 20)page(number, optional): Page number for pagination (default: 1)
Returns: List of error items with details such as counter, level, total occurrences, etc.
rollbar_get_item
Get a specific item (error) from Rollbar using the internal item ID maintained by Rollbar's system.
Input:
id(number): Item ID
Returns: Detailed information about a specific error item
rollbar_get_item_by_counter
Get a specific item by project counter from Rollbar. The counter is the visible ID that appears in the Rollbar UI.
Input:
counter(number): Project counter for the item
Returns: Detailed information about a specific error item identified by its project counter
rollbar_list_occurrences
List occurrences of errors from Rollbar
Input:
itemId(number, optional): Item ID to filter occurrenceslimit(number, optional): Maximum number of occurrences to return (default: 20)page(number, optional): Page number for pagination (default: 1)
Returns: List of error occurrences with detailed information
rollbar_get_occurrence
Get a specific occurrence of an error from Rollbar
Input:
id(string): Occurrence ID
Returns: Detailed information about a specific error occurrence
rollbar_list_projects
List projects from Rollbar
Input: None
Returns: List of projects with their IDs, names, and statuses
rollbar_get_project
Get a specific project from Rollbar
Input:
id(number): Project ID
Returns: Detailed information about a specific project
rollbar_list_environments
List environments from Rollbar
Input:
projectId(number): Project ID
Returns: List of environments for the specified project
rollbar_list_users
List users from Rollbar
Input: None
Returns: List of users with their IDs, usernames, emails, and access levels
rollbar_get_user
Get a specific user from Rollbar
Input:
id(number): User ID
Returns: Detailed information about a specific user
rollbar_list_deploys
List deploys from Rollbar
Input:
projectId(number): Project IDenvironment(string, optional): Environment namelimit(number, optional): Maximum number of deploys to return (default: 20)page(number, optional): Page number for pagination (default: 1)
Returns: List of deploys for the specified project and environment
rollbar_get_deploy
Get a specific deploy from Rollbar
Input:
deployId(number): Deploy ID
Returns: Detailed information about a specific deployment
Available Tools
13 toolsrollbar_get_deployC
Get a specific deploy from Rollbar
Inputs: deployId (required).
rollbar_get_itemB
Get a specific item (error) from Rollbar using the internal item ID maintained by Rollbar's system.
Inputs: id (required).
rollbar_get_item_by_counterA
Get a specific item by project counter from Rollbar. The counter is the visible ID that appears in the Rollbar UI.
Inputs: counter (required).
rollbar_get_item_by_occurrence_uuidA
Get a specific item (error) from Rollbar using an occurrence UUID. The UUID must be from an occurrence that belongs to the item.
Inputs: uuid (required).
rollbar_get_occurrenceC
Get a specific occurrence of an error from Rollbar
Inputs: id (required).
rollbar_get_projectC
Get a specific project from Rollbar
Inputs: id (required).
rollbar_get_userC
Get a specific user from Rollbar
Inputs: id (required).
rollbar_list_deploysC
List deploys from Rollbar
Inputs: projectId (required), environment, limit, page.
rollbar_list_environmentsC
List environments from Rollbar
Inputs: projectId (required).
rollbar_list_itemsC
List items (errors) from Rollbar
Inputs: status, level, environment, limit, +1 more.
rollbar_list_occurrencesC
List occurrences of errors from Rollbar
Inputs: itemId, limit, page.
rollbar_list_projectsB
List projects from Rollbar
Inputs: no named parameters.
rollbar_list_usersB
List users from Rollbar
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 13 tools
Every tool has a clearly distinct purpose with no ambiguity. The tools are organized around specific Rollbar resources (deploys, items, occurrences, projects, users, environments) with clear get vs list operations. Even the three item retrieval methods (by internal ID, counter, or occurrence UUID) are explicitly differentiated in their descriptions.
Perfectly consistent naming pattern throughout all 13 tools. Every tool follows the exact same 'rollbar_verb_noun' structure with consistent snake_case. The verbs (get/list) are used predictably across all resource types.
13 tools is well-scoped for a Rollbar integration server. Each tool earns its place by covering distinct operations across multiple resource types. The count provides comprehensive coverage without being overwhelming for the error monitoring domain.
Excellent coverage of read operations for all core Rollbar resources with consistent get/list pairs. Minor gaps exist in write operations (no create/update/delete tools), but this appears intentional for a monitoring-focused server. Agents can perform most common error investigation workflows.
Maintenance
Related MCP Connectors
MCP server for Sentry - error monitoring, issue tracking, and debugging for AI assistants
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J.
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI agents to retrieve and analyze error reports from a self-hosted Telebugs instance. It provides tools for listing projects, searching error groups, and fetching detailed reports directly from the Telebugs SQLite database.4-
- AlicenseAqualityDmaintenanceMCP server that validates LLM-generated tool-call arguments, lints tool definitions, and produces retry messages for AI assistants.352 npm1MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that provides tools to interact with the LiteLLM proxy API, enabling LLM completions, embeddings, image generation, and admin operations.33 npmMIT
- AlicenseAqualityDmaintenanceMCP server for integrating self-hosted Sentry with AI assistants, enabling project and issue listing, issue details with stack traces, and event retrieval.714 npm1MIT