Claude Revolut X connectorWhat Claude can do in your Revolut X account.
The Claude Revolut X connector exposes 21 tools. 19 read your account and the market, and 2 write only to your computer to set up access. Here is what Claude reads, why it places no orders at all, and what it checks with you first.
Verified Trustpilot reviews · AI, automation & growth agency
What the Claude Revolut X connector changes for you
You no longer need to open the app to see where your balances or orders stand on Revolut X. You ask Claude, it reads your account and the market, then answers. It does not trade, though: Revolut built this connector's server so that it cannot place, modify or cancel orders.
Review your portfolio. get_balances shows your balances, get_active_orders your pending orders, and get_order_by_id the fees on a specific order, the only tool that returns them.
Read the market. get_tickers, get_candles and get_order_book cover prices, history and depth, all as of the moment you ask.
Test an idea with no risk. grid_backtest and grid_optimize simulate a grid strategy on past data, with no order placed, and Claude reminds you that past results promise nothing.
What Claude does not do: it never places, amends or cancels an order. To trade, get_trading_setup points you to Revolut's command-line tool and its Claude Code plugin. It gives no investment advice either: Revolut forbids it from saying whether to buy, sell or hold. And nothing runs on its own; no alert fires unless you ask. For that kind of watching, you need an automation platform, a different job; the Integrations hub covers that side.
The vocabulary in one minute
Five words that make the rest of the page easier.
- Connector
- The link you install once between Claude and your Revolut X account, so Claude can look at it while answering you.
- Tool
- One named action the connector hands to Claude. Claude picks which to use; the directory sheet lists them by name.
- Authorization
- The access you grant the service for Claude. Here, according to Revolut, it goes through a key pair and an API key, not a sign-in screen.
- Approval
- The confirmation Claude waits for before carrying out something that changes anything, shown right in the chat.
- MCP
- The common standard connectors are built on; it lets an assistant talk to an outside service.
Connect Revolut X to Claude in three steps
- 01
Find Revolut X in Claude Desktop
Revolut X is a desktop extension, so it installs on Claude Desktop. Open settings, go to Customize then Connectors and look for Revolut X. On a Team or Enterprise plan, an Owner or Primary Owner has to enable it first.
- 02
Start the install
Start the connection from Revolut X's row. Revolut describes this as installing it from the Claude Desktop directory. If the extension misbehaves later, use Disconnect and add it again from the same row.
- 03
Set up your access keys
There is no sign-in screen here. According to Revolut, you ask Claude to set up your keys: it generates a key pair, you add the public key in your Revolut X profile, create an API key there and paste it back into the chat.
All 21 tools, grouped by effect
Revolut X gives Claude 21 tools: 19 that read your account, 2 that change something in it.
Two groups: what Claude reads, and the two tools that write to your computer to set up access. Tool names stay exactly as Claude shows them.
- 19 read
- 2 write
What Claude reads (19)
19 toolsNineteen tools that read your account, the market or Revolut X help, with no order placed.
get_instructions
Returns the connector's full tool inventory. Revolut notes the call is optional, since the same orientation already reaches Claude through the server's startup instructions.
get_trading_setup
When you want to trade, Claude does not do it: this tool returns installation instructions for Revolut's revx command-line tool and its Claude Code plugin, which Revolut names for placing orders, running grid bots and monitors.
get_cli_install_command
Gives the command that installs revx, Revolut's trading command-line tool. Revolut annotates it as a read-only tool.
check_auth_status
Verifies that the API credentials are configured and working. Revolut lists it as the last step of the key setup sequence, after generate_keypair and configure_api_key.
get_balances
Shows every balance on your Revolut X account: available, reserved and total.
get_currencies
Lists the currencies available on the platform, with name, asset type, precision and status.
get_currency_pairs
Lists the tradeable pairs, with step sizes, minimum and maximum order sizes, and status for each.
get_order_book
Fetches the order book for a pair, the buy and sell offers waiting to be matched. Depth is adjustable from 1 to 192 levels per side, 50 by default, with the best ask and the best bid first.
get_tickers
Gives the bid, ask, mid and last traded price, plus statistics over the past day, for all pairs or the symbols you name.
get_candles
Provides price history as candles (open, high, low, close, volume), with resolutions from one minute to four weeks. It paginates on its own when you give a start and end date.
get_public_trades
Shows the public trades on a pair, across all participants, not just yours.
get_active_orders
Brings back every order you still have open, filterable by symbol, side, state or order type (limit, conditional, tpsl). It paginates on its own.
get_historical_orders
Returns your completed orders, whether filled, cancelled, rejected or replaced, over the date range you ask for, split automatically into seven-day chunks.
get_order_fills
Lists every fill, meaning each execution, of a given order.
grid_backtest
Simulates a grid trading strategy on Revolut X candle history without placing any live order. Before running, Claude is told to have you confirm the symbol, amount, number of levels, range and split.
grid_optimize
Runs a backtest for every combination of grid levels and range percentages on past data, then ranks the results by total return. Everything stays simulated and no live order goes out.
get_order_by_id
Opens one order by its venue order ID, with the total fees paid and, for conditional and tpsl orders, their trigger details. It is the only tool that returns per-order fees.
list_kb_articles
Lists the Revolut X help articles, each with its ID and a plain-English description of the question it covers. Revolut asks Claude to call it first to pick the right article.
search_kb
Returns the full content of a help article from its exact ID, to answer questions on fees, order types, deposits, withdrawals, staking, setup or account issues.
What Claude writes to your machine (2)
2 toolsTwo setup tools that store keys locally. No source gives them their own confirmation.
generate_keypair
Approval: see the ruleGenerates a new key pair for Revolut X API authentication. According to Revolut's code, the private key is written to your computer and the public key is returned, for you to add under Profile, then API Keys, in your Revolut X account.
configure_api_key
Approval: see the ruleSaves the API key Revolut X gave you after you added your public key. According to Revolut's code, the key is stored in a local configuration folder on your computer, not in your Revolut X account.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before each action it takes on an account for you, right in the conversation.
Revolut adds its own rules, delivered to Claude through the server's instructions. Before a grid simulation, Claude has to confirm with you the symbol, amount and other parameters. Before a query covering more than 30 days or "all history", it has to confirm the scope. On Team and Enterprise, owners can also cap what a connector does across the whole organization, and members cannot override that from their own account.
Which plans include the connector
None of the 819 sheets in the official directory shows availability by plan; connector by connector, the information is not published anywhere.
The general rule is documented: desktop extensions such as this one install on Claude Desktop, while remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organization. For the current state, check the Revolut X sheet in the directory. Only Revolut documents this connector.
Where the Revolut X connector stops
A connector is not an automation: Claude calls these tools while it answers you, and no alert goes out on its own.
Revolut built the server read-only as far as your account is concerned: it cannot place, amend or cancel an order, and every tool description reminds Claude of it. The only two tools that write do so on your computer, to store your keys. The server's README also describes two transaction tools that are not on the sheet; the sheet is what tells you what Claude actually has. The directory badge is not a security audit.
Need help connecting Revolut X to Claude?
A person reads every message.
