Skip to main content
Glama
9,948 servers. Last updated

"Understanding or Using Memory Lists" matching MCP connectors:

Matching Connector Tools:

  • Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve incidents.

  • Connect engineering metrics, DORA performance, and deploy risk scoring to any AI assistant. Score PRs for deployment risk using a 36-signal model, query team health, incidents, coverage, and more.

  • The Google GKE MCP server is a managed Model Context Protocol server that provides AI applications with tools to manage Google Kubernetes Engine (GKE) clusters and Kubernetes resources. It exposes a structured, discoverable interface that allows AI agents to interact with GKE and Kubernetes APIs, enabling them to inspect cluster configurations, retrieve Kubernetes resource YAMLs, monitor operations like cluster upgrades, diagnose issues, and optimize costs—all without needing to parse text output or use complex kubectl commands.

  • Uptime, SSL, DNS and domain monitoring you can talk to from Claude or any MCP client.

  • Mobile observability for AI agents. Investigate crashes, hangs, ANRs, bugs, and app performance, and triage app store reviews, directly from your IDE or terminal.

  • SentryAOAuth

    Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.

  • Log, evaluate, and ground AI decisions against authority context. Returns PASS, WARN, or BLOCK.

  • Debug production issues using Shipbook logs and Loglytics error insights.

  • The Polar Signals MCP server enables AI assistants to connect directly with performance profiling data, allowing users to analyze application performance through natural language queries. Key capabilities include querying CPU performance and memory usage, exploring profiling metadata like profile types and labels, and providing AI-driven code optimization suggestions directly within development environments like Claude Code or Cursor.

  • The Buildkite MCP server exposes Buildkite product data (pipelines, builds, jobs, and test data) to AI tools, editors, and agents through the Model Context Protocol. It provides capabilities including pipeline creation and management, build monitoring with specialized tools like 'wait_for_build', efficient log querying using Apache Parquet conversion and caching, and OAuth-based authentication for both read-write and read-only access to Buildkite's REST API.