"sap business one" matching MCP servers:

Enables read-only monitoring, failed-message analysis, health summarization, and AI-assisted troubleshooting against SAP Cloud Integration tenants through MCP-compatible clients.

Enables local or HTTP-based MCP interactions with a mock SAP Cloud ALM environment, enforcing read/write capability separation and fail-closed security policies for future SAP Cloud ALM connectivity.

MCP server for reading and searching SAP Commerce Cloud (CCV2) logs stored in Azure Blob Storage, enabling log listing, retrieval, and regex search via MCP tools.

Enterprise-grade MCP server with multi-agent system for business AI transformation across finance, healthcare, retail, and other domains. Provides specialized AI agents for data analysis, API execution, business validation, and report generation with real-time monitoring and observability.

Enables AI agents to perform root cause analysis on SAP systems by querying Azure Log Analytics data, offering schema discovery, validated KQL execution, result analysis, and automated 8-step RCA workflows.

Enables classification of GPU workloads as training, inference, or idle from telemetry data, with tools for one-shot classification, benchmarking, and audit log verification.

Unified observability gateway for AI agents — one MCP server for Prometheus, Loki, and any backend.

MCP server for Healthchecks: inspect, create and adjust cron and uptime checks, and read why one failed

Laravel Telescope-style debugging for Hono apps whose dashboard endpoint is also an MCP server: read recent exceptions with the request that produced them, recent requests filtered by status or duration, one request in full, and the slowest queries. Five read-only tools, zero runtime dependencies.

Zabbix MCP server and CLI in one Go binary. 15 task-shaped tools: current problems, host investigation, why an alert did or did not arrive, metrics, maintenance. Zabbix 6.4+.

An MCP server that exposes GPU-accelerated anomaly detection to AI assistants via the Model Context Protocol. Provides two MCP tools: waveguard_scan (send training + test data in one call, returns per-sample anomaly scores and top explanatory features) and waveguard_health (check API and GPU status). Works on time series, JSON, numbers, text, and images — fully stateless.

The logs of everything on one machine — app, build, GPU, containers, serial board, OS — interleaved in the order they happened, and readable by an agent. Read-only: it can tail, search and wait, and it cannot write, delete or configure anything.

Read-only Model Context Protocol server that enables querying Langfuse v4 events-only deployments for traces rebuilt as trees, sessions, searchable observations, scores, server-side metrics aggregates and managed prompts. Supports many projects from one server, taking a project argument per data tool and verifying each key against the project it is filed under before any data is read.

Streams live progress from long-running MCP tool calls to any connected client. Instrument a tool call with mcp-telemetry-sdk, and telemetry_subscribe pushes its steps, logs, cost, and completion over notifications/progress — no polling, and a job started in one session can be watched from a different one.

Model Context Protocol (MCP) server & CLI inspector for the Agent-Shelter Protocol (ASP) reference observatory

glama.json already carries one, so this may prefill

Zero-config MCP server that gives AI coding assistants a real-time diagnostic snapshot of your local dev environment. Detects framework, running services, recent errors, git state, and provides a health diagnosis in one call.

A read-only stdio MCP server that provides a generic log-querying layer for Grafana/Loki, enabling discovery, retrieval, and aggregation of logs (raw, slow, errors, volumes) through 15 tools, with hard limits on data volume and no built-in business logic.

A self-contained, security-first, EU-sovereign unified AI-operations MCP server that fuses a live bitemporal fleet model, a drift engine, and a tiered audited actuator into one control plane.

Lets your coding agent check whether a production deploy actually worked. It waits for DeployAngel's verdict on a release (cleared, failed, or not cleared yet) and reads the evidence when one fails, including jobs that quietly stopped running.