"How to handle REST APIs" matching MCP servers:

Enables AI assistants to search Elasticsearch logs, retrieve log details, analyze service health, scan local codebases for APIs, and create Kibana dashboards.

Enables AI clients like Claude to triage, investigate, and operate Icinga installations through natural language, integrating with Icinga's REST APIs and providing deep awareness of monitoring plugins and historical performance data.

An MCP server that exposes Home Assistant's REST and WebSocket APIs as 182 tools, enabling clients like Claude Code to control lights, climate, media, automations, and more. It also provides a status dashboard and supports running as a Home Assistant app or container.

Enables LLM clients to manage Uptime Kuma HTTP(S) monitors, groups, tags, and notifications, and to retrieve heartbeats, stats, and incident history through MCP tools.

Enables SRE operations through BMC Helix ITSM REST APIs, including incident and change management, CMDB queries, and MTTD calculation.

Federates MCP, A2A, and REST/gRPC APIs with centralized governance, discovery, and observability, optimizing agent and tool calling with plugin support.

A feature-rich gateway and proxy that federates MCP, REST, and gRPC services into a unified endpoint for AI clients. It enables virtualization of legacy APIs as MCP-compliant tools while providing built-in security, rate-limiting, and OpenTelemetry observability.

Analyzes how search engines and AI systems discover, crawl, cite, and convert traffic via CLI and MCP tools.

A read-only MCP server that exposes Hatchet client / REST observability APIs to coding agents across multiple environments from one process.

A Model Context Protocol (MCP) server that provides comprehensive Datadog monitoring capabilities, enabling Claude to manage CI/CD pipelines, analyze logs, query metrics, and handle monitors and SLOs.

An MCP server that records agent execution metrics and exposes a Context Window Explorer to visualize exactly what entered the model's context window across sessions, tokens, and tool calls.

Provides cryptographically signed, tamper-evident compute usage receipts via a Model Context Protocol server, exposing tools to record usage, verify receipts, list the ledger, and verify ledger integrity without requiring any account, API key, or single cloud provider.

8 standalone MCP servers for SMBs — Guardrails (prompt injection, PII, secrets detection), FinOps (AI cost tracking and budgets), Observability (agent tracing), Smart Router (17+ models, 9 providers), Trust Score (governance scoring 0-100), Memory (persistent agent memory), ThinkSecure (runtime security + SOC2/GDPR audit), and A2A Lite (agent-to-agent protocol). 37 tools total, TNC credits

Web analytics and AI session replay for agents: visitors, breakdowns, funnels, goals, revenue attribution, and AI-found site issues. Connects to the hosted Flowsery MCP server.

Provides MCP tools to create and query SigNoz trace funnels, enabling agents to measure their own step conversion rates from within the agent loop.

16-tool MCP server for Google PageSpeed Insights & Chrome UX Report APIs. Analyze, compare, and optimize web performance directly through Claude, Cursor, or any MCP-compatible AI client.

MCP server for Kibana / Elasticsearch — log search, aggregations, index discovery, and dashboard browsing. Hits Elasticsearch REST API directly for log queries; falls back to Kibana Console proxy when no direct ES URL is configured. Supports ApiKey auth (best for agents), Basic auth, and anonymous access. All 5 tools are read-only (readOnlyHint: true). Returns structured JSON (outputSchema).

Relays error logs from other MCP servers when an LLM call fails and the returned error message is unclear, helping the model handle errors more intelligently.

Provides Claude with read-only access to PC diagnostics including hardware specs, live performance metrics, disk usage, network checks, and more, enabling natural language queries about PC health and performance.

Minimal MCP server that integrates with Graylog, enabling agents to search, analyze, and inspect log messages across streams, discover fields and streams, and query multiple Graylog instances.