New Relic MCP Server for CrewAI 10 tools — connect in under 2 minutes
Connect your CrewAI agents to New Relic through Vinkius, pass the Edge URL in the `mcps` parameter and every New Relic tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
from crewai import Agent, Task, Crew
agent = Agent(
role="New Relic Specialist",
goal="Help users interact with New Relic effectively",
backstory=(
"You are an expert at leveraging New Relic tools "
"for automation and data analysis."
),
# Your Vinkius token. get it at cloud.vinkius.com
mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)
task = Task(
description=(
"Explore all available tools in New Relic "
"and summarize their capabilities."
),
agent=agent,
expected_output=(
"A detailed summary of 10 available tools "
"and what they can do."
),
)
crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
About New Relic MCP Server
Connect your New Relic account to your AI agent and gain full visibility into your applications and infrastructure through natural conversation using the powerful NerdGraph GraphQL API.
When paired with CrewAI, New Relic becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call New Relic tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
What you can do
- Entity Discovery — List and search for monitored entities such as APM applications, hosts, containers, and browser apps.
- Custom Querying — Execute raw NRQL (New Relic Query Language) strings to retrieve specific datasets and custom metrics.
- Golden Metrics — Fetch real-time APM summaries including error rates, Apdex scores, and average response times.
- Incident Monitoring — Track active AI-detected issues and open alerts across your accounts.
- Dashboard Oversight — List and retrieve configuration details for your custom observability dashboards.
- Account Management — Access current user metadata and list all accessible New Relic accounts.
- SLO Tracking — Monitor defined Service Level Indicators (SLOs) and performance levels.
The New Relic MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
How to Connect New Relic to CrewAI via MCP
Follow these steps to integrate the New Relic MCP Server with CrewAI.
Install CrewAI
Run pip install crewai
Replace the token
Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com
Customize the agent
Adjust the role, goal, and backstory to fit your use case
Run the crew
Run python crew.py. CrewAI auto-discovers 10 tools from New Relic
Why Use CrewAI with the New Relic MCP Server
CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with New Relic through the Model Context Protocol.
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
New Relic + CrewAI Use Cases
Practical scenarios where CrewAI combined with the New Relic MCP Server delivers measurable value.
Automated multi-step research: a reconnaissance agent queries New Relic for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff
Scheduled intelligence reports: set up a crew that periodically queries New Relic, analyzes trends over time, and generates executive briefings in markdown or PDF format
Multi-source enrichment pipelines: chain New Relic tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow
Compliance and audit automation: a compliance agent queries New Relic against predefined policy rules, generates deviation reports, and routes findings to the appropriate team
New Relic MCP Tools for CrewAI (10)
These 10 tools become available when you connect New Relic to CrewAI via MCP:
get_apm_summary
Get APM golden metrics
get_dashboard
Get dashboard configuration
get_entity_details
Get specific entity metadata
get_me
Get current user and account info
list_accounts
List accessible New Relic accounts
list_alerts
List active issues and alerts
list_dashboards
List New Relic dashboards
list_entities
List monitored entities
list_service_levels
List Service Level Indicators (SLOs)
run_nrql
Execute a NRQL query
Example Prompts for New Relic in CrewAI
Ready-to-use prompts you can give your CrewAI agent to start working with New Relic immediately.
"List all APM applications in my account."
"Show me the error rate and response time for application GUID 'MTIzNDU2fEFQTXxBUFBMSUNBVElPTnwxMjM'."
"Run NRQL: 'SELECT average(duration) FROM Transaction FACET appName SINCE 1 DAY AGO' for account 12345."
Troubleshooting New Relic MCP Server with CrewAI
Common issues when connecting New Relic to CrewAI through the Vinkius, and how to resolve them.
MCP tools not discovered
Agent not using tools
Timeout errors
Rate limiting or 429 errors
New Relic + CrewAI FAQ
Common questions about integrating New Relic MCP Server with CrewAI.
How does CrewAI discover and connect to MCP tools?
tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.Can different agents in the same crew use different MCP servers?
mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.What happens when an MCP tool call fails during a crew run?
Can CrewAI agents call multiple MCP tools in parallel?
process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.Can I run CrewAI crews on a schedule (cron)?
crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.Connect New Relic with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect New Relic to CrewAI
Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.
