AI-Native Trade Execution

Let Your Clients Trade Throughthe AI They Already Use

Bruno MCP turns any AI client — Claude, ChatGPT, Cursor — into an OAuth-secured, prepare-and-confirm trading terminal on your Bruno stack. No front-end to build, no inference to pay for. The connector is the product.

How It Works
9:41
ClaudeClaude
Connected to Bruno MCP
Buy limit US500, 0.10 lot @ 7,400. SL 7,370, TP 7,450.
bruno_prepare_order

Here's your order, staged and ready. Confirm to place it:

Staged orderexpires in 60s
SymbolUS500SideBuy limitVolume0.10Price7,400.0
Order placed · routed to Bruno OMS
Reply to Claude…

Why Bruno MCP?

The trading interface is no longer a screen you own. Your clients bring the AI, the AI brings them to you — a structurally cheaper business with protocol-scale distribution.

Your Clients' AI Is the Front-End

Zero Front-End to Build

Trading moves from an app you build to a tool your clients' AI calls. No proprietary terminal to design, ship, or maintain — the connector is the product.

No app to shipNo UI to maintainConnector-firstLearn more

Bring-Your-Own-AI Economics

Broker-Dealer Margins

You don't train models or pay for inference — the client's choice of LLM is their cost, not yours. The unit economics of a broker-dealer with the distribution of a protocol.

No model trainingNo inference billClient's LLMLearn more

Distribution on an Open Protocol

Protocol-Scale Reach

MCP is becoming the standard connector layer for every serious AI client. List once and any compliant client — including ones that ship next quarter — can connect.

MCP standardList onceFuture clientsLearn more

Safe by Architecture

Prepare → Confirm

Every order is staged behind a single-use, 60-second confirmation. The AI can suggest; only an explicit human confirmation routes capital. No agent loop can drain an account.

Single-use confirm60-second windowHuman-gatedLearn more

Mobile Surface, Inherited

Every AI Phone App

Every AI assistant running on phones becomes a trading surface the moment a client adds the connector. You never build, or maintain, a mobile trading app.

No mobile buildAdd onceTrade in chatLearn more

Live, Not a Slide

Deployed Today

A real order routed to a live MetaTrader 5 account in seconds — placed from a phone, in a conversation. The rails are deployed and validated end to end.

Real MT5 orderE2E validatedMulti-clientLearn more

How It Works

The AI Suggests. Only a Human Confirmation Routes Capital.

Every write tool returns a single-use confirmation valid for 60 seconds. No agent loop can compound a position; no prompt injection can drain an account.

1

Connect Once

The client's AI registers itself via OAuth 2.1 dynamic client registration and authenticates with their existing Bruno credentials. No API keys to share.

2

AI Prepares

The AI calls a prepare tool with the trade parameters. The server returns a single-use confirmation ID, valid for 60 seconds.

3

Human Confirms

The AI shows the staged order and waits. Only an explicit confirmation passes the ID to the matching confirm tool — nothing executes before that.

4

Execute Once

The order routes to Bruno OMS or MetaTrader 5 and executes exactly once. The same audit trail as a regulated broker-dealer, with conversation as the UX.

Tool Surface

30+ Tools Across 8 Modules

Clients describe what they want in natural language; their AI picks the right tool. Reads are open, every write is gated behind prepare → confirm.

Read the client's identity, trading accounts, wallets, and balance operations — the foundation every other workflow builds on.

User profile
Accounts list
Account snapshot
Wallets
Balance operations

Place, modify, close, and cancel — every write tool is gated behind the prepare → confirm contract, so nothing executes without explicit human confirmation.

Place order
Modify position
Modify order
Close position
Cancel order

Real-time quotes, OHLC history across timeframes, and full instrument metadata, so the AI can reason over live markets.

Quotes
OHLC history
Instrument detail
Instrument search

Open and closed positions, executed deals, pending orders, and full order history for complete book visibility.

Open positions
Closed positions
Deals
Pending orders
Order history

P&L breakdowns and risk-adjusted portfolio analysis the client's AI can summarize, compare, and act on.

Portfolio summary
Floating P&L
Exposure analysis

Browse curated thematic baskets, invest, top up, withdraw, and track basket performance — every write gated behind prepare → confirm.

Browse baskets
Basket detail
Invest / top up
Withdraw / close
Basket portfolio summary

Coming soon. Set financial goals, track progress, and surface automated planning and rebalancing suggestions to the client's AI.

Goal creation
Progress tracking
Rebalance suggestions

