Install Channels

Four ways in, all converge on the same jarvis-server.

Channels

Channel	Command	Best when
PyPI direct	uv tool install jarvis-mcp	You want the CLI + server with no client-specific integration — works with any stdio client
Claude Code plugin	/plugin marketplace add jarvis-intelligence/jarvis-index then /plugin install jarvis@jarvis	You use Claude Code — auto-registers the server and bundles the three skills
Codex plugin	Same marketplace source, via the repo-root Codex manifest	You use Codex CLI — auto-registers the server and bundles the three skills
MCP Registry	Entry io.github.jarvis-intelligence/jarvis, package jarvis-mcp, stdio transport	Your client discovers/installs servers through the MCP Registry

Walkthrough by client

Claude Code

Install the plugin — it registers the server and bundles jarvis-setup, jarvis-use, and jarvis-issues:

/plugin marketplace add jarvis-intelligence/jarvis-index
/plugin install jarvis@jarvis

See the Claude Code guide for the manual path and PATH troubleshooting.

Cursor

Use the one-click install link, or add the plugin marketplace, or register manually:

Add jarvis to Cursor

See the Cursor guide for the plugin marketplace path and the manual JSON block.

Codex CLI

Codex CLI has no MCP install URL scheme — use the plugin marketplace or a manual config edit:

codex plugin marketplace add https://github.com/jarvis-intelligence/jarvis-index --ref main
codex plugin add jarvis

See the Codex CLI guide for the manual ~/.codex config.

Any stdio client

Any MCP client that can launch a stdio server can run jarvis with this one block:

mcp.json

{
  "mcpServers": {
    "jarvis": {
      "command": "uvx",
      "args": ["--from", "jarvis-mcp>=0.6.0", "jarvis-server"]
    }
  }
}

See the generic stdio guide for where to paste it.

MCP Registry deep links

Client	Deep link / command
Cursor	cursor://anysphere.cursor-deeplink/mcp/install?name=jarvis&config=… — decode the config param yourself before trusting any install link
Claude Code	No URL scheme — claude mcp add jarvis --scope user -- jarvis-server (or the plugin above)
Codex CLI	No URL scheme — the plugin marketplace command above, or the manual ~/.codex config
Any other client	No registry deep link exists for arbitrary clients — see the generic stdio JSON guide

The registry entry itself lives at io.github.jarvis-intelligence/jarvis (package jarvis-mcp, stdio transport) — clients that browse the registry directly will find jarvis there without any deep link.