Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
New Relic MCP server for observing AI coding assistants (Claude Code, Cursor, Copilot, etc.)
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
NEW_RELIC_LICENSE_KEY, NR_AI_MODE, NEW_RELIC_ACCOUNT_IDValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"preflight": {
"command": "npx",
"args": [
"-y",
"@newrelic/preflight"
],
"env": {
"NEW_RELIC_LICENSE_KEY": "your-value",
"NR_AI_MODE": "your-value",
"NEW_RELIC_ACCOUNT_ID": "your-value"
}
}
}
}Run this in your terminal
claude mcp add preflight --env NEW_RELIC_LICENSE_KEY=your-value --env NR_AI_MODE=your-value --env NEW_RELIC_ACCOUNT_ID=your-value -- npx -y @newrelic/preflightFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"preflight": {
"command": "npx",
"args": [
"-y",
"@newrelic/preflight"
],
"env": {
"NEW_RELIC_LICENSE_KEY": "your-value",
"NR_AI_MODE": "your-value",
"NEW_RELIC_ACCOUNT_ID": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"preflight": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@newrelic/preflight"
],
"env": {
"NEW_RELIC_LICENSE_KEY": "your-value",
"NR_AI_MODE": "your-value",
"NEW_RELIC_ACCOUNT_ID": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
NR_AI_MODE envNEW_RELIC_ACCOUNT_ID envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account newrelic-experimental, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: NEW_RELIC_LICENSE_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.71.0) reached the registry 3 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Kanal Varna — drains, leaks & plumbing (Varna, BG)
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Drain unblocking, leak detection & plumbing in Varna, Bulgaria: services, prices, areas, contact
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Preflight Observability for AI Coding Assistants
Docs • What's New • Examples • Community • Contributing
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.
See cost breakdown, efficiency scoring, anti-patterns, and live session tracking in action.
localhost:7777, no account requirednpm install -g @newrelic/preflight
Using [Smithery](https://smithery.ai)? 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, either run
preflight installin a terminal, or set"allowHeadlessInstall": truein your Preflight config (orNEW_RELIC_AI_ALLOW_HEADLESS_INSTALL=true) and ask Claude Code to call thenr_observe_install_hooksMCP tool. The tool refuses by default, because any connected MCP client can call it. With the flag on, it offers to do this automatically oncenr_observe_healthreportssetup_required: true. Then restart Claude Code to activate monitoring.
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.
Using GitHub Copilot? The wizard also asks to install Copilot hooks — saying yes configures both the Copilot CLI and VS Code Copilot Chat automatically (hooks, MCP registration, and the fix for VS Code's hook double-capture), so Copilot gets the same tool-call and cost metrics Claude Code does. Run it standalone anytime with
preflight install --copilot. See docs/ADAPTERS.md for details.
When prompted, pick a mode:
| Mode | What it does | New Relic account? |
|---|---|---|
| local _(default)_ | Everything stays on your machine; live dashboard at localhost:7777 | Not needed |
| cloud | Ships telemetry to New Relic | Required |
| both | Local dashboard and New Relic | Required |
Restart your AI tool — hooks and the MCP server load at session start. Every tool call is captured automatically. Open http://localhost:7777 to watch your session live.
Using Kiro? Add Preflight as a Kiro Power for the
nr_observe_*query tools — see the doc for install steps and how to add
automatic tool-call capture on top.
Using Claude Code? You can skip the npm install above and add Preflight as a Claude Code plugin instead:
`
/plugin marketplace add newrelic-experimental/preflight
/plugin install newrelic-preflight@newrelic-preflight-marketplace
`
Cursor — Add to Cursor installs the MCP server via a one-click deeplink; run preflight setup afterwards for hook capture.
Homebrew (macOS):
brew tap newrelic-experimental/preflight
brew trust newrelic-experimental/preflight brew install preflight
Run preflight setup afterwards for hook capture.
Claude Code • Amazon Kiro • Amazon Q Developer CLI • Factory Droid • OpenAI Codex • opencode • Kilo Code • Pi • GitHub Copilot • GitHub Copilot SDK • GitHub Copilot app • Google Gemini CLI • Cursor • Windsurf • Google Antigravity • Zed • Continue.dev • Cline
Coverage isn't uniform — some platforms capture every built-in tool call, others (Zed, Continue.dev, Cline) only see calls routed to Preflight's own MCP tools. See ADAPTERS.md for what each platform can and can't observe, and per-platform setup steps.
Local mode is fully featured on its own. Connect a New Relic account to unlock:
Re-run preflight setup and choose cloud or both, or configure it non-interactively:
preflight install \
--mode cloud \ --license-key YOUR_LICENSE_KEY \ --account-id YOUR_ACCOUNT_ID
EU accounts add --eu. FedRAMP accounts add --fedramp. Japan accounts add --jp.
A key passed with --license-key is visible to every local user through ps. For scripts, read it from a file instead (--license-key-file ~/.nr-key, which warns if other users can read the file) or set NEW_RELIC_LICENSE_KEY and NEW_RELIC_ACCOUNT_ID in the environment. The flag wins over the file, and the file wins over the environment. The environment is used only when config.json has no stored licenseKey or licenseKeyCommand, so a shell that already exports these variables for an APM agent never overwrites your stored key. To replace a stored key, pass --license-key-file. With --copilot, the key is still handed to copilot mcp add as an argument, so it is briefly visible in ps for that one call.
Then deploy the prebuilt dashboards:
NEW_RELIC_API_KEY=NRAK-... NEW_RELIC_ACCOUNT_ID=12345 \
preflight deploy-dashboards --all
You'll need a license key (telemetry ingest) and your account ID, plus a user API key (NRAK-…) to deploy dashboards and alerts. See ADVANCED.md for alerts, OTLP export to other backends, and Terraform.
No dashboard until you run `deploy-dashboards`. Cloud mode ships telemetry to New Relic as soon as it's configured, but nothing creates a dashboard automatically — that's the separate step above, and it needs a different credential (a user API key, not your license key). Until you run it, there's no UI to look at. In the meantime, query the raw events directly in New Relic's Query Builder, e.g.:
`sql
SELECT * FROM AiToolCall SINCE 1 hour ago
`
Once
deploy-dashboardssucceeds, find the dashboards under your New Relic account's Dashboards section.
Data ingest note: Telemetry sent to New Relic counts against your account's data ingest. On paid plans, standard ingest rates apply. Monitor your usage under NR One → Data Management → Data Ingestion.
cloud/both mode. Skip it to run local-only (the default).NRAK-…) — only needed to deploy dashboards and alertspreflight doctor # Run 10 diagnostic checks and print actionable fix commands
preflight validate # Check config for syntax errors and unknown keys preflight update # Pull latest version, rebuild, and offer to restart a running dashboard (source installs only — npm installs: npm install -g @newrelic/preflight@latest; Homebrew installs: brew upgrade preflight) preflight local # List running --local dashboard processes and live --stdio MCP processes preflight local --clean # Kill orphaned --local processes and --stdio processes with a missing binary (prompts for confirmation) preflight uninstall # Remove hooks and MCP config (prompts with a summary first) preflight uninstall --yes # Skip the confirmation prompt (for scripts and CI) preflight uninstall --daemon # Remove only the background dashboard daemon
Add --project to install/uninstall to scope changes to the current directory only.
WSL users: preflight setup will ask which Claude Code you're running. You can also set it explicitly:
--windows-cc — Windows Claude Code (the desktop app); uses wsl.exe hooks and Windows paths--linux-cc — Linux Claude Code installed via npm inside WSLOnly the beginning is shown; read the rest in the repo