‹ Back to Blog

Best Monitoring Tools With MCP Servers for AI Coding Agents (2026)

AI Dev Tools Observability

Your AI coding agent can read your code, run your tests, and open a pull request. Until recently it could not see what that code does in production. MCP servers from monitoring vendors close that gap. Connect one, and Claude Code, Cursor, or Copilot can pull the error, the trace, and the slow query behind a bug report without you copying anything out of a dashboard.

Most major monitoring vendors now offer an official MCP server. But they aren’t interchangeable. Some only expose errors. Some can resolve issues and edit dashboards on their own. Some bill every tool call. This guide compares them on the things that change how an agent works with your production data.

Quick Comparison

Tool Product covers Hosted server Data an agent can read Can it change data? MCP cost Starting price
Scout Monitoring APM, errors, logs Yes, OAuth Errors, traces, metrics, performance insights, background jobs No, read-only Included, not metered Free plan; paid from $19/mo
Sentry Error tracking, tracing, logs Yes, OAuth Errors, events, issue analysis Yes (resolve, assign) Included (Seer AI extra) Free plan; Team $26/mo
Datadog Full observability platform Yes, OAuth Logs, traces, metrics, monitors, error tracking, dashboards Yes, behind a permission Not documented APM from $31/host/mo
New Relic Full observability platform Yes, OAuth NRQL queries, errors, traces, logs, deployments, alerts No Metered in compute units Free tier; usage plus per-user
Honeybadger Error tracking, logs, uptime Yes, OAuth Errors, Insights queries, dashboards, alarms Yes Not documented Free plan; Team $26/mo
AppSignal APM, errors, logs Yes, OAuth or token Errors, performance, anomalies, logs, metrics Yes, per toolset Not documented Free plan; paid from $25/mo
Rollbar Error tracking No, local only Errors, occurrences, deployments, replays Yes (update items) Not documented Free plan (5K occurrences/mo); usage-based
Grafana Observability stack (you instrument) Yes (Grafana Cloud) Prometheus, Loki, Tempo, Pyroscope, dashboards, alerts Yes, can be disabled Cloud: billed per Assistant user Free tier; Pro from $19/mo plus usage
Better Stack Logs, uptime, errors Yes, OAuth or token Errors, logs, metrics, traces, uptime, incidents Yes, tools can be filtered Not documented Free tier; usage-based

What a product covers shapes what your agent can learn from it: error tracking shows what broke, while APM data also shows where time went, such as slow queries and N+1 patterns. Pricing checked against public vendor pricing pages in October 2026. “Not documented” means we could not find a statement on whether MCP use is included or billed separately. MCP availability and features change quickly, so confirm details in each vendor’s docs before you choose.

How We Evaluated

  • Setup: Is there a hosted server with OAuth, or do you have to run and update a local process?
  • Data depth: Can the agent see only errors, or also traces, slow queries, and logs it needs to find a root cause?
  • Safety: Can the server change production data, and can you limit that?
  • Cost: Is the server included, or are tool calls metered?
  • Fit: What kind of team and stack is each tool built for?

We sell monitoring software (Scout Monitoring), so we have a bias. We have tried to be fair about every tool on this list, including our own.

Scout Monitoring

Scout’s MCP server gives an agent read-only access to the errors, traces, metrics, and performance insights Scout already collects. Insights include N+1 queries, memory bloat, and slow queries, which point an agent at the cause of a slow endpoint, not just the symptom. It also covers background jobs and anomaly events.

The hosted server takes one command in Claude Code:

claude mcp add --transport http scout https://scoutapm.com/mcp

It authenticates with OAuth. A self-hosted option is available through npx @scout_apm/wizard. The server works with Claude Code, Claude Desktop, Cursor, VS Code with Copilot, Windsurf, Cline, and other MCP clients. There is no extra charge for it. See the Scout MCP server page for details.

Best for: Small and mid-sized teams on Ruby, Python, PHP, Elixir, or Node.js who want one server that covers errors and performance.

Limitations:

  • Log data is not available through the MCP server yet. It is on the roadmap.
  • Read-only by design, so an agent cannot resolve or assign errors through it.
  • Covers application monitoring, not infrastructure, Kubernetes, or front-end monitoring.

Look elsewhere if: your stack is Java, Go, or .NET, or you need one tool for infrastructure and application monitoring together.

Sentry

Sentry’s MCP server is hosted at mcp.sentry.dev with OAuth, with a local package (@sentry/mcp-server) for self-hosted Sentry. Its tools include find_issues, get_issue_details, search_events, update_issue, and analyze_issue_with_seer, which hands an issue to Sentry’s AI debugger.

