Rollbar Mcp Server

Created By
rollbara year ago
The Rollbar MCP Server implements the Model Context Protocol (MCP), letting you run Rollbar-compatible agents in local or custom environments.
Overview

What is rollbar-mcp-server?

rollbar-mcp-server is a pre-release Model Context Protocol (MCP) server designed for integration with Rollbar, allowing AI tools to directly interact with Rollbar's services.

How to use rollbar-mcp-server?

To use rollbar-mcp-server, install the necessary dependencies, build the project, and configure your environment with the required Rollbar access token. You can run the server directly from your AI tool or through VS Code.

Key features of rollbar-mcp-server?

  • Implements the stdio server type for direct AI tool integration.
  • Provides a get-item-details tool to fetch item details from Rollbar.
  • Easy configuration with access tokens for secure access.

Use cases of rollbar-mcp-server?

  1. Fetching details of specific Rollbar items for debugging.
  2. Integrating Rollbar's error tracking with AI tools for automated diagnostics.
  3. Developing custom tools that leverage Rollbar's data in real-time.

FAQ from rollbar-mcp-server?

  • Is rollbar-mcp-server stable for production use?

No, it is currently in pre-release and alpha quality, intended for testing and development.

  • What programming language is rollbar-mcp-server written in?

It is written in TypeScript.

  • How do I configure the Rollbar access token?

You can set the ROLLBAR_ACCESS_TOKEN environment variable in your configuration files.

Server Config

{
  "mcpServers": {
    "rollbar": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@rollbar/mcp-server@latest"
      ],
      "env": {
        "ROLLBAR_ACCESS_TOKEN": "<project read/write access token>"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
7 months ago
Author Name
rollbar
Star
4
Language
TypeScript
License
MIT license
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago