Calico · OAuth Scopes

Calico OAuth Scopes

OAuth 2.0 probed

Calico uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

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.

CNIContainerseBPFKubernetesNetwork PolicyNetwork SecurityNetworkingOpen-SourceService Mesh
Scopes: 0 Flows: Method: probed

Scopes (0)

Calico implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

📄 Provider scope reference:

Source

OAuth Scopes

Raw ↑ 
generated: '2026-09-05'
method: probed
source: https://www.tigera.io/.well-known/oauth-authorization-server/
description: >-
  OAuth scope surface reachable from this record. The Calico API itself (projectcalico.org/v3) does
  NOT use OAuth — it authenticates with Kubernetes bearer tokens or client certificates and
  authorizes with Kubernetes RBAC, so it has no scope vocabulary at all (see
  authentication/calico-authentication.yml). The only OAuth authorization server on a host in this
  record is Tigera's, which fronts the remote MCP server in mcp/calico-mcp.yml.
authorization_server: https://www.tigera.io
metadata_document: https://www.tigera.io/.well-known/oauth-authorization-server/
protected_resource: https://www.tigera.io/wp-json/mcp/mcp-oauth-server
flows:
- type: authorization_code
  pkce_required_methods: [S256]
  token_endpoint_auth_methods: [none]
  dynamic_registration: client_id_metadata_document
scopes:
- name: mcp
  description: >-
    The single scope advertised in scopes_supported. Grants access to the Tigera MCP server. The
    provider publishes no scopes reference page, so no finer-grained description is available and
    none has been invented.
  source: scopes_supported in the RFC 8414 metadata document
scope_count: 1
docs: null
notes:
- >-
  Calico API authorization is Kubernetes RBAC, expressed as ClusterRole/Role rules over the
  projectcalico.org API group (verbs get/list/watch/create/update/patch/delete on resources such as
  networkpolicies, globalnetworkpolicies, ippools, bgppeers, hostendpoints, tiers). That is a real
  permission model, but it is not an OAuth scope model and is deliberately not transcribed here as
  one.
- >-
  This file is derived from a discovery document that was actually fetched. derive-oauth-scopes.py
  found zero oauth2 securitySchemes in openapi/ and correctly wrote nothing.

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/calico-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.