TradingPlace MCP Server

The TradingPlace MCP Server gives any MCP-compatible client a safe, org-scoped way to read live trading state, place and manage trades, and review closed trade history with P&L through the TradingPlace broker proxy layer.

What You Need Before You Start

What The MCP Server Can Do

Read live state

List eligible accounts, check which ones are connected, and inspect open trades and pending orders before taking action.

Place new trades

Submit orders to one or more selected accounts with market, limit, or stopmarket workflows plus bracket logic.

Manage active positions

Close trades, move stop loss, and move take profit using the returned trade and order identifiers.

Review closed trades

Pull today's closed trades with realized P&L per account to track performance and inform next decisions.

Build automated workflows

Use the same tools inside structured prompts, agent loops, or voice-driven workflows with your own safety rules.

Connect Your MCP Client

The TradingPlace MCP Server uses OAuth for authentication. Your MCP client handles the OAuth flow automatically — no tokens to copy or manage.

Transport: Streamable HTTP
URL: https://www.tradingplace.us/mcp/trading
  1. Open your MCP client's server settings.
  2. Add a new remote MCP server.
  3. Choose Streamable HTTP as the transport.
  4. Enter the TradingPlace MCP URL shown above.
  5. Save and connect — your client will open a TradingPlace sign-in page to authorize access.
  6. After authorization, test with tp_whoami to confirm the connected org.

Note: TradingPlace OAuth grants org-scoped access only. The MCP server can only see accounts and trades belonging to your organization. You can revoke access at any time from your TradingPlace portal settings.

Tool Set

  • tp_whoami — returns the authenticated org and connection status.
  • tp_list_accounts — lists org-linked accounts with live connection state.
  • tp_get_state — returns accounts, open trades, pending orders, and disconnected users.
  • tp_get_closed_trades — returns today's closed trades with realized P&L per account.
  • tp_place_order — submits trades across explicit account selections.
  • tp_close_trade — closes live trades and cancels matching pending entries.
  • tp_modify_stop_loss — moves stop prices for an existing trade.
  • tp_modify_take_profit — moves take-profit prices for an existing trade.

Recommended First Workflow

  1. Confirm who you are connected as with tp_whoami.
  2. List trade-enabled accounts and confirm the ones you want to target.
  3. Get current state before placing or editing any order.
  4. Place a trade with explicit symbol, side, contracts, and account selection.
  5. Store the returned tradeGuid and orderGuid values for later management.
  6. Use those IDs for stop, target, or close actions.
  7. Review closed trades and daily P&L to assess performance.

Safe Usage Rules

Use explicit account selection

Only fan out to all trade-enabled accounts when that is your deliberate intent. Otherwise tell Claude exactly which accounts to use.

Read before you write

Call tp_list_accounts and tp_get_state before every trade decision, especially inside bot loops.

Revoke access when needed

You can revoke OAuth access at any time from your TradingPlace portal settings. No tokens to rotate or secrets to manage.

Save trade identifiers

Follow-up management actions are much safer when your workflow stores the returned tradeGuid and orderGuid.

Example Prompts

Show me all trade-enabled TradingPlace accounts and which ones are connected.

Get my current state and summarize any open trades or pending orders.

Buy 1 MNQ on account refs TP-101 and TP-204 with a 20 tick stop and 40 tick target.

Move the stop loss for tradeGuid claude-12345 to 19452.00.

Close the trade with orderGuid 7e1c... and tell me what happened.

Show me today's closed trades and P&L across all accounts.

Bot And Voice Workflow Ideas

Get Started

MCP access is available to all TradingPlace organizations. Questions? Email support@tradingplace.us.

Resources Connecting Accounts →