About OuterSpace Apizr
OuterSpace Apizr is an MCP server plugin for clients inspecting Python projects and reviewing recorded experiments. Its source analysis is read-only and does not execute project functions; analysis, history access, and delivery are controlled separately by permissions.
Key features
- 01Read-only Python source analysis
- 02Access recorded experiment history
- 03Compare experiment records
- 04Configure project access policy
- 05Separate permissions for analysis and history
Use cases
- 01Let an MCP client inspect a Python project
- 02Analyze source without running project functions
- 03Review experiment records when authorized
- 04Set which project and plugin directory the client can access
MCP support
It exposes Python project analysis and experiment-history review to MCP clients. Reading history requires history.read permission; delivery is optional and requires separate permissions.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEApizr MCP plugin
Let an MCP client inspect your Python project and review recorded experiments. Analysis reads your source without running its functions.
Use Apizr 0.4.6 with the matching plugin version. Follow the installation guide, then connect your MCP client.
You choose the project, its access policy and a separate directory for plugins.
The client needs all three paths. Install and enable the plugin before starting
the outerspace-apizr-mcp launcher.
Reading experiment history requires history.read permission. Delivery is
optional and requires its own permissions; enabling analysis does not enable it.
See the MCP guide
for tools, configuration and delivery options.
Python 3.11–3.15 · GPL-3.0-or-later · Release notes
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.