holon-run / uxc

UXC **Universal X-Protocol CLI** A stable execution surface for agents. English | 简体中文 UXC gives agents one stable way to discover, authenticate, and call remote tools across OpenAPI, gRPC, GraphQL, MCP, and JSON-RPC. Instead of writing separate glue for each protocol, SDK, or local MCP setup, UXC turns remote interfaces into one predictable command contract with help-first discovery, structured execution, and deterministic JSON output. Why UXC Exists Agent tool use usually breaks down in the same places: • auth scattered across prompts, scripts, and local setup • different invocation models for each protocol • local MCP server names and config that are not portable across machines • large tool manifests or schemas pushed into prompt context • one-off wrappers that drift from upstream interfaces UXC exists to make remote capabilities feel like one stable execution surface for agents and automation. What UXC Does • Discover operations from an endpoint on demand • Inspect input and output shape before execution • Execute operations with structured arguments • Return deterministic JSON envelopes by default • Reuse auth bindings, signer profiles, and linked shortcuts If a target can describe itself, UXC can usually call it. Why It Works Well With Agents and Skills • Progressive discovery keeps context small: , , then execute • URL-first usage avoids dependency on machine-specific MCP aliases or local wrapper names • Auth bindings externalize credential matching instead of burying it in prompts • Linked shortcuts ( ) turn remote endpoints into stable local commands • The same command contract can be reused across many skills and workflows Core Capabilities • URL-first usage: call endpoints directly, no server alias required • Multi-protocol detection and adapter routing • Schema-driven operation discovery ( , ) • Structured invocation (positional JSON, key-value args) • Deterministic JSON envelopes for automation and agents • Auth model with reusable credentials, bindings, and signer profiles • App-credential bootstrap for short-lived bearer tokens (for example, Feishu/Lark and DingTalk) • Host shortcut commands via • Link-level default OpenAPI schema persistence via • Daemon-backed background subscriptions via • Provider-aware event transports for Slack Socket Mode, Discord Gateway, and Feishu long connection • Stdio child-process auth injection via Supported protocols: • OpenAPI / Swagger • gRPC (server reflection) • GraphQL (introspection) • MCP (HTTP and stdio) • JSON-RPC (OpenRPC-based discovery) Architecture Snapshot UXC keeps protocol diversity behind one execution contract: This design keeps discovery, auth, and execution stable while allowing protocol-specific internals. Target Use Cases • AI agents and skills that need deterministic remote tool execution • CI/CD and automation jobs that need schema-driven calls without SDK setup • Cross-protocol integration testing with one command contract • Controlled runtime environments where JSON envelopes and predictable errors matter Non-Goals UXC is not: • a code generator • an SDK framework • an API gateway or reverse proxy UXC is a stable execution surface for remote capabilities that can describe themselves. Install Homebrew (macOS/Linux) Install Script (macOS/Linux) Review before running: Install a specific version: Windows note: native Windows is no longer supported; run UXC through WSL. Cargo From Source Quickstart (3 Minutes) Most HTTP examples omit the scheme for brevity. For public hosts, UXC infers when omitted. • Discover operations: • Inspect operation schema: • Execute with structured input: Use only these endpoint forms: • • • or For nested object or array inputs, key-value mode also supports dotted and indexed paths: Protocol Examples (One Each) Operation ID conventions: • OpenAPI: (example: ) • gRPC: • GraphQL: , • MCP: tool name (example: ) • JSON-RPC: method name (example: ) OpenAPI For schema-separated services, you can override schema source: gRPC Note: gRPC unary runtime invocation requires on . GraphQL MCP MCP (stdio) UXC can also invoke MCP servers started as local processes over stdio. For stdio endpoints, the "URL" is a quoted command line. Playwright MCP (stdio) example: JSON-RPC Skills UXC provides one canonical skill plus scenario-specific official wrappers. Use skill as the shared execution layer, and add wrappers when they fit your workflow. Start Here • : canonical schema discovery and multi-protocol execution layer • : browser automation over MCP stdio through • : current library documentation and examples over MCP See for publish history, validation notes, and ClawHub maintenance details. Core and Skill Authoring • : canonical schema discovery and multi-protocol execution layer • : templates and workflow guidance for building new UXC-based skills Browser Automation and Documentation • : run over MCP stdio through • : drive Chrome DevTools MCP through • : query up-to-date library documentation and examples • : query repository documentation and ask codebase questions Workspace and Messaging • : operate Notion MCP workflows with OAuth-aware guidance • : operate Linear issues, projects, and teams through GraphQL • : operate Slack Web API and receive inbound Socket Mode events through • : operate Discord REST API and receive Gateway events through • : operate Feishu/Lark IM APIs with bootstrap-managed auth and long-connection event intake • : operate Telegram Bot API and receive updates through polling-based • : operate Matrix Client-Server API and follow room timelines through polling • : operate DingTalk OpenAPI workflows with app bootstrap auth guidance • : operate LINE Messaging API request/response workflows • : operate WhatsApp Cloud API request/response workflows Crypto and Web3 • : query Alchemy prices and market endpoints through OpenAPI • : operate Binance Spot public market data and signed account/order flows through OpenAPI • : subscribe to Binan…