MCP quickstart

1. Install

Requires macOS or Linux and Node.js 22.13 or newer.

Install the published alpha release from npm:

npm install -g @n1xyz/nord-mcp-server@0.1.0-alpha.0
nord-mcp --version

The version command should print 0.1.0-alpha.0. The package includes built JavaScript and the browser approval page; no repository access or build tools are required.

2. Connect public market tools

Choose the command for your client. These commands register a local server; the client launches it when needed.

Codex

codex mcp add nord-public -- nord-mcp serve --public --network devnet

Claude Code

claude mcp add --transport stdio nord-public -- nord-mcp serve --public --network devnet

See Claude Code's MCP setup reference for client-specific configuration and approval settings.

Other MCP clients

Configure a local STDIO server with command nord-mcp and arguments:

["serve", "--public", "--network", "devnet"]

If a desktop client cannot find the command, run command -v nord-mcp in your terminal and use that absolute path in the client configuration.

Reconnect the MCP server or restart the client after changing its configuration. Public mode exposes exactly two tools: nord_list_markets and nord_get_market. It does not load credentials or create a profile.

3. Read market data

Ask your agent:

Use Nord to find the BTC market on Devnet and show its execution mode and current pricing. If it uses a CLOB, show the best bids and asks. Do not place any orders.

The agent should discover the market ID with nord_list_markets, then call nord_get_market. RFQ data is indicative and does not provide a firm quote or promise of a fill.

For public mainnet data, replace devnet with mainnet in the server's launch arguments. The network stays fixed for the life of that server process.

4. Authorize account access

You need an existing Nord account controlled by an external Solana wallet. Trading requires collateral. The MCP package does not create accounts or fund them; see funding with the SDK.

Run setup in your terminal:

nord-mcp setup --profile personal --network devnet

1. Open the setup page in a browser with a compatible wallet, such as Phantom or Solflare, and connect the wallet that owns your Nord account.
2. Select a Nord account in the terminal if prompted. You can instead supply --account-id during setup.
3. Review the owner, network, account, session expiry, renewal deadline, storage, and authority on the approval page. Approve the message in your wallet.
4. Wait for the CLI to confirm authorization. The browser's “Signature returned” screen only confirms that it handed the signature to the CLI.

Browser approval and OS credential storage are defaults. Read Sessions and security before enabling trading, including the session key's broader authority. Email/Turnkey login and hardware wallets requiring transaction-signing fallbacks are not supported.

5. Connect the authenticated server

Use one of the following commands:

# Codex
codex mcp add nord -- nord-mcp serve --profile personal

# Claude Code
claude mcp add --transport stdio nord -- nord-mcp serve --profile personal

For another client, use command nord-mcp and arguments ["serve", "--profile", "personal"]. Disable the nord-public entry if you no longer need it; authenticated mode includes the public tools.

Only one server process can use a profile at a time. Create separate profiles if Codex and Claude Code will run simultaneously. Configure client approvals before placing orders.

Reconnect and ask:

Use the authenticated Nord server to show my connection, network, account, balances, positions, and open orders. Do not submit or cancel anything.

To switch an existing public entry instead, replace its launch arguments with serve --profile personal and reconnect. Do not combine --public and --profile. For authenticated mainnet access, create a separate profile with nord-mcp setup --profile mainnet --network mainnet; the serving process takes its network from the profile.

Continue with the tool reference.