Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldNew Relic MCPWatchlist candidateMCP Server for Splunk platformMCP100 Selected
Task fit
Best for
  • Observability investigation and alerting workflows in New Relic.
  • Security and operations investigation over authorized Splunk searches and platform objects.
Not ideal for
  • Production use before the documented maturity gaps are resolved
  • Teams outside the publisher ecosystem or without least-privilege credentials
Avoid when
  • The connected identity is broader than the task requires
  • Tool calls cannot be reviewed before consequential mutations
  • The connected identity is broader than the task requires
  • Tool calls cannot be reviewed before consequential mutations
Provenance
Provenance details

First-party MCP

New Relic · Publisher source ↗

First-party MCP

ecosystem:splunk-platform · Publisher source ↗

Maintenance
Maintenance details

Repo: Not documented

Package: Not documented

Repo: Not documented

Package: Not documented

Popularity evidence
Client coverage
Client coverage details
Claude Code✓ Streamable HTTP
Claude Desktop✓ Streamable HTTP
Codex✓ Streamable HTTP
VS Code✓ Streamable HTTP
Cursor✓ Streamable HTTP
OpenCode✓ Streamable HTTP
Claude Code✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationThe hosted server supports OAuth and New Relic API keys.Splunk documents encrypted token handling and platform authentication for its managed MCP server.
CostThe MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply.The MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply.
PermissionsNew Relic RBAC, account permissions, API keys, and include-tags tool filtering constrain access.Splunk roles, capabilities, and tool-level configuration constrain searches and platform access.
Data handlingAuthorized service data and tool results pass through the MCP server to the connected AI client. Review the publisher and client data policies before using sensitive monitoring & observability information.Authorized service data and tool results pass through the MCP server to the connected AI client. Review the publisher and client data policies before using sensitive monitoring & observability information.
Limitations
Tradeoffs
  • New Relic explicitly provides the feature as a Preview program.
  • Search results may expose sensitive security and operational events; broad search roles should not be used.
Risk contextNew Relic explicitly provides the feature as a Preview program. Use a test environment where practical, least-privilege credentials, narrowly enabled tools, and explicit confirmation for mutations. MCP100 did not execute third-party server code during this documentation review.Search results may expose sensitive security and operational events; broad search roles should not be used. Use a test environment where practical, least-privilege credentials, narrowly enabled tools, and explicit confirmation for mutations. MCP100 did not execute third-party server code during this documentation review.
Evidence date
Editorial review2026-07-302026-07-30
Candidate evidence2026-07-30T19:00:00.000Z2026-07-30T19:00:00.000Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →