Abstraxn CLI

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

Node.js 18+
Application API key from Dashboard → Agentic Stack → Overview
For chat: an OpenAI-compatible LLM API key (OpenRouter, OpenAI, etc.)

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

Discover commands

abstraxn --help

The help output includes Quick start, Chat, On-chain transactions (mcp call), and Schedule a transaction examples. Inside chat, type /help for the same on-chain and scheduling tips. 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.

When prompted for an API key (login or chat --setup), input is masked as * while you type or paste — nothing is echoed in plain text.

Flag	Description
`--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-welcome`	Skip 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

Command	Action
`/exit`	Leave chat
`/clear`	Clear conversation history
`/help`	Commands plus on-chain and schedule examples

Run abstraxn --help for the full command reference.

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 — categorized output (Popular, Wallet, Payments, Trading, …)
abstraxn mcp tools

# Call a tool directly
abstraxn mcp call get_wallet_address --args '{"chain":"base"}'
abstraxn mcp call get_balance --agent <agent-uuid>

mcp tools prints a ChatGPT-style grouped list: connection header, sections with short descriptions, and total tool count. See 5-minute smoke test for raw curl equivalents and MCP tools reference for every tool.

On-chain transactions

Use abstraxn mcp call for direct tool calls, or ask in chat with natural language.

abstraxn mcp call get_balance --args '{"chain":"base"}'
abstraxn mcp call get_wallet_address --args '{"chain":"base"}'
abstraxn mcp call transfer --args '{"chain":"base","to":"0x…","amount":"0.01"}'
abstraxn mcp call get_transaction_status --args '{"chain":"base","hash":"0x…"}'

In chat:

abstraxn "What is my balance on Base?"
abstraxn "Prepare a transfer of 0.01 ETH on Base to 0x…"

transfer and swap tools return unsigned transactions. Signing and broadcast require the agent accessKey on your backend — the CLI does not store it yet. See Credentials.

Schedule a transaction

Defer execution with scheduleInMinutes, scheduleInSeconds, or executeAt (ISO 8601) on transfer or swap tools.

# In 10 minutes
abstraxn mcp call transfer --args '{
  "chain":"base","to":"0x…","amount":"0.01",
  "scheduleInMinutes": 10
}'

# At a specific time
abstraxn mcp call transfer --args '{
  "chain":"base","to":"0x…","amount":"0.01",
  "executeAt":"2026-07-03T18:00:00+05:30"
}'

Or in chat:

abstraxn "Send 0.01 ETH on Base to 0x… in 30 minutes"

Schedulable tools: transfer, evm_swap_quote, uniswap_swap_quote, lifi_swap_quote, jupiter_swap_quote, oneinch_swap_quote. Success returns status: transaction_scheduled with scheduledTransactionId. For autonomous execution and integrator webhooks (delegated MCP from CLI), see Autonomous transactions.

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

Variable	Purpose
`ABSTRAXN_API_KEY`	Application API key (overrides config)
`ABSTRAXN_MCP_URL` / `MCP_SERVER_URL`	MCP endpoint
`ABSTRAXN_AGENT_KIT_BASE_URL` / `AGENT_KIT_BASE_URL`	REST base URL
`LLM_API_KEY` / `OPENAI_API_KEY`	LLM provider API key
`LLM_BASE_URL`	OpenAI-compatible API base
`LLM_MODEL`	Model id

abstraxn config    # show config (secrets masked)
abstraxn logout    # remove saved config

What the CLI can and cannot do

Capability	CLI	Notes
`tools/list`, read-only MCP tools	Yes	After `login`
Chat + tool loop	Yes	Needs `LLM_API_KEY`
Create / list agents	Yes	Via `@abstraxn/agent-kit`
Schedule transfer / swap	Yes	`scheduleInMinutes` or `executeAt` on MCP tools
`transfer` broadcast	No	Needs stored `accessKey` on a backend
x402 `paymentPayload` signing	No	Use 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 CLI	Cursor MCP	Full app
Install	`npm i -g @abstraxn/cli`	Cursor `mcp.json`	NestJS + Next.js sample
Chat UX	Terminal REPL	IDE chat	Your web UI
LLM	BYOK (OpenRouter, etc.)	Cursor model	Your choice
Agent create	`abstraxn agents create`	REST / SDK	SDK in backend
Signing	Not yet	Not in IDE alone	Backend + `accessKey`

Troubleshooting

Issue	Fix
`abstraxn: command not found`	Add `~/.local/bin` to `PATH` after global install
`Not logged in`	Run `abstraxn login` or set `ABSTRAXN_API_KEY`
MCP 401	Check API key from Overview
`LLM API key not configured`	Run `abstraxn chat --setup`
Multiple agents / wallet tools fail	`abstraxn agents use <uuid>`

More: Troubleshooting

Getting started

SDK & wallets

Third-party integrations

Off-chain policies

Identity

Build your app

MCP

Payments

Help

Prerequisites

Install

Discover commands

Chat with MCP tools

1. Configure the LLM (once)

2. Start chatting

In-chat commands

Default agent

MCP commands (without chat)

On-chain transactions

Schedule a transaction

Agent commands

Configuration

What the CLI can and cannot do

Compare: CLI vs Cursor vs full app

Troubleshooting

​Prerequisites

​Install

​Discover commands

​Login

​Chat with MCP tools

​1. Configure the LLM (once)

​2. Start chatting

​In-chat commands

​Default agent

​MCP commands (without chat)

​On-chain transactions

​Schedule a transaction

​Agent commands

​Configuration

​What the CLI can and cannot do

​Compare: CLI vs Cursor vs full app

​Troubleshooting

​Related

Prerequisites

Install

Discover commands

Login

Chat with MCP tools

1. Configure the LLM (once)

2. Start chatting

In-chat commands

Default agent

MCP commands (without chat)

On-chain transactions

Schedule a transaction

Agent commands

Configuration

What the CLI can and cannot do

Compare: CLI vs Cursor vs full app

Troubleshooting

Related