> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neus.network/llms.txt
> Use this file to discover all available pages before exploring further.

# Install NEUS

> Connect assistants to NEUS MCP in one command.

Connect your assistant to NEUS once — portable identity, authority, and receipts travel with you across Cursor, Claude Code, Codex, and VS Code.

Install once. Reuse the same profile and trust context in every supported editor.

***

## Install

```bash theme={"dark"}
npm i -g @neus/sdk
neus setup
neus check
```

No global install? Run `npx -y -p @neus/sdk neus setup` once.

Ask your assistant:

```txt theme={"dark"}
Use NEUS so my identity, permissions, and context travel with me. Reuse receipts when you can, verify when you must, authorize actions against those limits, and leave an audit trail.
```

Your assistant reuses portable receipts for who you are and what you’re allowed to do, verifies only what’s missing, then summarizes as **Passed**, **Action needed**, or **Blocked**.

For example prompts, see [MCP journeys](./mcp/journeys).

***

## Supported tools

* Cursor
* Claude Code
* Codex
* VS Code
* MCP-compatible clients

***

## Advanced

| Topic                      | Link                                 |
| -------------------------- | ------------------------------------ |
| NEUS MCP setup             | [MCP setup](./mcp/setup)             |
| Assistant journeys         | [MCP journeys](./mcp/journeys)       |
| NEUS SDK                   | [JavaScript SDK](./sdks/javascript)  |
| Access keys (servers / CI) | [MCP setup](./mcp/setup#access-keys) |
| Trust receipt APIs         | [API overview](./api/overview)       |

For Codex, target that client during setup. The command starts its OAuth flow:

```bash theme={"dark"}
neus setup --client codex
```

Claude Code plugin (optional):

```text theme={"dark"}
/plugin marketplace add https://github.com/neus/network
/plugin install neus-trust@neus
```

**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. If both are present, `neus doctor` warns and `neus setup` soft-skips Cursor unless you pass `--client cursor` explicitly.