New Relic MCP for AI Agents. Query Your Infrastructure Status Instantly
New Relic monitors your entire stack, giving your AI agent full visibility into infrastructure performance. Use this MCP to list applications, run raw New Relic Query Language (NRQL) queries, track Service Level Objectives (SLOs), and check real-time error rates without opening the browser or dashboard. It's direct metrics access for SREs.
Give Claude and any AI agent real-world access
Gets the primary performance metrics (error rates and response times) for specific applications.
Runs raw New Relic Query Language (NRQL) strings to pull highly specific, custom metrics from your data lake.
Searches for and lists all types of monitored assets, including applications, hosts, and containers.
Retrieves a list of currently open alerts and AI-detected issues across your accounts.
Monitors defined Service Level Objectives (SLOs) to tell you if your service is meeting its performance targets.
Ask an AI about this
Waiting for input…
What AI agents can do with New Relic: 10 Tools for System Monitoring
These ten tools let you discover, query, and audit every critical aspect of your monitored infrastructure, giving deep visibility through natural conversation.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using New Relic MCPGet Apm Summary
Pulls the primary performance metrics, including error rates and Apdex scores, for an application.
Get Dashboard
Fetches the configuration details for a specific observability dashboard.
Get Entity Details
Retrieves detailed metadata about any monitored entity, like an app or host.
Get Me
Returns the current user and account information associated with your connection.
List Accounts
Lists all New Relic accounts that are accessible under your API key.
List Alerts
Retrieves a list of currently open and active issues or alerts across the monitored environment.
List Dashboards
Lists all custom observability dashboards configured within your New Relic account.
List Entities
Searches and lists various monitored assets, such as APM applications or container...
List Service Levels
Lists all defined Service Level Objectives (SLOs) to check against performance...
Run Nrql
Executes an arbitrary New Relic Query Language query to retrieve custom dataset...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with New Relic, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by New Relic. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
The Pain of Context Switching Solved with Vinkius AI Gateway
Right now, checking system health means jumping between tabs. You open the dashboard to check Apdex scores; then you switch to the alerts page to see active incidents. Next, you might have to manually run a query in an ad-hoc tab just to compare average response times across two services. It's a slow cycle of clicking, reading, copying metrics, and switching context.
With this MCP, all that data is synthesized for you. You talk to your agent and ask it to check the golden metrics on Service A, list any active alerts related to Service B, and then run a custom NRQL query comparing them side-by-side. The full diagnostic picture comes back in one conversational thread.
New Relic MCP: System Status at Your Fingertips
You don't have to open the browser, navigate menus, or manage multiple dashboards just to check a vital metric. You use `get_apm_summary` and instantly get error rates; you call `list_alerts` when something breaks; and you run `run_nrql` for deep data dives.
It’s less about checking boxes on a dashboard, and more about getting immediate answers to critical questions about your live infrastructure.
What your AI can actually do with this
Connect your New Relic account to your AI client and stop clicking through dashboards just to check system health. This MCP lets you talk to your infrastructure using natural language, querying deep performance data with the NerdGraph API. You can ask about specific applications, compare error rates across services, or list all active alerts—all in one conversation.
It's like having a single pane of glass that answers questions instead of just showing graphs.
Need to check if your deployment went smoothly? Ask for the golden metrics (like Apdex scores and average response times) on demand. Want to know which services are running low on capacity, or what SLO targets you’re close to missing? Just ask. If you're building a catalog of external connections, Vinkius makes it easy to integrate this kind of deep system monitoring into your existing agent workflow.
019d75dc-ffd9-729c-9253-a90faaa5d934 Here's how it actually works
The bottom line is you get real-time system metrics delivered to your conversation thread, eliminating manual dashboard checks.
First, subscribe to this MCP and provide your New Relic User API Key.
Next, instruct your AI client to use the appropriate tool name (e.g., list_accounts) with specific parameters.
Finally, your agent executes the query against New Relic's graph database and returns structured data directly in the chat.
Who is this actually for?
This is for the SRE or DevOps engineer who hates clicking through five different tabs just to check if production is stable. It’s also for developers needing immediate performance metrics during a complex feature rollout, and product managers who need hard data on user experience goals.
Runs raw NRQL queries or checks list_alerts to quickly confirm if an incident is active or what services are degrading, without ever opening the web console.
Uses get_apm_summary immediately after deploying a fix to verify that key metrics like error rates and average response times look normal.
Queries service level indicators using list_service_levels to get high-level confirmation on whether the product is meeting its public commitment goals (SLOs).
What Changes When You Connect
Eliminate manual dashboard checks. Use run_nrql to execute complex queries and pull specific metrics—like average transaction duration over the last 7 days—in a single conversation.
Know if you’re failing your goals instantly. You can use list_service_levels to see defined SLOs and check their current performance status without navigating deep into dedicated dashboards.
Rapid incident triage is finally easy. Instead of clicking through multiple pages, simply ask the agent to run list_alerts and get a summary of all active issues.
Understand what you're monitoring. Use list_entities and get_entity_details to quickly map out every application, host, or container that has been added to your system.
Check core app health with one command. Calling get_apm_summary gives you the golden metrics (error rate, Apdex score) for a service, letting developers confirm stability immediately.
See it in action
Investigating an intermittent latency spike
A developer notices slow transactions. They ask their agent to run run_nrql with the query: 'SELECT average(duration) FROM Transaction SINCE 3 HOURS AGO'. The agent returns a table showing which specific services spiked, letting them pinpoint the bottleneck without digging through raw logs.
On-call shift handover
The on-call engineer starts their shift by asking for an overview. They use list_alerts to get a clean summary of all active incidents, and then call get_apm_summary on the top three applications to assess general health.
Compliance reporting
A product manager needs proof that the core user journey meets its SLA. They use list_service_levels to check the status of the 'Checkout Flow' SLO and confirm performance is green.
Auditing system coverage
An SRE wants to know what systems are monitored but haven't been checked in weeks. They first use list_accounts to ensure they have access, then run list_entities to get a comprehensive list of all assets.
The honest tradeoffs
What to watch out for, and the recommended way to handle each one.
Asking for 'general metrics'
Typing: 'Give me the health status.' This results in vague answers because the agent doesn't know which service you mean or what metric matters most.
Be specific. Instead, ask to get_apm_summary for your main application name. Or, if you need a custom look at database calls, use run_nrql with the exact query.
Overlooking account scope
Assuming the agent can check all services in one go without knowing which accounts are available for monitoring.
First, run list_accounts. This ensures your client knows exactly which environments or tenants it has permission to monitor before running any metrics tools.
Treating it like a knowledge base
Asking: 'How do I fix the slow database?' The agent can't give procedural steps; it only reads data.
Use get_entity_details to get metrics on the database component itself, or use run_nrql to pull specific performance trends. It’s a monitoring tool, not a troubleshooting manual.
When It Fits, When It Doesn't
Use this MCP if your primary job involves checking quantifiable system performance: Are error rates too high? Is the response time spiking? Has an SLO been violated? If you need to read data from New Relic—whether it’s a list of assets, current alerts, or a custom metric query via run_nrql—this is your tool. Don't use this if you are asking purely conceptual questions like 'Why did the system fail?' The agent can only report on what happened (data), not speculate on why it happened (cause). If all you need is general chat advice, stick to a standard LLM; if you need actionable metrics, connect your API key and start using these tools.
Questions you might have
Can I use the New Relic MCP to find out who owns an application? +
The MCP can help you discover applications using list_entities and retrieve metadata with get_entity_details. However, ownership details are usually stored in your internal CMDB; this tool confirms what is monitored by New Relic.
How do I check my SLO status using the New Relic MCP? +
You use the list_service_levels tool to retrieve definitions and current performance metrics for all defined Service Level Objectives. This tells you if your service is meeting its targets.
Is the New Relic MCP better than just running a query manually? +
Yes. Instead of writing, executing, and then copying results from a raw NRQL console window, the agent runs the run_nrql for you and presents the structured data right in your chat conversation.
Does the New Relic MCP support all my environments? +
You first use list_accounts to see every account connected via the API key. This confirms which distinct environments (like Staging or Production) the agent can monitor for you.
What if I want metrics from a specific container? +
You should first use list_entities to find the container's name, then pass that entity ID and run a specialized query using run_nrql for detailed performance data.