Longbridge MCP

What is Longbridge MCP?

The Longbridge MCP server exposes the Longbridge OpenAPI as 110 composable tools, backed by a real brokerage licensed across Hong Kong, the United States, Singapore, Japan, and New Zealand. It lets any MCP‑capable AI assistant (Claude Desktop, Claude Code, Cursor, Cline, Windsurf) read markets, route orders, and analyse positions on the user’s behalf.

How to use Longbridge MCP?

Paste the following URL into your MCP client’s config (e.g., claude_desktop_config.json) and restart the client. On the first tool call, approve the Longbridge OAuth prompt — no manual credential configuration is required.

{
  "mcpServers": {
    "longbridge": {
      "url": "https://openapi.longbridge.com/mcp"
    }
  }
}

Key features of Longbridge MCP

• Real‑time US/HK quotes, candlesticks, depth book, options chain
• Submit, cancel, replace orders; view positions, balance, margin
• Financial reports, analyst ratings, EPS forecasts, company info
• DCA plan creation, update, pause, resume, stop, execution history
• News, discussion topics, filing details, community sharelists
• Price alerts CRUD, multi‑currency P&L analytics, account statements

Use cases of Longbridge MCP

• Agent‑driven trading: route a limit order, cancel a stale trade, or compute realised P&L against actual positions
• Research and analysis: read live order books, historical candlesticks, fundamental data, and analyst ratings
• Portfolio management: monitor multi‑currency positions, cash flow, and margin in real time
• Automated alerting: create, update, or delete price alerts for any listed instrument
• DCA strategy automation: create and manage dollar‑cost averaging plans with full execution history

FAQ from Longbridge MCP

What makes Longbridge MCP different from other stock MCP servers?

Most “stock” MCP servers are single‑API wrappers over free data feeds. Longbridge MCP is backed by a real brokerage — the same tools that read the order book can also route a limit order or compute realised P&L against actual positions.

How is the server built, and what are its runtime requirements?

It is written in Rust (using rmcp 1.4 and axum 0.8), stateless — each request forwards a Bearer token to the Longbridge SDK with no server‑side sessions or database. It uses Streamable HTTP transport and is hosted at https://openapi.longbridge.com/mcp.

How is authentication handled?

OAuth 2.1 via RFC 9728 Protected Resource Metadata. Clients auto‑discover the Longbridge authorization server; nothing needs to be configured manually.

Can I self‑host this server?

Yes. A Docker image (ghcr.io/longbridge/longbridge-mcp:0.1.7) is available for self‑hosting. The server is MIT‑licensed and source is on GitHub.

Where does my trading data live?

The server is stateless — it forwards requests to the Longbridge OpenAPI and does not store any user data. Your positions, orders, and account information remain on Longbridge’s infrastructure.