Sentry lists MCP on its free Developer plan. Seer is billed separately.

Best for: Teams whose main need is error tracking across many languages, including front-end and mobile.

Limitations:

  • The documented tools focus on issues and events more than traces and slow queries.
  • Seer analysis costs extra.
  • AI-powered search tools in the local server need your own LLM provider key.

Look elsewhere if: you want your agent to investigate slow endpoints and database queries more than exceptions.

Datadog

Datadog’s MCP server went GA in March 2026. It is hosted per Datadog site and supports OAuth or API keys. Tools are grouped into toolsets for logs, traces, metrics, monitors, dashboards, error tracking, database monitoring, RUM, security, and more, with tools like search_datadog_logs, get_datadog_trace, and search_datadog_error_tracking_issues. The APM toolset is still in preview.

The server can write: update error tracking issues, draft monitors, and edit dashboards. Writes require the mcp_write permission. Datadog documents support for more than 20 clients.

Best for: Teams already running Datadog across infrastructure and applications.

Limitations:

  • Rate limited to 50 requests per 10 seconds and 100,000 tool calls per month.
  • Not available on US government sites.
  • APM is priced per host, which adds up for small teams with many hosts.

Look elsewhere if: you are not already on Datadog. Adopting it for MCP access alone is a lot of platform to take on.

New Relic

New Relic’s MCP server, now called Ground Truth, became generally available in September 2026 after a public preview starting in November 2025. It is hosted at mcp.newrelic.com with OAuth and has to be enabled by an admin. Tools cover NRQL queries, errors, distributed traces, logs, golden metrics, deployments, dashboards, alerts, and incidents. The documented tools are all read operations.

Tool calls are metered in compute units. A few AI tools, such as natural-language-to-NRQL, use Advanced Compute, which is available on Pro and Enterprise.

Best for: Existing New Relic customers who want an agent to run NRQL against the data they already collect.

Limitations:

  • Usage is metered, so heavy agent use shows up on the bill.
  • Some tools only work with OAuth.
  • An admin has to turn it on.

Look elsewhere if: you want predictable costs with no per-call metering.

Honeybadger

Honeybadger hosts its MCP server at mcp.honeybadger.io (with an EU endpoint) and uses OAuth. A self-hosted Docker image or binary is available, and it runs read-only by default. The agent can read errors and occurrences, run Insights queries, and work with dashboards and alarms. In hosted mode it can also create and update projects, dashboards, and alarms.

Best for: Small teams that want simple error tracking and uptime with a friendly free plan.

Limitations:

  • Performance data is lighter than a full APM’s, so an agent has less to work with on slow requests.
  • Some tools, like account, team, and uptime, are still in development.

Look elsewhere if: your bugs are mostly performance problems that need traces to explain.

AppSignal

AppSignal’s MCP server is hosted at appsignal.com/api/mcp and authenticates with OAuth or scoped tokens. It exposes error incidents, performance data, anomaly detection, check-ins, logs, metrics, and dashboards. Each toolset can be set to read, write, or disabled per token.

Best for: Ruby, Elixir, and Node.js teams that want APM, errors, and logs in one tool, including logs over MCP.

Limitations:

  • Default tokens can write to exceptions and dashboards. Tighten the permissions if you want read-only.
  • Pricing is based on request volume, so high-traffic apps move up tiers quickly.

Look elsewhere if: you run high-traffic apps on a tight budget, since request-based tiers climb with volume.

Rollbar

Rollbar’s MCP server (@rollbar/mcp-server) runs locally over stdio with an access token. There is no hosted endpoint. Tools include list-items, get-item-details, get-top-items, list-occurrences, get-deployments, get-replay, and update-item. Rollbar describes the server as under active development.

Best for: Existing Rollbar users who want their agent to triage errors.

Limitations:

  • Errors only. No traces or performance data.
  • You run and update the server yourself on each developer’s machine.

Look elsewhere if: you want a hosted server or performance data.

Grafana

Grafana has two official servers. The open-source mcp-grafana runs locally against self-hosted Grafana or Grafana Cloud. The Grafana Cloud MCP server, announced in July 2026, is hosted at mcp.grafana.com with OAuth. Both reach dashboards, Prometheus, Loki, Tempo, Pyroscope, alerting, and incidents. Writes can be disabled with a flag (open source) or by withholding the write scope (Cloud).

Best for: Teams already running the Grafana stack who want an agent to query their own metrics, logs, and traces.

