Physical & geospatialPublic source

Environment / Runtime MCP Server

Runtime control plane for ADK-Rust Enterprise. Manages runtime environments, worker pools, deployment bundles, configuration sync, provider routing, validation gates, promotion, rollback, and configuration drift…

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 environment capabilities through a typed MCP contract.

Architecture

How Environment / Runtime 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.

→

Environment / Runtime MCP Server

Validates the request and owns 10 documented tool contracts.

→

Domain system

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

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

Environment / Runtime MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask Environment / Runtime 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.

10 named tools

list_environments

Show dev, staging, production, EU production, tenant envs

read only

inspect_environment

Inspect selected environment configuration

read only

sync_environment

Sync secrets, policies, providers, memory, MCP bindings (plan/apply)

external write

run_checks

Run provider, memory, protocol, payment, and policy checks

read only

scale_workers

Scale model, graph, browser, code, realtime, payment workers

internal write

promote_release

Promote immutable release bundle to target environment

external write

rollback_release

Roll back to previous release bundle

external write

audit_trail

Inspect release events and promotion evidence

read only

detect_drift

Detect configuration drift from expected state

read only

worker_status

Get detailed worker pool status for an environment

read only

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.

6 read only3 external write1 internal write

The registry manifest declares read only, external write, internal write tool risk classes.

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.

Prompts

ADK MCP SDKrmcpRegistry manifest

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-environment

MCP client configuration

{ "environment_id": "env_prod" }

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.