Skip to content

Packages

Packages and Registries

Know which Origin package name maps to the plugin, runtime setup, MCP connector, Rust crates, and release binaries.

Qi-Xuan LuUpdated 4 min read

At a glance

01

Origin has several public package names because one local product crosses Claude Code plugins, npm setup, MCP clients, Rust crates, and release binaries.

02

Most users should not choose a registry by hand. Install through Claude Code or npx setup, then let origin mcp add wire each client to the local connector.

01

Why the names differ

Origin is one local memory layer with several runtime surfaces. The daemon owns memory, the CLI manages setup and diagnostics, origin-mcp bridges MCP clients, and the Claude Code plugin adds the slash-command workflow.

The registry names map to ecosystems, not separate products. When docs mention several names, they are usually describing different entry points into the same local daemon.

Public surfaces

@7xuanlu/origin      Claude Code plugin package and setup entrypoint
origin-mcp          MCP connector package and Rust crate
origin-types        Shared HTTP/MCP wire types
GitHub Releases     Stable binaries, tags, and release notes

02

Normal install paths

Claude Code users should use the plugin marketplace path, then run /init. That verifies the plugin, local daemon, MCP route, and a memory round trip from inside Claude Code.

Other MCP clients should run the setup package once, then use origin mcp add for each client. That keeps client config pointed at the local connector installed under ~/.origin/bin.

Install paths

# Claude Code
/plugin marketplace add 7xuanlu/origin
/plugin install origin@7xuanlu
/init

# Other MCP clients
npx -y @7xuanlu/origin setup
~/.origin/bin/origin mcp add codex

# Manual MCP fallback
npx -y origin-mcp

03

MCP connector packages

origin-mcp is the connector MCP clients launch when they need Origin tools. Normal setup installs a local origin-mcp binary beside the CLI so configs can use a stable machine-local path.

The standalone npm package is useful when a client or automation flow needs to spawn the connector through npm. Prefer the installed local binary when setup has already prepared ~/.origin/bin.

Read MCP client setup

04

Rust crates

origin-mcp is also published as a Rust crate because the connector ships from the Rust workspace. Most users never install this crate directly.

origin-types contains shared HTTP and MCP wire types for downstream Rust clients. It exists so integrations can fail loudly on shape drift instead of passing around untyped JSON.

05

GitHub releases

GitHub Releases are the stable release record for tags, binaries, and changelog-backed behavior. If a page describes unreleased main-branch work, it should say so explicitly.

When you need to know whether a behavior is shipped, read the changelog before assuming a merged PR is in the package you installed.

Read the changelog

06

Verify your install

After changing packages, verify the runtime first. status and doctor tell you whether the local daemon is healthy before you debug an MCP client.

Then run origin mcp add with --dry-run for the client you care about. The output shows which connector path the client should launch.

Verification

~/.origin/bin/origin status
~/.origin/bin/origin doctor
~/.origin/bin/origin mcp add codex --dry-run
~/.origin/bin/origin mcp add cursor --dry-run

Next

Platform Support

Understand how Origin runs on macOS, Linux, and Windows: service managers, local data paths, model backends, and Docker/VM caveats.

Read next