Coming soon. Discover and follow top strategies, mirror allocations, and review performance — surfaced to the AI for review and confirmation.

Discover strategies
Follow / mirror
Performance feed

Connect Your AI

One Endpoint. OAuth. Done.

OAuth 2.1 with dynamic client registration means there are no API keys to provision and no partnership integration to negotiate. A client points at the endpoint, the user signs in once with their Bruno credentials, and tools start working.

# add Bruno MCP to your AI client

$ claude mcp add --transport http bruno <your-bruno-mcp-url>

Connected to bruno · authenticate once, then trade.

Works with the AI clients your customers already use

ClaudeClaude
ChatGPTChatGPT
GeminiGemini
CopilotCopilot
CursorCursor
MistralMistral
PerplexityPerplexity
WindsurfWindsurf

+ any MCP-compliant client over Streamable HTTP

One Connector, Multiple Venues

Bruno MCP resolves the broker per account, transparent to the AI client. New venues are an adapter, not a rewrite.

OMSBruno OMSAvailable now
MT5MetaTrader 5Available now
IBKRInteractive BrokersComing soon

Roadmap

What's Next

The rails are live today. These build on the same backend.

Per-tool permission scopes

Soon

Issue a read-only connector for analysis and a separate trade-enabled connector with stricter approval rules — same backend, two clicks.

Composable natural-language workflows

Soon

Clients author their own automations as prompts. You expose the primitives; their AI builds the workflow.

Cross-AI orchestration

Soon

Let multiple agents — each with its own scoped token — hit the same execution plane simultaneously.

Connector marketplace certification

Soon

One-click install from inside the major AI clients as Bruno MCP is listed in connector directories.

Bruno Brokerage Suite

Part of the Bruno Brokerage Suite

Bruno Core

Client-Facing Trading Platform

Modern, mobile-first trading platform for your clients. Web, iOS, Android, and desktop from a single codebase.

Bruno OMS

Execution Engine

Institutional-grade order management with FIX connectivity, dealer desk, and smart routing. 10,000+ orders/sec.

Bruno Admin

Back-Office Operations

90+ modules for client management, compliance, finance, IB networks, and reporting. Included with Bruno Core.

Bruno MCP FAQ

What is Bruno MCP?

Bruno MCP is a Model Context Protocol (MCP) connector that turns any compliant AI client — Claude, ChatGPT, Cursor and others — into a secure trading terminal for your clients. Their AI reads accounts, analyzes portfolios, and executes trades against your Bruno stack through natural conversation, with no app for you to build.

How does Bruno MCP keep AI-placed trades safe?

Every write action follows a strict prepare → confirm contract. The AI calls a prepare tool, the server returns a single-use confirmation ID valid for 60 seconds, and the order only executes after an explicit human confirmation. The AI can suggest unlimited trades, but no agent loop or prompt injection can route capital without that confirmation.

Which AI clients can connect?

Any client that supports MCP over Streamable HTTP — including Claude Desktop, Claude mobile, Claude.ai web, Claude Code, ChatGPT, and Cursor. Thanks to OAuth 2.1 dynamic client registration, clients self-register and authenticate with the user's existing Bruno credentials, so even clients that don't exist yet can connect with no integration work.

Which brokers and venues does it execute against?

Bruno MCP routes against Bruno OMS and MetaTrader 5 out of the box, resolved transparently per account — you can run them in hybrid. Additional adapters, including Interactive Brokers and cTrader, are on the roadmap. New brokers are an adapter, not a rewrite.

Do I need to build a front-end or pay for AI inference?

No. The client brings their own AI, so you don't train models, host inference, or maintain a trading app. You expose the Bruno MCP connector and the client's AI becomes the interface — the unit economics of a broker-dealer with the distribution of a protocol.

How does Bruno MCP relate to Bruno API?

Bruno MCP is an add-on to Bruno API. Bruno API provides the REST, WebSocket, and FIX connectivity (with Bruno OMS and Bruno Admin included); Bruno MCP layers the Model Context Protocol on top so AI agents and LLMs can connect to the same execution, data, and risk surface through natural language.

What can the AI actually do once connected?

Across 8 modules and 30+ tools: read accounts, balances, positions, deals and order history; pull quotes and OHLC market data; run portfolio and P&L analysis; fetch manual and strategy signals; generate statements; review Copilot chat history; and place, modify, close, or cancel orders — with every trade gated behind the prepare → confirm safety contract.

Chat with us on WhatsApp