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

# AI assistants in Parallax Wallet

> Let Claude and other AI assistants read the chain through your own node, and, as far as you allow, see your wallet and ask the app to act, each request approved by you.

[Parallax Wallet](../client/desktop), the desktop app, has an MCP server
built in. An AI assistant such as Claude connects to it on your computer
and answers from **your own node**: blocks, transactions, balances,
contracts, the mempool and mining, with none of it looked up on a public
server.

As far as you allow it, the assistant can also see your node's status and
logs, your wallet's accounts and your address book, start the node, and
ask the app to do things for you: send LAX, stop the node, change settings, create
an account, follow an address or add a contact. Each request waits for
you to approve it in the app.

It uses the same tools as the [public Parallax MCP server](./parallax-mcp),
so everything that guide says about asking questions applies here too.

***

## Public server or Parallax Wallet?

| | Public server | Parallax Wallet |
| - | - | - |
| Chain data from | The public RPC | Your own node |
| What you look up | Goes to a shared server | Stays on your computer, unless you allow the public explorer or status page |
| Explorer and network health | Always | When you allow them |
| Your wallet and address book | No | When you allow them |
| Asks the app to act | No | When you allow it, each request approved by you |
| Needs | Nothing | Parallax Wallet running, with its node |

***

## Turn it on

<Steps>
  <Step title="Open the assistant settings">
    In Parallax Wallet, open **Settings → AI assistants → Overview** and
    turn on **Assistant access**. Save.
  </Step>

  <Step title="Copy the connection">
    Under **Connect an assistant**, choose **Claude Code** or **JSON
    config** and copy it. It holds the server's address and its access
    token.
  </Step>

  <Step title="Choose what assistants may do">
    Open **Settings → AI assistants → Permissions**. To begin with, the
    node's status is allowed and everything else asks you first. You can
    leave it that way and decide as assistants ask.
  </Step>
</Steps>

The server listens on `127.0.0.1:8549` by default; you can change the
port in Overview.

