Developer toolsPublic source

Infrastructure MCP Server

Cloud infrastructure management for AI agents — deploy, scale, rollback, DNS, secrets, containers, environments, costs, and health monitoring. 24 tools with Kubernetes, Vercel, Railway, Fly.io, and Custom API backends.

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Provides infrastructure capabilities through a typed MCP contract.

Architecture

How Infrastructure MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

Infrastructure MCP Server

Validates the request and owns 24 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

This repository does not currently publish a dedicated architecture SVG. The integration diagram above is generated from its documented transport and server boundary; use the official README for implementation-specific details.

Tool catalog

What can an agent ask Infrastructure MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

24 named tools

list_services

All deployed services with status

see documentation

get_service

Service details: replicas, image, URL

see documentation

get_logs

Service logs (last N lines or since)

see documentation

get_resources

CPU, memory, network usage

see documentation

get_deploy_history

Deployment history

see documentation

deploy

Deploy service (new image/tag)

see documentation

scale

Scale to N replicas

see documentation

rollback

Rollback to previous version

see documentation

restart

Rolling restart

see documentation

list_dns

List DNS records for domain

see documentation

set_dns

Create/update DNS record

see documentation

delete_dns

Delete DNS record

see documentation

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

24 see documentation

deploy, scale, rollback, promote — production_write (affects live traffic)
delete_dns, delete_secret — destructive (cannot undo)
set_secret — internal_write (doesn't affect traffic directly)
All read operations — safe, no side effects

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.

ADK MCP SDKrmcp

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install mcp-infrastructure

ADK-Rust connection shape

let toolset = McpToolset::from_stdio(
    "mcp-infrastructure",
    ["mcp-infrastructure"],
).await?;

let agent = LlmAgentBuilder::new("agent")
    .tools(toolset.tools().await?)
    .build()?;

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.md Issues and support ↗github.com issues

Keep exploring

More in developer tools.

Browse all servers →

A2A Remote Agent MCP ServerAgent-to-Agent protocol management for ADK-Rust Enterprise. Discover remote agents, send tasks, stream results, and manage push notifications — across any framework that implements the A2A protocol.11 tools ACP Workspace MCP ServerEnterprise control plane for ACP (Agent Client Protocol) sessions in ADK-Rust Enterprise. Provides 9 MCP tools for managing coding delegates — permission gates, patch review, session lifecycle, and agent exposure.9 tools CI/CD MCP ServerGive your AI agents visibility into CI/CD pipelines. This MCP server connects to GitHub Actions so agents can check build status, read logs, download artifacts, trigger deployments, and re-run failed jobs — all through…8 tools

Source record

Release and repository metadata for this catalog entry.

View public repository ↗

Version: 1.0.0
License: Apache-2.0
Tools: 24
Revision: 14054fa9f9ef
Updated: May 25, 2026

Transportsstdio