A Bugsnag MCP server for interacting with Bugsnag API
from $29/mo
274 servers · 274 listings
Analytics & Monitoring
Analytics MCP server for Clamp Analytics. Gives Claude, Cursor, VS Code, Windsurf, and Cline tools for traffic, pages, events, revenue
from $19/mo
MCP server for cron job scheduling with systemd integration, retry logic, and observability
from $25/mo
MCP server for CronAlert uptime monitoring — manage monitors from Claude, Cursor, or any MCP client
from $19/mo
MCP server for querying CrowdStrike LogScale logs
from $25/mo
Prometheus metrics helpers for MongoDB MCP servers
from $10/mo
MCP server for Totem, the local-first toolkit that keeps AI-agent work queryable, enforceable, and derivable as plain files in your codebase
from $15/mo
Model Context Protocol (MCP) server for Prometheus monitoring
from $15/mo
Feature flags, A/B experiments, kill switches, dynamic config & i18n — Shipeasy MCP server.
from $19/mo
MCP server for weather, climate, air quality and geocoding from measurespace.io
from $19/mo
Official MCP server for ThreadMine — instant JVM thread dump analysis inside Claude Code, Claude Desktop and Cursor.
from $10/mo
GitHub repo analytics: stars, trending, code search, contributor maps for project research.
Free
Current drought conditions and severity across the United States
Free
A Model Context Protocol server providing tools to interact with ActivityWatch time tracking data
Free
Agent-native host monitoring MCP server — exposes real-time system vital signs (CPU, Memory, Temperature) to intelligent agents.
Free
Prometheus Alertmanager MCP Server for Claude AI integration
Free
AI-Powered Server Management - Connect Claude, Cursor, and other AI tools directly to your Alpacon infrastructure
Free
MCP server for interacting with Datadog API
Free
A Model Context Protocol server for Metabase integration
Free
Prometheus MCP Server
Free
MCP server for Sentry — error tracking, issues, releases, events, and project management for AI assistants.
Free
Analytics & Monitoring MCP servers on mcprush answer product, spend and reliability questions out of the warehouse and the observability stack, returning the cohort or the span the agent asked for rather than the dump around it.
What to look at before installing one is what a query costs and what the server may write back. A read tool pointed at a warehouse is a bill as well as a permission. Every server here names the publisher behind it and whether that publisher has been verified, the runtime it uses, how it authenticates, the tool surface it exposes and the price model it is sold under — and where a security scan has been run against it, what the scan found. The filters on the left narrow it further and the sort at the top decides what comes first.
A server that runs on its publisher’s infrastructure is reached through the mcprush gateway, so one key covers everything installed against your account, the calls are metered where you can see them and the ceiling on what they may cost is yours to set. Installing one is a line of the mcprush CLI — npx mcprush@latest add, followed by the server’s id — and a --client flag writes another client’s config instead of the default one. A server that runs on your own machine carries its publisher’s own instructions instead, and the listing says which of the two it is before you install anything.