Match-Trader's broker-management MCP server connects brokers and proprietary trading firms to their own Manager and Admin operational data. The vendor documents 23 read-only tools covering accounts, positions, orders, ledgers, instrument and group configuration, market data, trading sessions and risk rules. This is the broker-facing data service, not the separate trader-facing execution server.
Provides data. A read-only feed from one provider; it answers questions, doesn't act, and doesn't expect other servers alongside it. More on Source servers →All seven roles →
Vendor-verified only. The endpoint and 23-tool read-only scope come from Match-Trade's documentation; tool behavior has not been independently tested.
Restricted to Match-Trader Full Server License clients. Request an access token from Match-Trade; the endpoint alone does not grant access.
Cannot create or edit accounts, change server rules, or process deposits and withdrawals. Do not confuse it with the separate Match-Trader MCP for Traders, which can execute trades.
Broker-wide operational records can expose client identifiers and sensitive positions. Confirm the token's permissions and your firm's AI data policy before connecting.
This is broker and proprietary-trading infrastructure, not an advisor portfolio-management or suitability service. Start with read-only scopes and verify retrieved figures against the platform.
Rate this server
How to connect Match-Trader Broker Management MCP
Step 1
Remote server: paste a URL
Match-Trader Broker Management MCP publishes a remote (Streamable HTTP) endpoint, so nothing is installed locally. Add it as a custom connector in Claude, ChatGPT or your IDE and paste the endpoint below.
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.