https://mcp.neus.network/mcp
Quick start
Run Install NEUS first (neus setup · neus check). Return here for access keys, disconnect, migrate, and per-editor config paths.
neus setup detects your editors, configures hosted MCP, and signs you in. By default it uses browser OAuth for Cursor, VS Code, and Claude Code. If you set NEUS_ACCESS_KEY first, the CLI uses that key instead. Pass --access-key <npk_...> to override, and --json for scripted installs.
Daily commands
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.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
Migrate your workspace
Two paths — do not mix them up:Connect a trusted agent
Legacy IDE import (migration only)
Import existing IDE configuration into a portable NEUS manifest, then export it for another workspace.--from auto detects Claude Code, Cursor, and Claude Desktop workspaces.
Named sources:
Client setup
Per-editor install paths (Cursor, VS Code, Claude Code, and more): Install NEUS.neus setup connects Cursor, Codex, VS Code, and Claude Code in one command. Other MCP hosts (including Cline) use the same hosted URL — see IDE plugin.
Cursor: install the neus-trust plugin or run neus setup --client cursor — not both. The plugin already provides the neus MCP server; adding a second entry in ~/.cursor/mcp.json creates a duplicate. neus setup soft-skips Cursor when the plugin is detected (pass --client cursor to override). Public tools = 13 (correct).
Limit to one client: