
hiyorineko/mcp-rollbar-server
Developer tools이 페이지는 AI로 자동 번역되었습니다. 기술적인 세부 사항은 원문을 확인하세요. 원문 보기
MCP server implementation for Rollbar API integration
개요
A dynamic MCP server implementation for Rollbar API integration, enabling LLMs to interact with Rollbar error tracking data. - List and filter error items - Get detailed error information - View error occurrences - Access project and environment details - Track deployments - List users and teams - ROLLBAR_PROJECT_TOKEN: Rollbar Project Access Token - Required for APIs to retrieve project error and deployment information - ROLLBAR_ACCOUNT_TOKEN: Rollbar Account Access Token - Required for APIs to access account-wide project and user information - ROLLBAR_PROJECT_ID: Default project ID (used when not specified in requests) - Optional - ROLLBAR_PROJECT_NAME: Default project name for reference - Optional : 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.
README
원문 README의 일부입니다. 원문 보기.
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
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_list_items |
ROLLBAR_PROJECT_TOKEN |
rollbar_get_item |
ROLLBAR_PROJECT_TOKEN |
rollbar_get_item_by_counter |
ROLLBAR_PROJECT_TOKEN |
rollbar_list_occurrences |
ROLLBAR_PROJECT_TOKEN |
rollbar_get_occurrence |
ROLLBAR_PROJECT_TOKEN |
rollbar_list_environments |
ROLLBAR_PROJECT_TOKEN |
rollbar_list_deploys |
ROLLBAR_PROJECT_TOKEN |
rollbar_get_deploy |
ROLLBAR_PROJECT_TOKEN |
rollbar_list_projects |
ROLLBAR_ACCOUNT_TOKEN |
rollbar_get_project |
ROLLBAR_ACCOUNT_TOKEN |
rollbar_list_users |
ROLLBAR_ACCOUNT_TOKEN |
rollbar_get_user |
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
설치
npx -y @hiyorineko/mcp-rollbar-server설정
{
"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"
}
}
}
}