New Relic MCP Server

Created By
@cloudbring10 months ago
Run NRQL, NerdGraph, and REST v2 operations to query data, manage incidents, create synthetics, and annotate deployments — all from your MCP client. A full‑featured New Relic MCP server that goes far beyond basic NRQL. It exposes safe, typed tools for APM discovery, alert policy/incident workflows (including acknowledge), entity search and deep details, creating Synthetics Browser monitors, and New Relic REST v2 coverage for deployments and metrics with region awareness and auto‑pagination.
Overview

Strong coverage across APIs: NRQL, NerdGraph, Entities, Alerts, Synthetics, APM, and REST v2.

Actionable, not just read‑only: Acknowledge incidents; create Synthetics Browser monitors; record and delete deployments (guarded).

Production‑friendly controls: Region selection (US/EU), cursor/page handling, opt‑in auto‑pagination, per‑call account override for multi‑tenant orgs.

Safer UX: Destructive actions require explicit confirmation flags.

Robust quality: Typed schemas, strict input validation, and comprehensive tests (BDD with Gherkin and eval-based checks).

Easy to adopt: Works in Zed, Windsurf, MCP Inspector and via npx; tool discovery works even without creds (auth validated on execution).

Server Config

{
  "mcpServers": {
    "newrelic": {
      "command": "npx",
      "args": [
        "-y",
        "newrelic-mcp"
      ],
      "env": {
        "NEW_RELIC_API_KEY": "your-api-key-here",
        "NEW_RELIC_ACCOUNT_ID": "your-account-id"
      }
    }
  }
}
Project Info
Created At
10 months ago
Updated At
10 months ago
Author Name
@cloudbring
Star
-
Language
-
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)

20 hours ago
Gpt Scrambler

2 days ago