"Using an MCP server to generate structured ADK agents" matching MCP servers:

Enables an AI agent to launch, monitor, and steer multiple coding agents running in tmux panes, including sending keystrokes, waiting for idle or output patterns, and managing sessions.

Enables running isolated main and sub agent tasks in networkless Docker capsules with explicit input grants, verified artifact delivery, and independent reviewer oversight via MCP tools.

Local MCP server for specialist personas, reusable Markdown workflows, task-scoped subagent contracts and per-repository memory. Runs on your own computer with Python 3.11+ and a locally installed embedding model; its Claude Code plugin launches that separate installation.

GOSCE Portfolio Router Single entry point for the GOSCE agent portfolio. Routes orchestrators to verified agents by capability with real example outputs from live self-test probes. Quality-assured broker, not a static directory. Structured Output MCP Agent Turn a prompt and field schema into validated, typed JSON using Instructor over Gemini 2.5 Flash. Ideal for extracting structured entities from

Provides a read-only MCP server for searching and retrieving cryptographically verified AI agents from the AbsoluteJS public agent registry.

Enables orchestrating multiple specialist Claude Code agents as a team, with live visualization and agent-to-agent messaging.

MCP server that wraps AI CLI tools — Claude Code, Antigravity CLI, and Codex CLI — so any MCP client can call them as tools.

nexus-agents makes your AI coding tools work together intelligently. It coordinates Claude, Codex, Gemini, and OpenCode — routing each task to the best model using data-driven algorithms, validating outputs through multi-model consensus voting, and continuously improving through outcome-driven learning. Connect it to any MCP-compatible editor (Claude Code, Cursor, VS Code) and it handles the rest.

Enables running AI agents via OpenAI-compatible APIs with custom system prompts, models, and queries. Supports persistent memory, preset agents, and multi-step workflows like pipelines and swarms.

The simplest way to bridge and collaborate across AI Agent sessions like Claude Code, Codex, Gemini, or Cursor. It allows your agents to combine their strengths to solve your most difficult tasks without leaving their current context.

An MCP server that turns a one-sentence idea into working, tested code using a pipeline of six AI agents, with optional deployment.

Enhances Claude Code's Task tool with session resumption and independent agent execution, allowing autonomous subagents from .claude/agents/ with true parallel batch support.

Enables multiple AI agents using MCP-compatible clients to collaborate in parallel on the same project across one or more machines, with direct messaging, a shared task board, atomic file/folder locking, presence tracking, and a live web dashboard.

Enables listing, inspecting, chatting with, and waking deployed Voight Agents from any MCP client, including checking agent state, usage, tasks, and GPU status.

A streaming chat agent that integrates Google ADK with Model Context Protocol and Google Maps tools, enabling users to interact with location-based services through a conversational interface.

A lightweight framework for building and orchestrating AI agents through the Model Context Protocol, enabling users to create scalable multi-agent systems using only configuration files.

Gives AI agents a self-hosted Cloudflare mailbox they can use to receive, search, wait for, read, send, reply to and forward email, with attachments and threads, over MCP or REST behind a single bearer token.

Enables one coding agent to inspect, configure, debug, and repair another agent over stdio MCP, with redacted reads and confirm-gated writes and restarts.

Enables declarative agent manifest management and deterministic brief validation for the Presentador→Orquestador flow, with tools to list/get manifests and validate brief schemas.

Enables AI assistants and other MCP clients to launch and steer Cursor Cloud Agents on repositories or as repo-less research tasks, including model selection, mid-run follow-ups, cancellation, result retrieval, and run listing. Also exposes authentication checks and per-agent or per-run token usage and cost reporting.