Developer · Local MCP server
New Relic MCP Server
Secure, self-hosted New Relic observability and administration tools for MCP clients.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Meet-Bhalodiya/newrelic-mcp- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-08-18
- Updated
- 2026-08-18
- Publisher
- Meet-Bhalodiya (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Meet-Bhalodiya) · how
- Listed under
- New Relic MCP servers
- Website
- github.com/Meet-Bhalodiya/newrelic-mcp#readme
- Repository
- github.com/Meet-Bhalodiya/newrelic-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | @meet-bhalodiya/newrelic-mcp | 1.0.0 | stdio |
How to connect New Relic MCP Server
New Relic MCP Server runs locally from a Node.js package published to the npm registry: @meet-bhalodiya/newrelic-mcp version 1.0.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @meet-bhalodiya/newrelic-mcp@1.0.0. It reads these environment variables: NEW_RELIC_API_KEY (required, secret), NEW_RELIC_REGION, NEW_RELIC_DEFAULT_ACCOUNT_ID and NEW_RELIC_ACCOUNT_ALLOWLIST; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"newrelic-mcp": {
"command": "npx",
"args": [
"-y",
"@meet-bhalodiya/newrelic-mcp@1.0.0"
],
"env": {
"NEW_RELIC_API_KEY": "<secret>",
"NEW_RELIC_REGION": "<value>",
"NEW_RELIC_DEFAULT_ACCOUNT_ID": "<value>",
"NEW_RELIC_ACCOUNT_ALLOWLIST": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| NeurohiveMulti-agent memory intelligence with expertise tracking and conflict detection. | Local · stdio |
| Neverinfamous Memory Journal MCPA MCP server built for developers enabling Git based project management with project and personal… | Remote · HTTPLive check: ✗ no handshake |
| New LLM Release Tracker - buy per-query in-session (llmwatch)LLM releases: new models, availability, context. Register in-session - free testnet funds. | Remote · HTTPLive check: ✓ handshake |
| New MCP Server Directory (Agent Tools Index)MCP server index: newest agent tools listed. $0.01/query. Register in-session - free testnet funds. | Remote · HTTPLive check: ✓ handshake |
| New Relic MCP ServerMonitor, troubleshoot, and optimize your technology stack with Observability. | Remote · HTTPLive check: sign-in required |
| Newton BrowserLocal-only Chrome and Edge control for MCP clients through an origin-scoped extension. | Local · stdio |
| NexQL Postgres MCPStandalone Postgres MCP server - schema-aware, read-only by default, installable everywhere. | Local · stdio |
| NexsusPrivate persistent memory for Claude, ChatGPT & Gemini via MCP - semantic search, zero-code setup. | Remote · HTTPLive check: sign-in required |