OuterSpace Apizr

Connect selected Python functions to AI agents through MCP, or expose them as REST APIs.

Apizr is an open-source capability compiler: analyze existing Python code, choose which functions are public, generate their interfaces, and define how they execute. Your business logic stays in Python.

Quickstart: make your first MCP and REST calls · The full journey

Follow Install Apizr, then the Quickstart. See the release history for version-specific functionality, compatibility and verified publication. The journey is Python code → discover/select capabilities → expose as REST/MCP → optionally deliver as OCI.

Apizr 0.4.4 adds portable JSON evidence export/verification and a bounded HTTPS check for ambiguous first-publication diagnostics. See the release record and external governance handoff for scope, validation and integration limits. Publication status is recorded in the release history.

Python 3.11–3.14 · GPL-3.0-or-later.

Choose your path

The core handles supported static analysis and generation. Generated servers have their own runtime dependencies. Optional plugins live in separate environments; installation, activation and operator authorization are independent decisions.

Expose the functions you choose

Readiness reports whether the available code evidence supports an interface. An exposure policy names the functions you choose to make public. A bundle is the generated server, its contracts and the source needed by those functions. Being ready never makes a function public automatically.

The generated MCP server calls your selected functions. The separate, Apizr analysis MCP server analyzes repositories and plans exposure; it does not execute their functions.

Choose execution boundaries

Analysis and generation do not execute the project. Starting a generated server and calling its functions does: use trusted source and dependencies. Direct mode runs functions inside the server. Governed mode uses an execution policy to choose a worker and its required limits: a fresh local process or an OCI container per call. Local workers do not isolate the host filesystem or network; containers are not an untrusted-code guarantee.

The direct Quickstart needs no Docker. Read the exposure guide for governed examples and the execution boundaries for their guarantees and limits.

Existing workflows and limits

Single-source inspect, generate rest/mcp and execute remain supported. Apizr 0.4.2 also exports verified REST bundles to Postman, Bruno and Insomnia collections, with deterministic files and safe local regeneration.

The historical pipeline is a separate compatibility path. See the full journey for dependency, resource and exposure limits.

Watch the demo · Architecture · Development and checks · Report an issue · GPL-3.0-or-later