OuterSpace Apizr

io.github.Alien6-Studiov0.4.3Updated Oct 2, 2026

Python capability compiler: local read-only analysis and explicit MCP/REST exposure planning.

VerifiedSTDIODesktop onlyDeveloper Tools AI & ML

Overview

AI-generated overview

Lets an assistant analyze a local Python project read-only and plan explicit MCP or REST exposure without running its functions.

What it does: A local Python capability compiler exposed over stdio. In its default mode it offers exactly three read-only tools for analyzing a local Python project from an MCP client without executing the project's functions. The published 0.4.2 version also supports opt-in status, run and resume for an existing delivery request chosen by the operator. Delivery uses a shared coordinator and may mutate registry or proof state.
When to use it: Use it when you want an assistant to inspect a local Python project and plan how its capabilities could be exposed as MCP or REST, without executing project code. It suits operators who already run Apizr with a project file, operator policy and plugin store, and who may want to check or resume an existing delivery request.
Requirements: Local process run with uvx from the PyPI package outerspace-apizr-mcp; Python 3.11 to 3.14. The launcher needs absolute paths for a project file, an operator policy and a plugins directory, and the matching MCP plugin must be installed and activated in that separate store first. No hosted endpoint, no declared authentication, environment variables or headers.

Before you install

Installing the launcher does not install or activate the governed plugin, grant project access, or enable delivery; installation alone authorizes nothing. Enabling a version and supplying the operator policy are explicit steps, and development locks, activations and permissions are not migrated automatically. Delivery is opt-in, requires existing per-operation grants, and may mutate registry or proof state. Clients cannot choose operational paths, credentials or keys.

Installation

In SourceWeft

Open OuterSpace Apizr in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

outerspace-apizr-mcp

Analyze a local Python project from an MCP client without executing its functions. Default mode exposes exactly three read-only tools. The published 0.4.2 version also supports opt-in status/run/resume for an existing delivery request selected by the operator with --delivery-request. Clients cannot choose operational paths, credentials or keys. Existing per-operation grants remain required; delivery uses the shared coordinator and may mutate registry/proof state.

This optional Apizr plugin runs in its own Python environment. Use the installation guide to choose the matching catalog profile and verified target artifacts. The release record describes the functionality and validation for Apizr 0.4.3.

Installation does not activate a plugin or authorize its operations. Enable the chosen version explicitly and supply the required operator policy. Development locks, activations and permissions are not migrated automatically.

Registry launcher (0.4.3)

The new outerspace-apizr-mcp command delegates to apizr mcp serve. Supply --project /absolute/project/apizr.toml, --operator-policy /absolute/operator.json and --plugins-dir /absolute/plugins. Install and activate the matching MCP plugin in that separate store first. Installing this launcher through a registry client does not install or activate the governed plugin, grant access to a project, or enable delivery. Startup retains the existing admission checks and isolated plugin interpreter. No hosted endpoint is provided.

The released 0.4.2 wheel does not include this console command. The repository's server.json describes the 0.4.3 listing. Registry publication is separate from package publication. Use apizr mcp serve with published 0.4.2 installations.

See the plugin guide. Python 3.11–3.14. GPL-3.0-or-later; the full license is included.

Source: plugins/mcp/README.md at commit 0acfcda

Tools

Tool metadata has not been indexed yet.

Version history

v0.4.3LatestOct 2, 2026