Tigera MCP Server

A remote Model Context Protocol server published on the tigera.io host, advertised through RFC 8414 OAuth authorization-server metadata and RFC 9728 protected-resource metadata. The server fronts the Tigera WordPress content estate (the marketing site, blog and resources), not the Calico cluster API. Authorization is OAuth 2.1 authorization-code with PKCE (S256), a single `mcp` scope, public clients (token_endpoint_auth_method none) and client-ID metadata documents. tools/list is authenticated — an anonymous JSON-RPC call returns 401 mcp_unauthorized — so the live tool schemas require an authorized session.

API entry from apis.yml

apis.yml Raw ↑
aid: tigera:tigera-mcp-server
name: Tigera MCP Server
description: A remote Model Context Protocol server published on the tigera.io host, advertised through
  RFC 8414 OAuth authorization-server metadata and RFC 9728 protected-resource metadata. The server fronts
  the Tigera WordPress content estate (the marketing site, blog and resources), not the Calico cluster
  API. Authorization is OAuth 2.1 authorization-code with PKCE (S256), a single `mcp` scope, public clients
  (token_endpoint_auth_method none) and client-ID metadata documents. tools/list is authenticated — an
  anonymous JSON-RPC call returns 401 mcp_unauthorized — so the live tool schemas require an authorized
  session.
humanURL: https://www.tigera.io/
baseURL: https://www.tigera.io/wp-json/mcp/mcp-oauth-server
tags:
- MCP
- Agents
- Content
properties:
- type: MCPServer
  url: mcp/tigera-mcp.yml
- type: ToolCrosswalk
  url: mcp/tigera-tool-crosswalk.yml
- type: OAuthScopes
  url: scopes/tigera-scopes.yml
x-evidence:
  protected_resource: https://www.tigera.io/.well-known/oauth-protected-resource
  authorization_server: https://www.tigera.io/.well-known/oauth-authorization-server
  http_status: 200
  tools_list_status: 401
  fetched: '2026-08-05'