New Relic NerdGraph MCP Server

Created By
ulucaydina year ago
The Unofficial MCP Server for New Relic (Alpha)
Overview

What is New Relic NerdGraph MCP Server?

The New Relic NerdGraph MCP Server is an unofficial Model Context Protocol (MCP) server designed for interacting with the New Relic NerdGraph API, allowing users to query and manage their New Relic account data using natural language or specific commands.

How to use New Relic NerdGraph MCP Server?

To use the server, clone the repository, install the required dependencies, configure your New Relic API key and account ID as environment variables, and then run the server using the fastmcp command-line tool.

Key features of New Relic NerdGraph MCP Server?

  • Fetch account details and execute generic NerdGraph queries.
  • Run NRQL queries against your account data.
  • Manage entities such as applications and monitors.
  • List APM applications and synthetic monitors.
  • Manage alert policies and incidents.

Use cases of New Relic NerdGraph MCP Server?

  1. Querying account details and performance metrics.
  2. Executing custom NRQL queries for data analysis.
  3. Managing application performance monitoring (APM) applications.
  4. Automating the management of synthetic monitors and alerts.

FAQ from New Relic NerdGraph MCP Server?

  • What is required to run the server?
    You need Python 3.10+, pip, a New Relic account, and a User API key for authentication.

  • Can I use this server for all New Relic features?
    Yes, it exposes various New Relic capabilities, but ensure you have the necessary permissions in your New Relic account.

  • Is this server officially supported by New Relic?
    No, this is an unofficial server created by the community.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ulucaydin
Star
0
Language
Python
License
-

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)

2 days ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago