Programmatic Access

Many teams want to manage their MCP Manager setup programmatically — provisioning gateways, servers, identities, and roles from code or a pipeline instead of clicking through the app. This page explains what you can automate today and where the programmatic surfaces stand.

​

Manage your workspace with the Admin API

The Admin API and MCP server are the control plane for MCP Manager. From an agent or a script you can create and configure inbound servers, gateways and their assignments, identities, hosts and connections, teams, roles, and access tokens, and query the call logs and alerts — the same actions available in the app, enforced by the same role capabilities. Every operation is exposed both as an MCP tool and as a REST endpoint under /api/v1/mcpm-admin. This is in closed beta: available now to workspaces with the MCP Manager Admin API entitlement (ff-mcpm-admin), ahead of general availability. To get started, see Connect an agent and the tool & endpoint reference.

​

Still to come

A few programmatic surfaces are planned but not in the beta yet — the Admin API roadmap tracks them:

• A downloadable CLI to script the same operations and wire them into pipelines and infrastructure-as-code workflows.
• Gateway rules, custom rule engines, feature provisioning, reporting, and an admin audit log over the Admin API.

​

What you can automate today without the beta

Two related capabilities ship to every workspace and don’t require the Admin API entitlement. Both are about connecting agents to gateways, not about provisioning the gateways themselves.

• Token-based agent connection. A headless agent connects to a gateway with a gateway API access token rather than an interactive sign-in. You create a token-based host and issue it a token scoped to a single gateway connection. See API Tokens & Headless Agents.
• Per-user identity passing. A single agent can carry each end user’s own identity through to downstream servers, so actions run as the real person and stay fully logged. See Agents that Pass Identities to MCP Manager.

These let an agent use a gateway programmatically. The Admin API above is what lets you build and manage your gateways, servers, and roles programmatically.

​

Working with log data programmatically

Log data leaves MCP Manager in three ways. In the Admin API beta, the query_logs operation reads the AI-usage call logs with filters and pagination — useful for ad-hoc inspection from an agent. For durable pipelines into your own tooling, log data is also available as a file export (CSV or ND-JSON) and pushed to your own collector over OpenTelemetry. For a continuous feed into a SIEM, prefer OpenTelemetry over polling query_logs. See Accessing log data programmatically and Export to SIEM.

​

Further reading