NEUS Docs

Connect your editors to NEUS so they can load your account, reuse saved results, and use encrypted secrets. Hosted endpoint: https://mcp.neus.network/mcp

Quick start

Run one command:

npx -y -p @neus/sdk neus setup

Installs the trust skill, detects your editors, and signs you in. In Cursor, you can also install the neus-mcp plugin from the marketplace — it registers NEUS and runs sign-in in one click.

Daily commands

Step	Command
Connect this machine	`npx -y -p @neus/sdk neus setup`
Connect an agent to this project	`neus mount <agentId> --apply cursor`
Health check	`npx -y -p @neus/sdk neus doctor --live`
Read proofs	MCP tool `neus_proofs_get`

Access keys

OAuth is the default for IDE setup. Your MCP host discovers the NEUS OAuth metadata on first use and refreshes your session silently for up to 30 days. Use a profile access key from Access Keys only when browser OAuth is not available — servers, CI, and automation. Access keys are durable: once written to the MCP config, they do not expire.

export NEUS_ACCESS_KEY=npk_...
neus setup

When NEUS_ACCESS_KEY is set, neus setup writes a durable Bearer npk_… credential instead of starting OAuth. Run neus setup again after rotating the key. Treat access keys like passwords.

Disconnect

neus disconnect --access-key <token>

Migrate your workspace

Two paths — do not mix them up:

Goal	Command	Output
Connect a trusted agent to this project	`neus mount <agentId> --apply cursor`	`.neus/mount.json` + host rules (live receipts)
Snapshot legacy IDE config	`neus import` / `neus export`	`.neus/imported/*.json` (local scan, no proofs)

Connect a trusted agent

neus setup
neus mount <agentId> --apply cursor
neus doctor --live

See Connect agent context.

Legacy IDE import (migration only)

Import existing IDE configuration into a portable NEUS manifest, then export it for another workspace.

neus import --dry-run
neus import --from auto
neus export --to manifest

--from auto detects Claude Code, Cursor, and Claude Desktop workspaces. Named sources:

neus import --from cursor
neus import --from claude-code
neus import --from claude-desktop

Client setup

Per-editor setup commands (Cursor, VS Code, Claude Code, and more): NEUS Docs home. The setup command connects Cursor, Codex, VS Code, and Claude Code and installs the trust workflow skill. Other MCP hosts use the same hosted URL — see IDE plugin.

Host	User scope	Project scope
Cursor	`~/.cursor/mcp.json`	`./.cursor/mcp.json`
Codex	`~/.codex/config.toml` through `codex mcp add`	User-scoped
VS Code	macOS: `~/Library/Application Support/Code/User/mcp.json` · Linux: `~/.config/Code/User/mcp.json` · Windows: `%APPDATA%\Code\User\mcp.json`	`./.vscode/mcp.json`
Claude Code	`claude mcp add` → `~/.claude.json`	`./.mcp.json`

Limit to one client:

neus setup --client cursor
neus setup --client codex
neus setup --client vscode
neus setup --client claude

Start

Tool reference

Setup

Quick start

Daily commands

Access keys

Disconnect

Migrate your workspace

Connect a trusted agent

Legacy IDE import (migration only)

Client setup

​Quick start

​Daily commands

​Access keys

​Disconnect

​Migrate your workspace

​Connect a trusted agent

​Legacy IDE import (migration only)

​Client setup

Quick start

Daily commands

Access keys

Disconnect

Migrate your workspace

Connect a trusted agent

Legacy IDE import (migration only)

Client setup