Use @abstraxn/cli when you want a terminal-native Agent Kit experience: authenticate with your dashboard API key, list MCP tools, create agents, and chat with an LLM that calls those tools — without Cursor or a custom app.
Quick path: Dashboard setup → npm install -g @abstraxn/cli → abstraxn login → abstraxn chat --setup → abstraxn. For IDE-only MCP, see MCP in Cursor.

​
Prerequisites

​
Install

npm install -g @abstraxn/cli
abstraxn --version
If npm install -g fails with permission errors, use a user-owned npm prefix (no sudo):
mkdir -p ~/.local/bin ~/.local/lib/node_modules
npm config set prefix "$HOME/.local"
echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc
source ~/.bashrc
npm install -g @abstraxn/cli
Package: npm @abstraxn/cli

​
Login

Interactive (welcome screen + prompts): 
abstraxn login
Non-interactive (CI / scripts): 
abstraxn login --api-key "$ABSTRAXN_API_KEY" --no-welcome
Credentials are saved to ~/.abstraxn/config.json (file mode 600). See Credentials for what each secret is used for.
FlagDescription
--api-key <key>Application API key from dashboard Overview
--base-url <url>Agent Kit REST base (default: https://agent-kit.abstraxn.com)
--mcp-url <url>MCP endpoint (default: {baseUrl}/mcp)
--no-welcomeSkip welcome screen
Dev / local Agent Kit: 
abstraxn login \
  --api-key "$ABSTRAXN_API_KEY" \
  --base-url "http://localhost:3010" \
  --mcp-url "http://localhost:3010/mcp" \
  --no-welcome

​
Chat with MCP tools

The CLI runs an interactive REPL where an LLM calls Agent Kit MCP tools on your behalf (same pattern as the sample backend chat loop).

​
1. Configure the LLM (once)

abstraxn chat --setup
Or set environment variables: 
export LLM_API_KEY="your-openrouter-or-openai-key"
export LLM_BASE_URL="https://openrouter.ai/api/v1"   # optional
export LLM_MODEL="openai/gpt-4o-mini"               # optional

​
2. Start chatting

abstraxn
# same as: abstraxn chat
One-shot question: 
abstraxn "What is my wallet address on Base?"

​
In-chat commands

CommandAction
/exitLeave chat
/clearClear conversation history
/helpShow commands

​
Default agent

Wallet-scoped tools need an agent. Create or pick one: 
abstraxn agents list
abstraxn agents create --name "CLI Agent"
abstraxn agents use <agent-uuid>
When a default agent is set, the CLI uses its per-agent apiKey for MCP automatically.

​
MCP commands (without chat)

# List tools (same as smoke test tools/list)
abstraxn mcp tools

# Call a tool directly
abstraxn mcp call get_wallet_address --args '{"chain":"base"}'
abstraxn mcp call get_balance --agent <agent-uuid>
See 5-minute smoke test for raw curl equivalents and MCP tools reference for every tool.

​
Agent commands

abstraxn agents list
abstraxn agents create --name "My CLI Agent" --identity "cli-user@local"
abstraxn agents use <agent-uuid>
agents create provisions an Abstraxn server wallet via @abstraxn/agent-kit (same as SDK quickstart). The wallet accessKey is shown once — the CLI does not persist it yet.

​
Configuration

Config file: ~/.abstraxn/config.json
VariablePurpose
ABSTRAXN_API_KEYApplication API key (overrides config)
ABSTRAXN_MCP_URL / MCP_SERVER_URLMCP endpoint
ABSTRAXN_AGENT_KIT_BASE_URL / AGENT_KIT_BASE_URLREST base URL
LLM_API_KEY / OPENAI_API_KEYLLM provider API key
LLM_BASE_URLOpenAI-compatible API base
LLM_MODELModel id
abstraxn config    # show config (secrets masked)
abstraxn logout    # remove saved config

​
What the CLI can and cannot do

CapabilityCLINotes
tools/list, read-only MCP toolsYesAfter login
Chat + tool loopYesNeeds LLM_API_KEY
Create / list agentsYesVia @abstraxn/agent-kit
transfer broadcastNoNeeds stored accessKey on a backend
x402 paymentPayload signingNoUse SDK + backend
The dashboard API key is not the wallet accessKey. The CLI stores the application key for MCP; signing still requires your backend. See Credentials.

​
Compare: CLI vs Cursor vs full app

Abstraxn CLICursor MCPFull app
Installnpm i -g @abstraxn/cliCursor mcp.jsonNestJS + Next.js sample
Chat UXTerminal REPLIDE chatYour web UI
LLMBYOK (OpenRouter, etc.)Cursor modelYour choice
Agent createabstraxn agents createREST / SDKSDK in backend
SigningNot yetNot in IDE aloneBackend + accessKey

​
Troubleshooting

IssueFix
abstraxn: command not foundAdd ~/.local/bin to PATH after global install
Not logged inRun abstraxn login or set ABSTRAXN_API_KEY
MCP 401Check API key from Overview
LLM API key not configuredRun abstraxn chat --setup
Multiple agents / wallet tools failabstraxn agents use <uuid>
More: Troubleshooting