Packaging, Installation, and MCP
Use package-ready papers as reusable releases, understand install commands, inspect package metadata, and know when MCP support is present.
What a packaged paper exposes
When Packaging Release succeeds, the run or paper can expose a package handle, version, install command, registry status, dependency metadata, README preview, and links to requirements or dependency-graph assets.
This turns the paper from a read-only artifact into a reusable release surface. Readers can inspect what the package is called, how it should be installed, and which dependencies or graph metadata were exported along with it.
pip install omegaxiv
ox install <package-handle>==<version>The paper page and run detail page both prefer this user-facing install flow once a handle is ready.
What to look for in the package and preview metadata
The package panel is most useful when it includes more than just a name. Look for requirements, registry record links, dependency graphs, README content, and a publication preview that clarifies what the package actually demonstrates.
If you are producing a release, register a preview asset deliberately. Short videos, images, audio samples, or 3D previews make the result more legible than a package handle alone.
{
"handle": "continual-activation-core",
"version": "0.4.2",
"installReady": true,
"installCommand": "pip install omegaxiv && ox install continual-activation-core==0.4.2",
"requirementsUrl": "https://example.org/requirements.txt",
"dependencyGraphUrl": "https://example.org/dependency_graph.json",
"registryRecordUrl": "https://example.org/registry/continual-activation-core.json"
}These are the user-facing fields omegaXiv surfaces once a paper version is package-ready.
How to think about MCP support
Some reusable packages may also ship MCP server metadata as part of their packaging release. Treat that as an optional extension layer for tool integrations, not as a requirement for reading the paper or installing the package itself.
The safe mental model is: first install omegaXiv, then install the package handle, then follow any package-specific MCP instructions only if that release explicitly exposes them.
If a package panel does not show MCP-oriented metadata, do not assume the server registration path exists for that release.
Use the package handle, README preview, registry links, and dependency graph as the source of truth for what is available today.