Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Groundcover (BYOK) — connector documentation

  • MCP endpoint: https://byok-groundcover.connectorbay.com/mcp
  • REST API: POST https://byok-groundcover.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-groundcover.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Groundcover groundcover API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-groundcover.connectorbay.com/health · Tool schemas: https://byok-groundcover.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-groundcover · agent@connectorbay.com

What Groundcover (BYOK) is for

Groundcover (BYOK) lets an AI assistant read your own Groundcover data through the Groundcover API with a key you supply (groundcover API key). Read-only: 9 tools (list_clusters, list_namespaces, list_workloads, list_deployments, list_monitors, get_monitor, search_logs, search_traces, search_kubernetes_events). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.groundcover.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Groundcover. Groundcover and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which clusters does groundcover monitor and how loaded are they?"
  • "Which namespaces were active in my cluster this morning?"
  • "Which workloads have the highest error rate in groundcover?"
  • "Are all my deployments fully available?"
  • "What alert monitors do I have in groundcover?"
  • "Show how my groundcover monitor is configured"

What it does

  • list_clusters: List Kubernetes clusters monitored by groundcover with cloud provider, Kubernetes version, node count, issue count and CPU and memory usage against allocatable.
  • list_namespaces: List the Kubernetes namespaces seen by groundcover in a time range.
  • list_workloads: List Kubernetes workloads with namespace, kind, readiness, pod count, latency percentiles, requests per second, error rate, CPU and memory use and issue count.
  • list_deployments: List Kubernetes deployments active in a time range with cluster, namespace, desired, ready and available replicas and warnings.
  • list_monitors: List the configured groundcover monitors (alert rules) with ID, title and type (metrics, traces, logs, events, infra).
  • get_monitor: Get one monitor's configuration: title, severity, queries, thresholds, evaluation interval, no-data state and paused flag.
  • search_logs: Search logs with a gcQL query over a time range and return the matching rows or aggregates; end the query with a limit.
  • search_traces: Search trace spans with a gcQL query over a time range, for example failing requests or latency percentiles per endpoint.
  • search_kubernetes_events: Search Kubernetes events with a gcQL query over a time range, for example warnings grouped by reason.

BYOK key

You bring your own Groundcover groundcover API key (https://docs.groundcover.com/administer/api-keys). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.groundcover.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Notices

Works for the groundcover SaaS API (api.groundcover.com) and accounts with a single backend; accounts with several backends need an X-Backend-Id header that this connector does not send. Self-hosted deployments are not supported.

Data sources

Live from the Groundcover API (api.groundcover.com) with a BYOK key; documentation: https://docs.groundcover.com/reference/remote-access-and-apis/api-examples. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Groundcover. Groundcover and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Groundcover account.

Built for: Worldwide. Languages: English.