chore: MCP Registry listing prep (v2.1.1)

[cloudbring]

Prepares publication to the official MCP Registry (registry.modelcontextprotocol.io), where two other New Relic servers are listed and this one is absent.

• mcpName: io.github.cloudbring/newrelic-mcp in package.json — the registry's npm ownership check requires it in the published artifact, hence the 2.1.1 bump
• server.json (schema 2025-12-11): npm/stdio package with NEW_RELIC_API_KEY / NEW_RELIC_ACCOUNT_ID / NEW_RELIC_REGION
• README installation section rewritten: npx-first, MCP Registry, current smithery CLI syntax; fixes the pre-migration Smithery URLs (old server/@cloudbring/... path and the retired @smithery/cli install flow)

Merging auto-publishes 2.1.1 to npm (same OIDC pipeline as 2.1.0). After that, registry publication is two commands with GitHub device-flow auth:

mcp-publisher login github
mcp-publisher publish

🤖 Generated with Claude Code

https://claude.ai/code/session_012xEutmxJq5Ad1VdFyfzEhQ

[coderabbitai]

Warning

Review limit reached

@cloudbring, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 3 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: b5be9b3f-67e4-4fe0-91e9-60622eeb029b

📥 Commits

Reviewing files that changed from the base of the PR and between dc6e426 and f50a9fd.

📒 Files selected for processing (4)

• CHANGELOG.md
• README.md
• package.json
• server.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/mcp-registry-2.1.1

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}