Manage MCP
Use manifests to control who can use the Model Context Protocol (MCP) with your organization. Use manifests also to run MCP servers of your own. Each change is a pull request, so Git records who asked for it.
The Infrastream MCP sign-in, the gateway and the tools are a pilot. They run in the Infrastream integration environment. Customers cannot use them yet. The manifests in this guide are already valid. The manifests that run your own MCP servers work today. Read The Agent Path for the rollout.
Two kinds of MCP
| Kind | What it is | Who runs it | Status |
|---|---|---|---|
| The Infrastream MCP | The AI tool of an employee signs in as that employee. It reads the state of your estate and proposes changes as pull requests. | Infrastream | Pilot |
| Your own MCP server | An MCP server that your team builds. It runs on Cloud Run in your project. | You, with Infrastream | Available |
Decide who can connect to the Infrastream MCP
Access follows the tiers of the person in your organization. You do not make a separate list of MCP users.
-
Put people in groups. See Manage Access.
-
Put the groups in a tier of the
permissionsblock. The agent of a person gets the tier of that person, and no more.apiVersion: lowops.manifests.v1
kind: Organization
metadata:
name: acme-corp
spec:
permissions:
administrators:
groups: [platform-team]
contributors:
groups: [payments-team]
viewers:
groups: [qa-team] -
Merge the pull request. A tier change gets into the token of a person at the next sign-in. To remove access, remove the group from the tier in a pull request.
An MCP tool that proposes a change writes a pull request on a feature branch. It never writes to the main branch. A person merges the pull request.
Allow read-only access to the cloud resources of a project
Turn on mcpGcpAccess for each project that the agents may read. The block makes read-only service accounts in the project. No role of these accounts can write.
apiVersion: lowops.manifests.v1
kind: Project
metadata:
name: payments-prod
environment: production
organizational-unit: payments
organization: acme-corp
spec:
mcpGcpAccess:
enabled: true
permissions:
viewers:
groups: [payments-team]
The tier of a person on the project decides what the agent can read. The agent can have a lower tier on a production project than on a development project. See Controls for each project and environment.
If you remove the block, or set enabled to false, the engine deletes the reader service accounts. The access stops.
Run an MCP server of your own
An MCP server of your own is a container that your CI builds. Two manifests deploy it: an McpConfig for the server, and an McpDeploymentConfig for each environment.
-
Make a
BuildDefinitionthat builds the image of the server. See Set Up a Repository and CI. -
Make an
McpConfig. It names the project and the build.apiVersion: lowops.manifests.v1
kind: McpConfig
metadata:
name: orders-mcp
application-set: payments
release-track: standard
organizational-unit: payments
organization: acme-corp
spec:
description: Reads the order status for the support team
target: CLOUD_RUN
project: payments-dev
buildDefinition: orders-mcp-build -
Make an
McpDeploymentConfigfor each environment. It sets the version of the image and the scaling.apiVersion: lowops.manifests.v1
kind: McpDeploymentConfig
metadata:
name: orders-mcp
project: payments-dev
environment: development
organizational-unit: payments
organization: acme-corp
spec:
version: 0.1.0
scaling:
min: 0
max: 3 -
Open a pull request. Read the plan. Merge it.
The engine makes the Cloud Run service, a service account for the server, and an entry in the Agent Registry. Give the service account only the access that the server needs, in spec.accessControl of the McpConfig. See Mcp Config.
The health field of the McpDeploymentConfig is not yet implemented. The engine ignores it.
What is not yet available
| Need | Today |
|---|---|
| Connect the AI tool of an employee to the Infrastream MCP of your organization | Pilot. Customers cannot use it yet. |
| Show the MCP address of your organization in the portal | Not available. |
| Choose the lowest tier for each MCP route in your own manifests | Not available. The operator of the sign-in sets it. |
| Put your own MCP server behind the Infrastream gateway with the same sign-in | Not available. Your server uses the access control that you give it. |
Next
- The Agent Path: how the sign-in, the tiers and the routes work.
- Employees & Agents
- Access Tiers