
New Relic MCP Server
io.github.newrelic-partnersPublished by GitHub account newrelic-partnersv1.0.1-previewUpdated Oct 24, 2026
Monitor, troubleshoot, and optimize your technology stack with Intelligent Observability.
Overview
New Relic's hosted MCP server that lets an assistant monitor, troubleshoot and optimize your technology stack through New Relic observability data.
- What you can do
- Connect an assistant to New Relic observability for monitoring, troubleshooting and optimization of your technology stack. Tool groups are not listed in the manifest; the include-tags header can filter which tools are exposed, with examples such as discovery, alerting and data-access. Access is authenticated through OAuth or a New Relic user API key.
- When to use it
- Use it when you want an assistant to help investigate issues and reason about observability data in a New Relic account, without building a local integration. It suits teams already using New Relic for monitoring who want conversational troubleshooting.
- Requirements
- A remote streamable HTTP endpoint at mcp.newrelic.com; no local package or runtime. Authentication is required: OAuth, or a New Relic User API Key supplied in the api-key header. An optional include-tags header filters exposed tools. A New Relic account and network access are needed.
Installation
In SourceWeft
- Open New Relic MCP Server in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.newrelic-partners%2Fmcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"new-relic": {
"type": "http",
"url": "https://mcp.newrelic.com/mcp/"
}
}
}Tools
0Version history
1- v1.0.1-previewLatestSep 16, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.