Groundcover · OAuth Scopes

Groundcover OAuth Scopes

OAuth 2.0 probed

Groundcover publishes 1 OAuth 2.0 scope. Scopes are the fine-grained permissions an application requests at authorization time to act against the Groundcover API on a user’s behalf.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

AIOpsObservabilityKuberneteseBPFMonitoringLogsTracesMetricsOpenTelemetryMCP

Scopes: 1 Flows: Method: probed

Scopes (1)

Scope	Description	Flows
access:router	The single scope advertised by groundcover's MCP protected-resource metadata. Grants an OAuth-authenticated agent access to the MCP router endpoint; groundcover publishes no per-tool or per-signal scope breakdown, so the effective permission is the one the logged-in member already holds under RBAC.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-29'
method: probed
source: https://mcp.groundcover.com/.well-known/oauth-protected-resource
provider: Groundcover
providerId: groundcover
description: >-
  groundcover's only published OAuth surface is the remote MCP server. Its RFC 9728 Protected
  Resource Metadata declares exactly one scope. The REST API at api.groundcover.com does not use
  OAuth at all — it authenticates with a service-account bearer API key, and authorization is
  expressed through RBAC policies rather than scopes (see authentication/groundcover-authentication.yml).
  No scopes/permissions reference page exists in the docs; this file records what the server itself
  publishes.
resource: https://mcp.groundcover.com/api/mcp
authorization_servers:
  - https://mcp.groundcover.com
bearer_methods_supported:
  - header
scopes:
  - name: access:router
    description: >-
      The single scope advertised by groundcover's MCP protected-resource metadata. Grants an
      OAuth-authenticated agent access to the MCP router endpoint; groundcover publishes no
      per-tool or per-signal scope breakdown, so the effective permission is the one the logged-in
      member already holds under RBAC.
    source: https://mcp.groundcover.com/.well-known/oauth-protected-resource
    http_status: 200
    probed: '2026-08-29'
scope_count: 1
x-evidence:
  - url: https://mcp.groundcover.com/.well-known/oauth-protected-resource
    status: 200
  - url: https://mcp.groundcover.com/.well-known/oauth-authorization-server
    status: 200

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/groundcover-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.