Preflight
New Relic MCP server for observing AI coding assistants (Claude Code, Cursor, Copilot, etc.)
- Transport
- Not stated
- Package
- —
- Registry id
- io.github.newrelic-experimental/preflight
No install snippet on purpose. A working MCP config is a command, its arguments and an environment block — the last two are where API keys live, so this catalogue never stores them and cannot publish them. Follow the link above for the authors' own instructions.
Docs • What's New • Examples • Community • Contributing
Why Your AI Tool Needs Observability
Your AI coding assistant makes hundreds of decisions every session — what to read, what to edit, when to run commands. But you can't see any of it. You know it was fast, but was it efficient? You got a PR merged, but how much did it cost? You fixed a bug, but did it get stuck in a loop first?
Preflight is observability for agentic coding — the actions, cost, and efficiency of your AI coding assistant as it works. See exactly what's happening, how much it costs, and where your AI is wasting time.
Local-first by design. Preflight runs entirely on your machine and sends your data nowhere by default. A live dashboard at localhost:7777 shows your sessions in real time, fully offline. Connect a New Relic account only when you want more — team rollups, alerting, and cross-session history. You choose: local-only, New Relic, or both.
Demo

See cost breakdown, efficiency scoring, anti-patterns, and live session tracking in action.
What You Get
Visibility
- Every action captured — file reads, edits, commands, searches
- Live session dashboard — see what's happening right now
- Historical trends — analyze patterns over weeks and months
Cost Control
- USD spend tracking — per session, day, and week
- Per-model and cache breakdown — know which models cost most and how efficiently context is reused
- Budget alerts — get notified before you overspend
- Forecasting — project monthly burn rate
Efficiency Insights
- Efficiency score — 0–100 score per task, based on how directly the AI worked
- Anti-pattern detection — catches re-reads, blind edits, stuck loops
- Personalized recommendations — optimize your AI workflow
- Weekly coaching reports — narrative analysis vs. your historical baseline
Dashboards
- Local dashboard — live session view at
localhost:7777, no account required - 8 pre-built New Relic dashboards — deploy in seconds (New Relic mode):
- Overview — session stats, cost summary, top tools
- Personal — 30-day self-reflection scoped to you
- Session Detail — deep-dive into a single session's tool calls
- Team View — aggregated cost and efficiency across developers
- Manager View — high-level team metrics, no tool-call content
- Adoption & Cost — adoption momentum, spend, MCP usage, and per-developer outcomes for engineering managers
- Platform Comparison — Claude Code vs. Cursor vs. Windsurf, etc.
- Security Audit — audit trail of sensitive file access
Quick Start
1. Install
npm install -g @newrelic/preflight
Using Smithery? Installing Preflight from the Smithery MCP registry wires up the MCP server for you, but Smithery has no mechanism to write Claude Code hooks. After install, ask Claude Code to call the
nr_observe_install_hooksMCP tool (it will offer to do this automatically oncenr_observe_healthreportssetup_required: true), then restart Claude Code to activate monitoring.
2. Run setup
preflight setup
The wizard defaults to local mode — press Enter through the prompts and you're set. It wires Preflight into your AI tool (hooks + MCP server) and writes config to ~/.newrelic-preflight/. Takes under a minute, no account required.
From the project's README.