Register any MCP server with agent harnesses through one portable CLI and library.
Kurir keeps MCP registration behavior in one reusable implementation. Products provide a generic server specification; Kurir handles harness-specific config paths, entry shapes, scopes, backups, delegated CLIs, dry runs, and diagnostics.
It is product-agnostic. Any MCP server can use it.
cargo install kurirnpm install --global @suiflex/kurirThe npm package downloads the matching native binary for the current platform. Set KURIR_BIN to use an existing binary.
curl -fsSL https://raw.githubusercontent.com/suiflex/kurir/main/scripts/install.sh | shirm https://raw.githubusercontent.com/suiflex/kurir/main/scripts/install.ps1 | iexbrew install suiflex/tap/kurir
scoop bucket add suiflex https://github.com/suiflex/scoop-bucket
scoop install kurirCheck whether a newer release exists:
kurir update --checkInstall the latest matching native release and verify its SHA-256 checksum:
kurir updateUse --json for scripts:
kurir update --check --jsonPackage managers remain authoritative for managed installations. Use brew upgrade kurir,
scoop update kurir, cargo install kurir, or npm install --global @suiflex/kurir when
you want the package manager to own the upgrade.
Register a server with ARSY CODE:
kurir register \
--client arsy-code \
--scope user \
--name my-server \
--command my-server \
--arg mcpUse --scope project to write the connection into ARSY's workspace
configuration. Kurir delegates to the installed arsy mcp add command and
supports ARSY's stdio and http transports. ARSY's CLI has no fields for
environment variables or HTTP headers, so Kurir rejects those fields instead
of silently dropping them.
kurir register \
--client opencode \
--name my-server \
--command my-server \
--arg mcpProject-scoped registration:
kurir register \
--client claude-code \
--scope project \
--name my-server \
--command my-server \
--arg mcpPreview without writing:
kurir register \
--client cursor \
--name my-server \
--command my-server \
--arg mcp \
--dry-run \
--printLoad a complete server specification from JSON:
kurir register \
--client opencode \
--spec server.jsonKurir redacts environment values and headers in previews. Registration writes a .bak copy before replacing an existing configuration and refuses conflicts unless --force is explicit.
Remove a server by name:
kurir unregister \
--client cursor \
--name my-serverunregister takes the same --scope, --config, --cwd, --dry-run, and
--print flags as register. File-based harnesses drop only the named entry
and write a .bak copy first. Removing a server that is not configured is a
no-op that reports not-configured.
Delegated harnesses use the harness's own remove command:
| Harness | Command |
|---|---|
claude-code-cli |
claude mcp remove --scope <scope> <name> |
codex |
codex mcp remove <name> |
arsy-code |
arsy mcp remove <name> --scope <user|workspace> |
gemini-cli, hermes, and vscode report unsupported until their remove
commands are verified.
Register a lifecycle hook with a supported harness (e.g. Cursor, Claude Code, Codex):
kurir hook \
--client cursor \
--event PreToolUse \
--command "my-linter-check" \
--timeout 300Preview without writing:
kurir hook \
--client claude-code \
--event Stop \
--command "my-tool hook stop" \
--dry-run \
--printInstall a skill folder into the target harness skills directory:
OMP uses the shared .agents/skills directory for both project and user installs.
kurir skill \
--client cursor \
--path ./my-skill \
--scope project| Harness | Registration mode |
|---|---|
| ARSY CODE | arsy mcp add |
| Claude Code | JSON merge or claude mcp add |
| Claude Desktop | JSON merge |
| Codex | codex mcp add |
| Cursor | JSON merge |
| VS Code / Copilot | code --add-mcp |
| Gemini CLI | gemini mcp add |
| Copilot CLI | JSON merge |
| OpenCode | opencode.json merge |
| Windsurf | JSON merge |
| Zed | context_servers merge |
| OpenClaw | mcp.servers merge |
| Hermes | hermes mcp add |
| Antigravity CLI/Desktop | JSON merge |
| OMP | .omp/mcp.json (project) or ~/.omp/agent/mcp.json (user) merge |
| jcode | ~/.jcode/config.json mcp_servers merge (user scope) |
| ZCode | .zcode/config.json or ~/.zcode/cli/config.json mcp.servers merge |
jcode MCP registration uses the user scope. Kurir supports project and user
skills in .jcode/skills; jcode lifecycle hooks are unsupported.
OMP uses its native mcpServers map in .omp/mcp.json for project scope and
~/.omp/agent/mcp.json for user scope. For named profiles or relocated OMP
config directories, pass the intended mcp.json path with --config. OMP
lifecycle hooks remain unsupported by Kurir.
ZCode skills use .zcode/skills in each scope. ZCode hooks use the user-level
~/.zcode/cli/config.json; project-level hooks are not executed by ZCode.
ZCode ignores .agents/mcp.json within a scope when its native config defines
any MCP servers, so Kurir writes the native config directly.
Project-scope ZCode MCP registration rejects environment values and headers;
put credential-bearing servers in user scope.
Inspect the registry and local readiness:
kurir clients
kurir doctor
kurir doctor --client opencodeRust consumers can use the kurir crate directly:
use kurir::{Harness, RegistrationOptions, ServerSpec, register};
let server = ServerSpec::stdio("my-server", "my-server", vec!["mcp".into()]);
let options = RegistrationOptions::default();
register(Harness::OpenCode, &server, &options)?;To register lifecycle hooks or install skills programmatically:
use kurir::{Harness, HookSpec, RegistrationOptions, install_skill, register_hook};
use std::path::Path;
let hook = HookSpec {
event: "Stop".into(),
matcher: None,
command: "my-tool hook stop".into(),
timeout_seconds: 600,
};
let options = RegistrationOptions::default();
register_hook(Harness::Codex, &hook, &options)?;
install_skill(Harness::OpenCode, Path::new("./my-skill"), &options)?;Requirements: Rust 1.88+, Cargo, Node 18+.
cargo fmt --all -- --check
cargo clippy --all-targets -- -D warnings
cargo test
npm test --prefix npmMIT. See LICENSE.