Developer toolsPublic source

ACP Workspace MCP Server

Enterprise 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.

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.

Enterprise control plane — wraps ACP wire protocol with governance, not redefines it.

Permission-gated — file writes, shell commands, and network access require explicit approval.

Patch review — proposed changes are reviewable before application (platform-derived, not core ACP).

Full audit trail — every session, prompt, permission decision, and patch is recorded.

Bidirectional — manage coding delegates AND expose ADK-Rust agents as ACP servers.

Protocol-aligned — session/cancel as notification, session/update payload preserved in full.

Architecture

How ACP Workspace 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.

→

ACP Workspace MCP Server

Validates the request and owns 9 documented tool contracts.

→

Domain system

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

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

ACP Workspace MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask ACP Workspace 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.

9 named tools

list_participants

Show registered ACP clients and servers

read only

start_session

Start ACP session in a workspace

internal write

delegate_task

Delegate task to ACP-compatible agent

external write

get_session_updates

Get streaming session/update events

read only

handle_permission

Handle permission request from coding agent

internal write

get_proposed_changes

Retrieve proposed file changes from session

read only

review_patch

Approve, reject, or annotate a proposed patch

internal write

stop_session

Stop ACP session and capture trace

internal write

publish_agent

Publish ADK-Rust agent as ACP-compatible server

external write

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.

4 internal write3 read only2 external write

File writes require explicit permission mapped to governance policy
Shell commands require permission with command allowlist
Network access gated separately
Workspace trust boundaries enforced (can't write outside workspace)
All sessions produce audit traces
Patches reviewable before application

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-acp-workspace

MCP client configuration

{
  "mcpServers": {
    "acp-workspace": {
      "command": "/path/to/mcp-acp-workspace"
    }
  }
}

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 CHANGELOG ↗CHANGELOG.md Api Reference ↗docs/api-reference.md Architecture ↗docs/architecture.svg Issues and support ↗github.com issues

Keep exploring