MCP server registry
Data & contentPublic source

ADK Rust MCP Toolkit

Production-ready Model Context Protocol (MCP) servers for generative media, built in Rust. Generate images, videos, music, and speech through a unified, provider-agnostic interface.

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.

01

🖼️ Image Generation — Text-to-image with Imagen 3 and Gemini multimodal models

02

🎬 Video Generation — Text-to-video, image-to-video, video extension with Veo 3.1

03

🎵 Music Generation — Full songs with Lyria 3 Pro/Clip, real-time streaming with Lyria RealTime

04

🗣️ Speech Synthesis — High-quality TTS with Chirp3-HD and Gemini voices (30 voices, 70+ languages)

05

🎛️ Media Processing — FFmpeg-powered audio/video manipulation

06

🔌 Multiple Transports — Stdio, HTTP, and SSE for any integration scenario

07

🔑 Dual API Support — Works with both Vertex AI (ADC) and Gemini API (API key)

Architecture

How ADK Rust MCP Toolkit 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.

01

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

02

MCP client

Discovers schemas, sends calls, and receives typed content.

03

ADK Rust MCP Toolkit

Validates the request and owns 44 documented tool contracts.

04

Domain system

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

Connection: stdio · streamable HTTP · SSE · Server framework: 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 ADK Rust MCP Toolkit 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.

The README documents 44 tools as grouped capabilities.

Open the official API reference or README below for the authoritative tool names and input schemas.

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.

  • Review the server documentation and deployment credentials before enabling it for an agent.

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.

Resources
Prompts
rmcp

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 adk-rust-mcp-image adk-rust-mcp-video adk-rust-mcp-music \
MCP client configuration
# Option 1: Gemini API (recommended for getting started)
export GEMINI_API_KEY=your-api-key  # from https://aistudio.google.com/apikey

# Option 2: Vertex AI (for production/enterprise)
export PROJECT_ID=your-gcp-project
export LOCATION=us-central1
export GCS_BUCKET=your-bucket  # Required for video generation on Vertex

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.

Source record

Release and repository metadata for this catalog entry.

View public repository ↗
Version
Source release
License
See LICENSE
Tools
44
Revision
1e55050efef0
Updated
May 24, 2026
Transportsstdiostreamable HTTPSSE