Skip to main content
This is optional. First-run is MCP setup: add the endpoint, click Connect, then call neus_context. To load the same agent into an editor project:
Same command for claude or codex. VS Code uses --apply cursor. This writes .neus/mount.json and the host adapter. Start a new session so the project picks it up. The editor runs the tools. NEUS supplies identity, limits, and proofs. Cursor Cloud Agents can use the hosted MCP endpoint the same way. NEUS does not spawn those VMs for you.

​
From the agent card

Connect in copies:
Valid --apply values are cursor, claude, or codex. VS Code uses --apply cursor. Run it in the project. If the host is not connected yet, run neus setup first. The browser never downloads a static rules file.

​
Assistant tool

When signed in, call neus_agent_mount with agentId. You can also use agentWallet or the identity proof ID in identityQHash. Suggested order:
  1. neus_context
  2. neus_agent_mount when acting as a specific agent
  3. neus_proofs_check / neus_verify_or_guide before sensitive actions

​
SDK

Use resolveRuntimeBundleFromMcp with your MCP transport, then applyRuntimeBundle(host, bundle, cwd) for project files. The same bundle shape is returned by the neus_agent_mount MCP tool and the neus mount CLI.

​
Where permissions are enforced

Your client controls its own tools. NEUS supplies verified context and permissions; your host remains responsible for enforcement.
Last modified on September 2, 2026