What problem does it solve? Managing UiPath AgentHub MCP server registrations involves non-obvious CLI rules—slug validation, folder context resolution, async refresh behavior, and payload shapes—that cause cryptic HTTP 400/404 errors when guessed. This Skill encodes those rules so every uip agenthub mcp and uip agenthub mcp-tools call succeeds on the first attempt. ## Core Features & Use Cases - Six server types: Create, update, delete, and refresh uipath, coded, command, remote, platform, and swagger MCP servers with the correct differentiating flags for each. - Resource tool authoring: Bind Orchestrator resources (automations, agents, agentic processes, API workflows) as tools on uipath-type servers via mcp-tools create-resource, including cross-folder targeting. - Built-in verification workflow: Enforces post-mutation verification, --dry-run inspection, and schema discovery via --print-schema and template commands. - Use Case: Register an existing HTTP MCP server as a remote AgentHub server in the Shared folder, refresh its tools synchronously, then verify with mcp-tools list—without hitting folder-resolution or slug-validation errors. ## Quick Start Register a new remote AgentHub MCP server pointing at my HTTP endpoint in the Shared folder and confirm its tools were discovered.
