Match-Trader
MCP for Traders

Let your traders connect their Match-Trader accounts to the AI assistants they already use, like Claude and ChatGPT. They check positions, review history and prepare orders in plain language. No development work for your brokerage, and you keep control of access, limits and the audit trail.

Works with MCP clients such as

Claude ChatGPT Cursor VS Code

AI assistant
Match-Trader MCP connected

Which of my open positions have no stop loss set?

list_positions· done

Two of your 5 open positions have no stop loss:

EURUSD · BUY 0.50+42.10
XAUUSD · SELL 0.10−18.60

Place a pending order on EURUSD at 1.0850 with a 30 pip stop loss.

create_pending_order· awaiting confirmation

Here’s the order I’m about to send. Please confirm:

EURUSD · BUY LIMIT0.10 lot
Price1.0850
Stop loss1.0820
ConfirmCancel

Illustrative example. Figures are sample data.

What is Match-Trader MCP for Traders?

A remote Model Context Protocol server that connects a trader’s Match-Trader account to their AI assistant. Built on the Match-Trader Trader API, it gives the assistant controlled access to one trading account.

The assistant reads account, market and portfolio data. With the trader’s confirmation, it can also open, modify and close positions and orders.

MCP is an open standard: one server works across every MCP-compatible client, so traders aren’t tied to one AI vendor and you don’t maintain a separate integration for each.

The trader is the user. Your brokerage offers it and keeps every control. It doesn’t replace the platform, the terminal or a trading strategy.

MCP server

The Match-Trader service that exposes account data and trading operations to an AI assistant.

MCP client

The trader’s AI application, such as Claude, ChatGPT, Cursor or VS Code.

Tool

A single operation the assistant can call, such as reading open positions or placing a pending order.

Remote MCP

The server runs on the Match-Trader side. Traders install nothing.

Token

An access key per trading account, with scopes the trader selects. Revocable at any time.

Human-in-the-loop

Every action that changes the account needs the trader’s confirmation in their AI app.

From a question to the trader’s live account

Each request runs on the infrastructure your brokerage already uses. MCP adds a new way in, not a new back end.

Step 1

Trader asks

The trader writes in plain language: “Which positions have no stop loss?”

Step 2

AI app

Claude, ChatGPT or another MCP client picks the right tool and shows the trader what it intends to call.

Step 3

Match-Trader MCP

The remote server checks the token, its scopes and rate limits, then forwards the call.

Step 4

Trader API

The request runs against the trader’s account with the platform’s standard validation and limits.

Your traders use it.
Your brokerage benefits.

Your traders get a faster way to work with their accounts. You offer it with no development project and no changes to your risk set-up — and you keep the on/off switch.

FOR YOUR BROKERAGE

Offer it with zero effort

No development on your side

Match-Trader operates the MCP server on top of the existing Trader API. Nothing to build, host or maintain.

Remote server One server for every AI app Self-service tokens

Your risk controls stay in force

Orders via MCP go through the same validation, limits and audit trail as any other Trader API request.

Same validation & limits Trader confirms actions Rate limits per token & user

Control and traceability at broker level

Decide whether API access is available, cut off any single token and see which integration acted on an account.

API on/off switch Revoke from Platform Config Token name in history

FOR YOUR TRADERS

A faster way to their account

Their account, in their AI assistant

Review closed trades, check swaps and commissions, see exposure and prepare orders from live data. No exports or spreadsheets.

Their choice of assistant

MCP is an open standard. Claude, ChatGPT, Cursor or VS Code — the same server serves all of them.

A clearly defined scope

Account, market data, portfolio and trading. Reading data and changing the account are kept clearly apart.

Works with Claude ChatGPT Cursor VS Code

The control stays with your brokerage

Trading desks and compliance teams ask one question first: what happens when something goes wrong? These controls are in place from day one.

Switch API access off at broker level

Disable the API for your brokerage entirely. Traders get a 403 response telling them to contact their broker.

Revoke any token from Platform Config

The trader, the broker and Support can all revoke tokens — without affecting the trader’s other integrations.

One token, one account, chosen scopes

Each token is bound to a single trading account. Access is granted per function group, not all-or-nothing.

Rate limits that can’t be worked around

Limits apply per token and per user across all tokens. Creating more keys doesn’t raise the ceiling.

Time-limited by design

Tokens last up to one year, or shorter. Reminders go out 7 days before expiry and on the expiry day.

Confirmation before every action

The AI client shows which tool it intends to call and asks the trader to confirm anything that changes the account.

What your traders can ask

Real requests, answered from the trader’s own live data. Pick a category to see how the assistant handles it.

Account

Answered from live data

Show my open positions and work out how much swap is costing me this month.

list_positions· list_ledger· Match-Trader MCP

You have 5 open positions. Swap charges this month total −36.75 USD across 14 ledger entries:

SymbolSwap this month
GBPJPY−12.40
EURUSD−9.85
XAUUSD−8.30
2 other positions−6.20
Total−36.75

Illustrative example. Figures are sample data.

TRY ASKING

What traders can do
through MCP

Capabilities fall into four areas. Three only read data. The fourth changes the account, and every action in it needs the trader’s confirmation.

