"what servers", "available", "list"?
list_servers / discover_tools
MCP control plane — register servers, discover tools, manage allow-lists, monitor health, restart unhealthy servers, and export inventory for the enterprise MCP fleet.
What this skill teaches
An MCP server tells an agent which actions are available. A skill adds the judgment around those actions: how to recognize the job, which sequence to follow, what to avoid, and how to decide that the result is complete.
Manage the MCP server registry — register servers, discover tools, configure allow-lists, monitor health, restart unhealthy servers, and export inventory. Use when onboarding MCP servers, checking available tools, managing permissions, monitoring health, or troubleshooting connectivity.
Architecture
The skill stays readable and portable because it contains instructions rather than service credentials or business data. ADK-Rust supplies it to the agent, the agent chooses from its reviewed tool boundary, and the connected MCP server performs the authenticated operation.
The agent receives a goal expressed in ordinary language.
Matches intent, supplies the decision guide, and narrows the tool boundary.
Plans the workflow and streams each meaningful step through the runtime.
Executes authenticated operations against the system that owns the capability.
The skill's completion rules shape the evidence returned to the user.
Decision guide
These routes come directly from the skill instructions. They help the model recognize intent and select a focused tool or workflow instead of improvising across the entire capability surface.
"what servers", "available", "list"?
list_servers / discover_tools
"register", "onboard", "add server"?
register_server
"health", "status", "is it up"?
health_check / inspect_server
"allow", "permission", "enable tool"?
allow_list_tools
"restart", "fix", "unhealthy"?
restart_server
"disable", "remove"?
disable_server
"export", "inventory"?
export_inventory
Proven workflows
A workflow joins several tool calls into a task the user actually recognizes. The skill explains the sequence and the intended result while ADK-Rust streams the agent's progress through the shared runtime.
List servers + available tools
Validate manifest → register
Check + restart if unhealthy
Grant/revoke tool access
Tool boundary
This allowlist is declared by the skill. It keeps the agent focused on the actions needed for this job while mcp-registry retains responsibility for authentication, validation, and the connected system.
Working rules
Operating boundaries
Install and connect
Install the repository where your ADK-Rust skill loader can discover it, connect mcp-registry, and confirm the declared tools are available before asking the agent to use the workflow.
git clone https://github.com/zavora-ai/skill-mcp-registry-management.git \
~/.skills/skills/mcp-registry-managementlet skills = SkillLoader::from_dir("~/.skills/skills").await?;
let skill = skills.load("mcp-registry-management").await?;
let agent = LlmAgentBuilder::new("agent")
.instruction(skill.instructions())
.tools(skill.allowed_tools(toolset)?)
.build()?;The repository's compatibility statement: Requires mcp-registry server connected.
Official documentation
The repository remains authoritative for its exact instructions, examples, helper scripts, assets, MCP requirements, license, and later updates.
Keep exploring
Source record
Repository metadata for this skill entry.