Limitations:

  • You get what you instrument. There is no built-in APM agent that finds N+1 queries for you.
  • On Grafana Cloud, each user who connects is billed as a Grafana Assistant user.

Look elsewhere if: you want monitoring that works out of the box without building dashboards and queries.

Better Stack

Better Stack’s MCP server is hosted at mcp.betterstack.com with OAuth or an API token. It covers errors, logs, metrics, traces (via SQL), uptime monitors, incidents, on-call, and status pages. It can resolve incidents, create monitors, and update errors. You can restrict tools with request headers.

Best for: Teams that want logs, uptime, and incident management together.

Limitations:

  • Traces are queried through SQL, which puts more work on the agent.
  • Write tools are on unless you filter them.

Look elsewhere if: you want framework-level APM insights more than log search and uptime.

Other Tools With MCP Servers

  • Raygun has a hosted server covering crash reporting, RUM, and APM. It needs a paid plan. Raygun has a 14-day trial but no free tier.
  • BugSnag (SmartBear) is covered by the SmartBear MCP server, hosted or local, with an on-premise option.
  • PostHog has a free hosted server for error tracking alongside product analytics, feature flags, and experiments. It does not include APM traces.
  • Dynatrace has a hosted MCP gateway per environment for DQL queries, problems, and vulnerabilities.
  • Elastic serves an MCP server from your own Kibana through Agent Builder, with ES|QL access to logs, traces, and metrics.
  • Last9 offers hosted and local servers with more than 50 read tools for traces, logs, and exceptions.

Which MCP Server Should You Choose?

If you are already on Datadog, New Relic, or Grafana, use their server. Your data is already there, and switching tools for MCP access alone rarely pays off.

If you mainly need error tracking, Sentry and Honeybadger are strong, simple choices with free plans.

If you need performance debugging, look beyond error data. An MCP server that exposes traces, slow queries, and framework-level performance insights gives an agent much more context for diagnosing a slow endpoint than error data alone. Scout Monitoring exposes this data for Ruby, Python, PHP, Elixir, and Node.js applications.

If safety matters most, start read-only. Scout Monitoring and New Relic are read-only. For the others, use scoped tokens or read-only flags until you trust how your agent uses write access.

Frequently Asked Questions

Which monitoring tools have MCP servers for AI coding agents?

As of October 2026, Scout Monitoring, Sentry, Datadog, New Relic, Honeybadger, AppSignal, Rollbar, Grafana, Better Stack, Raygun, BugSnag, PostHog, Dynatrace, Elastic, and Last9 all offer official MCP servers. They differ in whether the server is hosted, what data it exposes (errors only, or traces and logs too), whether it can change data, and what it costs.

How do I let Claude Code or Cursor see my production errors?

Connect your monitoring tool’s MCP server to your AI client. Most vendors offer a hosted server with OAuth, so setup is one command or one config entry. For example, Scout Monitoring’s hosted server is added to Claude Code with claude mcp add --transport http scout https://scoutapm.com/mcp. The agent can then query errors, traces, and performance data in your editor.

Do monitoring MCP servers cost extra?

Usually not directly. Scout Monitoring, Sentry, and PostHog include their MCP servers at no extra charge. New Relic meters MCP tool calls in compute units, Grafana Cloud bills each connecting user as a Grafana Assistant user, and Elastic Serverless charges per Agent Builder execution after a free allowance. Your AI provider’s token usage is a separate cost in every case.

Should a monitoring MCP server be read-only?

For most teams, read-only is the safer default for an AI agent working against production data. Scout Monitoring and New Relic’s servers are read-only. Sentry, Datadog, Honeybadger, AppSignal, Rollbar, Grafana, and Better Stack can also change data, such as resolving issues or editing dashboards, and most let you restrict that with scopes, permissions, or a read-only flag.

What is the best monitoring MCP server for a small team?

For a small team running Ruby, Python, PHP, Elixir, or Node.js, Scout Monitoring gives an agent errors, traces, and performance insights like N+1 queries from one read-only server, with a free plan and no per-seat or per-host fees. Teams that only need error tracking often choose Sentry or Honeybadger. Teams already on Datadog or New Relic should use the server that comes with their existing platform.

Try Scout Monitoring’s MCP Server

Scout Monitoring is free to start, with 300K transactions a month, error monitoring, and log management included. Connect the Scout MCP server to your editor and ask your agent which endpoint is slowest and why. Sign up for Scout Monitoring.

For application monitoring with errors, logs, and traces, Scout Monitoring provides the fastest insights without the bloat.