02

READ

Market data

Instrument and price data, in the context of the trader’s own account.

  • Contract size, volume limits, swaps and trading hours
  • Current prices
  • Historical candles across timeframes

get_symbols get_candles

03

READ

Portfolio

Open exposure and trading history, ready to review.

  • Open positions with P&L, swap, commission and margin
  • Closed positions, incl. the close reason
  • Pending orders and their parameters
  • Positions with no stop loss set

list_positions list_closed_positions

04

ACTION · CONFIRMED

Trading

Orders prepared in plain language and sent only after the trader approves them.

  • Open positions with SL and TP
  • Adjust SL and TP on open positions
  • Close positions in full or partially
  • Place, modify and cancel pending orders

create_pending_order cancel_pending_order

The MCP server is developed continuously and new capabilities are added over time. The current list of tools is in the documentation.

What it is, and
what it isn’t

A clear scope protects your brokerage and sets the right expectations for your clients.

IN SCOPE

What MCP does

  • Gives an AI assistant request-response access to a single trading account through the Trader API.
  • Lets traders read account, market and portfolio data in plain language.
  • Prepares trading actions that only run after the trader confirms them.
  • Applies the same validation, limits and audit trail as any other Trader API request.

OUT OF SCOPE

What MCP doesn’t do

  • It isn’t an autonomous, 24/7 trading bot. Unattended agents need their own runtime.
  • It doesn’t give investment advice or recommendations.
  • It doesn’t replace the Match-Trader platform or terminal — it’s an additional way to reach them.
  • It doesn’t connect to MT4 or MT5 accounts.

Getting started

How your traders connect

Traders set up the connection themselves. Your brokerage keeps the on/off switch and can revoke access at any time.

Generate a token

In the API Access view, create a named token for one trading account.

Choose scopes and expiry

Pick the function groups and validity — up to one year.

Configure the AI app

Add the server URL and token to the MCP configuration.

Start asking

Reads work right away; actions wait for confirmation.

  1. Set up the Match-Trader remote MCP server for me.
  2. Server URL: https://mcp.match-trader.com/mcp
  3. Authentication: Authorization: Bearer <MY_TOKEN>
  4. Add it to my MCP configuration, then verify
  5. the connection by calling get_account.

ADDRESS https://mcp.match-trader.com/mcp

Configured by hand in the AI app with an Authorization: Bearer header. Cursor or VS Code users can paste the prompt and let the assistant set it up. The documentation covers each supported client.

Frequently asked questions

What is Match-Trader MCP for Traders?

A remote Model Context Protocol (MCP) server, built on the Match-Trader Trader API, that traders use to connect their Match-Trader account to an AI assistant. It reads account, market and portfolio data and, with the trader’s confirmation, carries out trading actions.

Who uses it, the trader or the broker?

Traders use it: each trader connects their own account to the AI assistant they choose. Your brokerage offers it to clients and keeps control. You can switch API access off, revoke tokens and see in the trading history which token acted on an account.

Does my brokerage need to build or host anything?

No. Match-Trader operates the MCP server on top of the existing Trader API. There’s nothing to install on the trader’s side and nothing to integrate on yours.

How do traders connect?

The trader generates a token in the API Access view in Match-Trader, then adds the server URL and the token to their AI app’s MCP configuration. This is currently a manual configuration step. The documentation covers it for each AI client.

Can we turn MCP access off?

Yes. You can switch API access off for your brokerage entirely, in which case traders receive a 403 response asking them to contact their broker. Broker and Support can also revoke individual tokens from Platform Config.

Will the AI trade on its own?

No. MCP is a request-response layer, not a 24/7 trading bot. The AI client shows which tool it intends to call and asks the trader to confirm before any action that changes the account, such as opening, modifying or closing a position.

Do MCP orders bypass our risk controls?

No. Trading actions sent through MCP go through the same validation, limits and audit trail as the regular Trader API.

How can our dealing desk tell which orders came through an AI assistant?

Each token carries a name the trader sets. A position closed through the API records that name in its close reason, for example “Platform API — my-trading-bot-token”, so the source is visible in the trading history.

Which AI apps work with it?

MCP is an open standard, so the same server works in MCP-compatible clients such as Claude, ChatGPT, Cursor and VS Code.

Where does account data go?

Account data flows to the AI application the trader chose to connect and is governed by that provider’s data policy. Match-Trader doesn’t control how third-party AI providers process data or the quality of the model’s output.

Does it work with MT4 or MT5?

No. Match-Trader MCP for Traders is an interface to Match-Trader trading accounts only.

Your platform. Your traders’ AI assistant.
One connection.

Talk to our team about offering Match-Trader MCP for Traders to your clients.

No development on your side Broker-level control Open MCP standard

Match-Trader MCP for Traders provides a technical interface between a trading account and a third-party AI application chosen by the account holder. It doesn’t provide investment advice, recommendations or forecasts. The account holder is responsible for every order they confirm through an AI assistant. Output generated by third-party AI models is the responsibility of the respective AI provider. Claude, ChatGPT, Cursor and VS Code are trademarks of their respective owners. Their mention indicates compatibility only and doesn’t imply endorsement.