Google Apigee is the most complete API governance platform in the enterprise market. It manages proxies, packages APIs into products, governs developer access, tracks deployments, discovers shadow APIs, stores specifications, and runs integration workflows. The Naftiko capability set for Apigee turns all of that governance infrastructure into a structured tool surface for AI agents.
What the Capability Covers
The Apigee capability set is organized into five shared definitions and workflow capabilities covering API management, API Hub, APIM shadow discovery, Integrations, Registry, specification management, developer portal and app management, and analytics traffic observability.
MCP Tools Available
list-hub-apis, list-api-versions, list-api-specs, get-api-spec-contents, lint-api-spec, list-registry-apis, list-registry-specs, list-api-proxies, get-api-proxy, deploy-proxy, list-api-products, list-developers, list-developer-apps, list-environments, get-environment-deployments, list-shared-flows, list-target-servers, get-analytics-stats, list-observation-jobs, list-integrations, execute-integration
Capability Specification
naftiko: "1.0.0-alpha1"
info:
label: "Apigee API Specification Management"
description: "Unified workflow for managing API specifications on Apigee — browsing the API Hub catalog, retrieving spec contents, linting for compliance, and cross-referencing with Registry artifacts."
tags:
- Apigee
- API Specifications
- API Governance
- OpenAPI
- Google Cloud
binds:
- namespace: env
keys:
GOOGLE_ACCESS_TOKEN: GOOGLE_ACCESS_TOKEN
capability:
consumes:
- import: api-hub
location: ./shared/api-hub.yaml
- import: registry
location: ./shared/registry.yaml
exposes:
- type: mcp
port: 9092
namespace: apigee-specs-mcp
transport: http
description: "MCP server for AI-assisted API specification management and governance."
tools:
- name: list-hub-apis
description: "List all APIs catalogued in Apigee API Hub — the primary API inventory for governance."
hints:
readOnly: true
destructive: false
idempotent: true
call: "api-hub.listApis"
outputParameters:
- type: object
mapping: "$."
- name: list-api-specs
description: "List OpenAPI and other specs attached to an API version in the Hub."
hints:
readOnly: true
destructive: false
idempotent: true
call: "api-hub.listApiSpecs"
outputParameters:
- type: object
mapping: "$."
- name: get-api-spec-contents
description: "Retrieve the raw contents of an API spec — useful for inspection, diffing, or feeding to an AI agent."
hints:
readOnly: true
destructive: false
idempotent: true
call: "api-hub.getApiSpecContents"
outputParameters:
- type: object
mapping: "$."
- name: lint-api-spec
description: "Lint an API spec for compliance and quality violations — returns issues with severity and location."
hints:
readOnly: false
destructive: false
idempotent: true
call: "api-hub.lintApiSpec"
outputParameters:
- type: object
mapping: "$."
- name: list-registry-apis
description: "List APIs tracked in the Apigee Registry."
hints:
readOnly: true
destructive: false
idempotent: true
call: "registry.listApis"
outputParameters:
- type: object
mapping: "$."
Running It
docker pull ghcr.io/naftiko/framework:latest
# Set GOOGLE_ACCESS_TOKEN in your .env file
docker run -p 9092:9092 \
-v ./capabilities/api-specification-management.yaml:/app/capability.yaml \
--env-file .env \
ghcr.io/naftiko/framework:latest /app/capability.yaml
The Apigee capabilities are part of the Naftiko Fleet. Clone the repo, set GOOGLE_ACCESS_TOKEN, and your Apigee governance surface is immediately available as MCP tools.
