YAADMINCompatibility boundary#
Standards-compatible MCP servers can be connected where their transport/authentication behavior matches the currently supported YAADMIN MCP implementation.
The verified tool path is initialize → tools/list → tools/call, with notifications/initialized. STDIO process configuration and HTTP POST are supported. See MCP overview for the protocol limitations.
Tool names#
Provide stable remote names. YAADMIN retains the exact remote name for calls, while normalizing a local registry name of the form mcp.<server__tool>. Local actions are truncated to 120 characters; normalization can collide, so names differing only by unsupported characters may not remain distinct locally.
Descriptions#
Describe the real operation, inputs, target scope and consequential effects. YAADMIN exposes the description to tool-selection adapters; vague descriptions make correct selection harder. Do not encode credentials or private data in descriptions.
Input schemas#
Expose the actual inputSchema from tools/list. YAADMIN retains it in the registered descriptor. A schema describes arguments; it does not replace remote validation, authorization or safety checks.
Permissions and approval#
YAADMIN generates a permission for each discovered server/tool. A configured read-only server uses READ/POLICY metadata; other MCP tools use CHANGE/ALWAYS. The server remains responsible for its own authorization and behavior.
Current implementation notes#
YAADMIN-specific remote code is not required for supported generic tool operations. Compatibility with every MCP server, authentication extension or protocol feature is not guaranteed.