ToolsMCP
New Relic MCP Server
Listed in the official MCP Registry with a hosted streamable-http endpoint. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- newrelic.com
- Prerequisites
- An MCP client that supports streamable-http. The publisher declares a required credential header.
- Current version
- 0.1.0 · updated
Publisher’s description
Access New Relic observability data through MCP - query metrics, logs, traces, entities, and more
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 0.1.0, registry status active. 1 remote endpoint (streamable-http)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- newrelic.com
- Version observed
- 0.1.0
- Source
- registry.modelcontextprotocol.io/v0.1/servers/com.newrelic%2Fmcp-server/versions/0.1.0
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Investigate errors and incidents | Publisher description mentions “new relic”, “observability”, “metrics”, “logs”, “traces”. | No connection check or task run. Capability is as described by the publisher. | Rule observability matched: “new relic”, “observability”, “metrics”, “logs”, “traces”. Rule observability. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Remote endpoints
https://mcp.newrelic.com/mcp(streamable-http, declares a required credential)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
com.newrelic/mcp-server
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.