Match-Trader's trader-facing remote MCP server, announced October 6, 2026, connects one trading account to an AI assistant. Read tools retrieve account, portfolio and market data; action tools map to the Trader API to open, modify and close positions and create, modify and cancel pending orders. Access uses a revocable account token generated in the platform's API Access view.
Provides one system's data and actions. Reads and writes inside a single product of record; it can act, but only within its own walls. More on System servers →All seven roles →
Vendor-verified only. Capabilities and token controls come from Match-Trade's launch announcement and have not been independently tested.
No verbatim MCP endpoint is confirmed in the public announcement. Obtain the connection address and token instructions from your Match-Trader platform provider; a Trader API URL is not a substitute for an MCP endpoint.
Separate from the broker-management server. This connection reaches one trader account and can place or change real orders.
Client-side approval prompts depend on the AI client; they are not a guaranteed server-side execution safeguard. Keep approvals enabled, restrict the account token and revoke it when no longer needed.
The server provides no investment advice or client-specific suitability determination. A firm's supervisory procedures still govern any agent with trading access.
Start with read-only scopes and a demo account. Do not grant live trading access until every proposed action can be reviewed before execution.
Rate this server
How to connect Match-Trader MCP for Traders
Step 1
Check the vendor's documentation
This listing does not publish a public endpoint or install command yet. Open the vendor documentation above for access details, then follow the general steps in our connection guide.
Step 2
Authenticate with Bearer token
Pass a bearer token issued by the vendor's existing API in your client's Authorization header. Check how long the token lives and how it renews, and start with the narrowest scopes available.
Step 3
Verify, then widen access
Restart your client, confirm the server's tools appear, and run one read-only question first. Keep client-side approval prompts on for any tool that can write, trade or send. Confirm with your firm's compliance policy before connecting systems holding client data.
Prepare, do not stage or submit, a proposed rebalance for <account>. Take targets and current positions from the wealth platform, then use the brokerage or execution tools read-only to check tradability for each name: current quote, lot sizes, restrictions and anything that cannot be traded as intended. Show symbol, side, quantity, estimated value, rationale tied to the target model, and a tradability note with its source. Note cash impact and any position that would breach a restriction. Stop and show me the blotter for explicit approval before any order is created anywhere.
Guardrail · Proposal only. Keep trade approvals on; no order should exist without your say-so.
Post-trade reconciliation
Confirm fills matched intent, with breaks flagged.
Read-only: reconcile yesterday's executed trades against the intended blotter for <account or household>. Show intended vs. filled quantity and price, unfilled or partially filled orders, and any unexpected trade. Mask account numbers to the last four digits. Do not cancel, resubmit or correct anything, list the breaks for me to handle.
Guardrail · Read-only. Breaks get resolved by a human through the system of record.
Digital asset holdings snapshot
One consolidated view across exchanges and wallets.
Crypto & Digital AssetsCrypto & Digital AssetsBrokerage & Trade Execution
Read-only: consolidate my digital asset holdings across every connected source, exchange accounts, on-chain wallet or explorer tools, and any brokerage account holding crypto or crypto ETPs, into one table: asset, quantity, venue, source tool, USD value and share of total. Show a per-source subtotal so I can see which tool reported what, and flag any asset that appears in more than one source so it is not double-counted. Mask wallet addresses beyond the first and last four characters. Do not trade, transfer, approve or sign anything.
Guardrail · Read-only keys only. Never give a chat tool withdrawal or signing permissions.
