@porio/install

One-shot interactive installer that wires the Porio MCP server into your AI coding harness of choice.

npx @porio/install <your-porio-token>

The installer walks you through three prompts:

1. Token management — inline the token in the MCP config (easiest) or reference it via $PORIO_TOKEN.
2. Scope — install for the current project only, or globally.
3. Harnesses — Claude Code, Cursor, VS Code (Continue), Codex CLI. Pick any combination.

It then writes the right config files for each harness, preserving any existing MCP entries you already have.

Get a token

Create a long-lived org-scoped API key at https://app.porio.ai/settings/api-keys.

Supported harnesses

| Harness | Global config | Project config | Extras written | | ------------------ | ------------------------ | --------------------------- | --------------------- | | Claude Code | ~/.claude.json | <project>/.mcp.json | slash command + skill | | Cursor | ~/.cursor/mcp.json | <project>/.cursor/mcp.json| — | | VS Code (Continue) | ~/.continue/mcpServers/porio.yaml | <project>/.continue/mcpServers/porio.yaml | — | | Codex CLI | ~/.codex/config.toml | (machine-wide only) | — |

Codex CLI has no project-scoped config — the porio entry lives in ~/.codex/config.toml regardless of the scope you pick.

What the installer wires

Every harness ends up launching the same stdio MCP server:

npx -y -p @porio/cli porio mcp

with PORIO_TOKEN either inlined (direct mode) or referenced from your shell env (env mode).

Uninstall

The installer is purely additive — nothing is registered with your OS. To remove:

• Claude Code — delete the porio entry under mcpServers in ~/.claude.json or .mcp.json, plus .claude/commands/porio.md and .claude/skills/porio/.
• Cursor — delete the porio entry under mcpServers in ~/.cursor/mcp.json or .cursor/mcp.json.
• Continue — delete ~/.continue/mcpServers/porio.yaml or the project-local equivalent.
• Codex CLI — delete the [mcp_servers.porio] section (and [mcp_servers.porio.env]) from ~/.codex/config.toml.

Hidden non-interactive mode

For CI / smoke tests:

PORIO_INSTALL_NONINTERACTIVE=1 node bin.js <token> \
  --target=claude-code,cursor,vscode,codex \
  --scope=global \
  --token-mode=direct \
  --config-root=/tmp/porio-install-smoke

--config-root reroots all writes under one tmpdir for safe testing.

Publishing

The user publishes manually (OTP-protected):

cd porio-install
npm publish --access public

Bump the version in package.json first.