Automate your API platform—with the same security as the UI
Platform engineers and AI can manage collections, proxies, and workflows without a second integration. Same identity and permissions as the admin UI—one auth model for both.
Practical use cases
Here’s what you can do when automation and AI connect to your platform through Management MCP.
Script and CI/CD without logging into the UI
Create a new API product, add a proxy, or update a workflow from a script or pipeline. Use the same credentials as the admin UI (e.g. service account or CI identity). No screen scraping or separate API keys—everything goes through the management API with full audit. Ideal for onboarding new products per environment, promoting config from dev to prod, or bulk updates.
Let AI assistants manage your API catalog
An AI assistant in your IDE or chat can create a collection, add endpoints to a proxy, or modify a workflow from a natural-language request (e.g. “Add a new product for Partner X with rate limit 1000/min”). The assistant uses the same identity and permissions as a human admin—so you keep one audit trail and no extra credentials. Great for platform teams who want to move faster without leaving their tools. Zerq also ships Zerq Copilot for Management inside the management UI — the same Management MCP tools, accessible in a chat panel without leaving the browser.
Infrastructure-as-code and automation
Define API products, proxies, and workflows in code or config, then apply them via the management API. Same role-based access as the UI: viewers can list and inspect, modifiers can create and update. Optional discovery lets MCP clients (and other automation) obtain tokens from your identity provider, so you don’t ship long-lived keys in scripts.
One audit trail for UI and automation
Every change made via the management API—whether from the admin UI, a script, or an AI agent—shows up in the same audit log. Compliance and ops see who changed what and when, without distinguishing “human” vs “automation.” Same permissions model everywhere.
Who it's for
Platform engineers, operations teams, and AI-assisted admin workflows. If you want to automate configuration, script changes, or let AI agents manage your API catalog and workflows with the same permissions as your admin UI, you get a standard endpoint (Model Context Protocol) with the same identity and role-based access. No second set of credentials or a separate “automation API.”
What you can do
The management API is exposed as standard MCP tools. With the right permissions you can:
- Collections: list, get, create, update, delete, enable/disable.
- Proxies: list, get, create, update, delete—each proxy defines routes and can have a workflow.
- Workflows: get and update workflow definitions; list workflow nodes and templates for building or editing flows.
Every call is authorized with your existing credentials and role-based access—viewers can list and get; modifiers can create and update. Same rules as the admin UI.
How it works
You connect with the same credentials you use for the admin UI (e.g. single sign-on or service account). Tool calls go to the management API; role-based access is enforced there. Optional: standards-based discovery lets MCP clients (and other automation) connect using your existing identity provider, so you don’t maintain separate API keys for scripts or AI.