<Note>
  The assistant server doesn't need HTTP-RPC (**Settings → RPC**): it
  reaches the node inside the app, as the wallet does. It does need the node
  running: while the node is stopped, a tool that needs it has it started
  first, as **Start the node** allows (see [Permissions](#permissions)), and
  carries on.
</Note>

### Claude Code

Run the command you copied in a terminal. It looks like this, with your
own token:

```bash theme={null}
claude mcp add --transport http parallax-wallet-app http://127.0.0.1:8549/mcp \
  --header "Authorization: Bearer <token>"
```

Add `-s user` after `claude mcp add` to have it in every project. Then run
`/mcp` in Claude Code to check that `parallax-wallet-app` is connected.

### Other assistants

The JSON config works for MCP clients that read an `mcpServers` config,
such as a project's `.mcp.json`:

```json theme={null}
{
  "mcpServers": {
    "parallax-wallet-app": {
      "type": "http",
      "url": "http://127.0.0.1:8549/mcp",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}
```

The client must run on the same computer as Parallax Wallet, and support
Streamable HTTP with a custom header.

***

## The assistant bar

While an assistant is connected, a small round bar sits at the bottom
right of the window, beside the node bar, with a dot for its state. Point
at it to see who is connected, such as *"Claude Code connected"*.

* **At work.** While an assistant uses a tool, the robot gives way to a
  spinner, and pointing at the bar says what it's doing: *"Claude Code is
  checking a balance…"*, or *"…is waiting for block 10…"* while it waits
  on the chain. A **✕** beside it stops that: the tool's work ends, and
  the assistant is told you cancelled it.
* **On a request.** When an assistant asks for something, the bar opens
  into the request, lit blue, pushing the node bar aside, and closes again
  once you've decided (see [Approving requests](#approving-requests)).

With no assistant connected, the bar isn't shown.

***

## Permissions

You choose, feature by feature, what assistants may see, do and ask for.
Each permission is set to one of:

* **Allow:** assistants use it without asking.
* **Ask:** the app asks you the first time an assistant uses it (see
  below).
* **Block:** refused, without asking you.

Changes apply as soon as you save, even for an assistant already
connected.

### When an assistant asks for permission

Like Claude asks before it uses a tool, Parallax Wallet asks you before an
assistant uses a feature set to **Ask**. The prompt names the tool and
what it gives the assistant, and offers:

* **Allow once:** this assistant may use it until it disconnects (or goes
  half an hour without it). Other assistants are asked again.
* **Always allow:** the permission becomes **Allow**, for every assistant.
* **Don't allow:** refused this time.

The assistant waits up to 2 minutes for your answer, then is told you
didn't answer.

### What assistants can see

| Permission | What it shows |
| - | - |
| **Chain data** (always) | Blocks, transactions, balances, contracts, the mempool, mining and the docs, from your node |
| **Node status** (allowed by default) | Whether the node runs and syncs, peers, uptime and version |
| **Logs** | The node's and the app's log, which can name peers' addresses |
| **Wallet** | Your accounts, their names, balances and activity, your recovery phrases by name (never their words), and your hardware wallets by name, with which accounts sign on a Ledger or Trezor |
| **Address book** | Your contacts' names, addresses and notes |

Everything an assistant reads goes to its provider along with your
conversation. Turning on **Wallet**, for example, lets the provider see
which addresses are yours.

### Public services

| Permission | What it adds |
| - | - |
| **Block explorer** | Address histories, token balances and transfers, verified contract sources and search, from [explorer.parallaxprotocol.org](https://explorer.parallaxprotocol.org). Transactions and events are decoded with verified sources too. |
| **Status page** | Network health and alerts, recommended confirmations, incidents and network-wide mining figures, from [status.parallaxprotocol.org](https://status.parallaxprotocol.org) |

Both are off by default: everything comes from your node. With them on,
what the assistant looks up there leaves your computer. Changing them
restarts the assistant server, so connected assistants reconnect (in
Claude Code, from `/mcp` if it doesn't on its own). The development chain
never uses them, as they describe mainnet.

### What assistants can do

| Permission | What it does |
| - | - |
| **Start the node** | Starts the node when it's stopped: when an assistant asks to, and when a tool it uses needs the node. Set to **Ask**, the prompt says the node is stopped; allowed, the node starts and the assistant's request carries on. |

### What assistants can ask for

These don't act on their own. The assistant asks, and the app shows you
the request to approve or turn down, every time, so these are set to
**Ask** or **Block**: Block stops assistants from asking at all.

| Permission | The request |
| - | - |
| **Stop the node** | Stop the node |
| **Settings** | Change settings: appearance, logging, sync, peers, caches, the transaction pool, fee estimates and RPC limits |
| **Create accounts** | Create a wallet account, with a new key or the next one from a recovery phrase |
| **Watch-only accounts** | Follow an address whose key is kept elsewhere |
| **Edit the address book** | Add a contact, or change one |
| **Send transactions** | Send LAX from one of your accounts, approved with the wallet password, or on the device for a hardware wallet account |

***

## Approving requests

When an assistant asks for something, the assistant bar opens on the
request wherever you are in the app, with a desktop notification if the
window is in the background and notifications are on. It shows exactly
what would happen:

* **Settings:** each setting before and after, when it takes effect, and
  a warning on sensitive ones (those that open the node to other programs
  or share something about it).
* **Contacts:** the address in full, and the old values when a contact
  changes. Check the address: a contact is where you'll send funds.
* **Sends:** the amount, the account it comes from, the recipient in full
  and who it is (one of your accounts, a contact, or an address you have
  never sent to, with a warning), the network fee, the total and your
  balance after. Amounts are exact, never rounded. You approve with the
  wallet password, which goes to the wallet, never to the assistant. The
  app refuses beforehand what your balance doesn't cover, or a fee over
  your fee cap (1 LAX unless you changed it). From a watch-only account,
  approving makes a signing request to sign on your offline signer. From
  a hardware wallet account, there's no password: approving sends it to
  your Ledger or Trezor, where you check it against the request and
  confirm or reject it. If the device isn't connected and ready (unlocked,
  with the Ethereum app open on a Ledger), the request stays for you to
  try again. Sends are plain LAX transfers: assistants can't ask to call
  contracts.
* **Accounts:** the new account's name and where its key comes from. You
  type the wallet password in the app; it goes to the wallet, never to
  the assistant.

The assistant's reason is shown in quotes, as its words. The approving
button names what it does (**Sign and send**, **Change settings**,
**Create account**, **Add contact** and so on) and carries out exactly
what was shown; **Don't allow** refuses it. Requests come one at a time,
the next taking the bar's place once you've decided. A request not decided
within 10 minutes expires, and no more than five wait at once. The
assistant is told the outcome.

Once a send is made, the bar confirms it: the amount, where it went, and
the transaction's hash to copy. It stays while you point at it, and closes
two seconds after you move away.

Some settings can never be requested: RPC addresses, APIs and CORS,
proxies and Tor, peers and bootnodes, network restrictions, the fee and
disk guards, data directories, update checks, offline signing and the
assistant settings.

***

## What assistants can never do

Whatever you allow, no assistant can:

* See recovery phrases, or export, import or back up keys.
* See or change the wallet password.
* Sign or send a transaction without your approval and the wallet
  password, or, from a hardware wallet account, your confirmation on the
  device.
* Remove accounts, recovery phrases or contacts.
* Open the node to the network.
* Turn offline signing on or off, or change what assistants may do.

It can build an unsigned transaction for you to check and sign yourself.

***

## Safety

* **Local only.** The server listens on `127.0.0.1`, so only programs on
  your computer reach it.
* **Access token.** Every request needs the token. **New token** in
  Overview replaces it and disconnects every assistant set up with the old
  one; set them up again with the new command.
* **Not from web pages.** Requests from web pages are refused, and so are
  those using another host name, a trick web pages use to reach local
  servers.
* **Read-only to the node.** Every request to the node passes the same
  read-only allowlist as the public server.
* **Untrusted text.** Token names, contract strings, log messages and
  imported contacts are marked as data the assistant must not follow.

<Warning>
  Assistants can be misled by what they read: a web page, a token's name or
  a contract can carry instructions meant to steer them. Approve only
  requests you meant to make, and check addresses yourself.
</Warning>

***

## Troubleshooting

| Problem | What to do |
| - | - |
| The assistant bar isn't showing | It shows only while an assistant is connected. Check the assistant's connection (in Claude Code, `/mcp`). |
| Overview says the server could not start | Its port is taken, often by another copy of Parallax Wallet. Choose another port. |
| The assistant says the node is stopped | **Start the node** is set to **Block**, or you turned the prompt down. Start it in the app, or set it to **Ask** or **Allow**. |
| The assistant says you don't let it | That permission is set to **Block**: change it in **Settings → AI assistants → Permissions**. |
| The assistant says you didn't answer | A prompt waited 2 minutes. Ask again and answer it in the app, or set the permission to **Allow**. |
| The assistant can't connect after a change | Changing the port or the public services restarts the server: reconnect, in Claude Code from `/mcp`. A new token needs the server added again. |
| A send from a hardware wallet account waits | Connect and unlock the device (on a Ledger, open the Ethereum app), then approve the request again: it stays until you do. |
| No explorer data or network health | Turn on **Block explorer** or **Status page** under Permissions. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.