urirun documentation

urirun is a URI runtime: declare an action once as the address scheme://target/resource/operation and call it from a shell, backend, frontend, flow, or the IFURI app. It is the new path instead of hand-written shell integrations (urisys).

Two options, one contract

IFURI App — for the operator: GUI, voice, chat, device view and flow workspace. urirun — for execution: scan artifacts, generate bindings/registry and run the same URIs from CLI, a backend, or IFURI. Both options use the same URI addresses.

Start here

Getting startedInstall, scan a project, compile a registry and run a URI. Registry & bindingsHow bindings become a portable, executable registry. TransportsLocal functions, shell, Docker, HTTP, gRPC, MCP and A2A. CommandsThe urirun CLI and ifuri-app urirun-*. ExamplesFlows with urirun, IFURI and LAN services. Two optionsIFURI App or the lightweight urirun runtime — compared on the homepage.

Recommendation

For new projects use urirun (schema-first, JSON Schema validation, policy gate):

pip install "git+https://github.com/if-uri/urirun.git@main#subdirectory=adapters/python"
urirun scan ./project --out generated/bindings.v2.json --registry-out generated/registry.json
urirun list generated/registry.json

Ecosystem & external docs

docs.ifuri.com →The full ifURI documentation portal: runtime, MCP/A2A, connectors and host. MCP & A2A →How urirun projects URI addresses onto MCP tools and A2A agents. Work summary →Ecosystem state after the latest runtime, connector, app and examples work. Connector hub →Installable connector packages with manifests and one-line installers. noVNC demo →URI commands drive browsers inside noVNC desktops across the LAN. Roadmap →Direction: the runtime/host split and connector discovery.