NEUS Docs | Portable Trust Infrastructure

Add https://mcp.neus.network/mcp, click Connect, and reuse your current profile, agents, and proofs. No wallet or access key is required for interactive clients.

Start in three steps

Register NEUS. Add https://mcp.neus.network/mcp once (plugin, registry, or URL-only config).
Sign in. Click Connect in the host.
Check the connection. Ask for your profile and current proofs.

The host discovers sign-in from the endpoint.

Connect

Add this remote in the host MCP settings, marketplace, or registry:

{
  "mcpServers": {
    "neus": {
      "url": "https://mcp.neus.network/mcp"
    }
  }
}

If the host requires the spec type field:

{
  "mcpServers": {
    "neus": {
      "type": "http",
      "url": "https://mcp.neus.network/mcp"
    }
  }
}

Then click Connect and finish browser sign-in. If the host already offers a NEUS marketplace plugin or registry listing, install that instead of adding a second neus entry by hand.

Reuse what you have

Ask:

Reuse what I already have. Before a sensitive action, check my current proofs.

NEUS answers Passed, Action needed, or Blocked. Tool list: MCP overview and MCP tools.

One prompt

# NEUS connect in one prompt

Connect this host to NEUS so it can reuse my identity, proofs,
permissions, and private data.

1. Register the hosted MCP remote https://mcp.neus.network/mcp in this
   host (marketplace plugin, registry listing, or URL-only MCP config).
   Do not add a second neus entry.
2. Tell me to click Connect in the host MCP panel if sign-in is not done.
3. After connect, call neus_context once. Reuse existing proofs before
   asking me to verify again. Before any sensitive action (spend, publish,
   secrets, or a tool call), check proofs first. Summarize as
   NEUS Verify: Passed, Action needed, or Blocked.

Canonical endpoint: https://mcp.neus.network/mcp
Docs: https://docs.neus.network/mcp/setup

Next: create or import an agent

After Connect, ask:

Create or import an agent on my NEUS profile. Use generate if I need a
separate spend account. Set spend and action limits. Then confirm it is
ready.

That call uses neus_agent_create. Default is your signed-in account. Use generate only for a dedicated spend key. Confirm with neus_agent_link.

Do the work

Call neus_context, then create or import an agent. Chat on neus.network, or start a Pro job. To use Gmail, Slack, GitHub, or a custom server, open Connections on neus.network. Connections Cursor, Claude Code, Codex, Hermes, and Grok connect to the same endpoint. Optional project mount:

npx -y -p @neus/sdk neus mount <agentId> --apply cursor

Valid --apply values: cursor, claude, codex. See Connect agent context.

From a terminal

Optional. Writes the same hosted endpoint and the public workflow skill:

npx -y -p @neus/sdk neus setup

If a NEUS plugin is already installed, setup skips a second neus entry.

Advanced: access keys

Use Connect for interactive clients. Use a profile access key only when browser sign-in is unavailable, such as a server or CI job.

export NEUS_ACCESS_KEY=npk_...
npx -y -p @neus/sdk neus setup

Treat the key like a password. Never paste it into chat or commit it to a repository.

Disconnect

neus disconnect --access-key <token>

Troubleshooting

No tools appear: restart the MCP client after the endpoint is registered.
No Connect, or Unauthorized with Logout visible: click Logout, then Connect.
Host has no Connect: use the host’s own MCP login after the endpoint is registered.
Two neus servers: a marketplace plugin and a user MCP config both registered NEUS. Remove the extra neus key from the host MCP config. If you used the terminal installer, run npx -y -p @neus/sdk neus setup again to drop the leftover user entry.
Confirm the connection: neus doctor --live (Node).
Agent permission missing: create or refresh the agent permission on NEUS, then run neus mount again.
Search-only endpoint: use https://mcp.neus.network/mcp. https://docs.neus.network/mcp only searches documentation.

MCP overview lists the twelve tools. For a laptop, server, or confidential VM, see Private Cloud Trust Harness.

​Start in three steps

​Connect

​Reuse what you have

​One prompt

​Next: create or import an agent

​Do the work

​From a terminal

​Advanced: access keys

​Disconnect

​Troubleshooting