Longbridge MCP 服務

Longbridge 提供託管的 MCP（Model Context Protocol）服務，讓你在 ChatGPT、AI 編程助手或其他對話工具中直接使用 Longbridge 的行情與帳戶能力，無需手動管理 API 金鑰。

MCP 服務地址

全球：https://mcp.longbridge.com
中國大陸：https://mcp.longbridge.cn（訪問更快）

美國賬戶請使用全球地址 —— .cn 沒有通往美國數據中心的鏈路，僅服務 AP 賬戶（新加坡 / 香港）。詳見接入點與數據中心。

可用能力

Longbridge MCP 暴露 160+ 工具，覆蓋六大能力域，客戶端連接後會自動發現——無需手動配置。

能力	覆蓋範圍
即時行情	報價、K 線、深度、經紀隊列、逐筆、分時資金流
基本面與研究	公司資料、派息、估值、高管持倉、A/H 溢價、宏觀經濟指標
衍生品	期權鏈、窩輪篩選、發行商、窩輪報價
賬戶與組合	餘額、持倉、資金流水、自選股及分組
交易	下單、改單、撤單、可買量估算
自動化	股價提醒、定投（DCA）計劃

實際可用工具因地區、帳戶等級與 OAuth 授權範圍而異。

可用工具

account_balance

ah_premium

ah_premium_intraday

alert_add

alert_delete

alert_disable

alert_enable

alert_list

anomaly

authenticate

bank_cards

broker_holding

broker_holding_daily

broker_holding_detail

brokers

business_segments

business_segments_history

calc_indexes

cancel_order

candlesticks

capital_distribution

capital_flow

cash_flow

company

consensus

constituent

corp_action

create_watchlist_group

dca_check

dca_create

dca_history

dca_list

dca_pause

dca_resume

dca_stats

dca_stop

dca_update

delete_watchlist_group

deposits

depth

dividend

dividend_detail

estimate_max_purchase_quantity

etf_docs

exchange_rate

executive

filings

finance_calendar

financial_report

financial_report_key_metrics

financial_report_latest

financial_report_snapshot

financial_statement

forecast_eps

fund_holder

fund_positions

grid_cancel

grid_detail

grid_list

grid_list_by_ids

grid_questionnaire

grid_replace

Replace an existing grid order's rule by order_id. Accepts the same grid rule fields as grid_submit. Overwrites the order's entire rule. TWO-STEP CONFIRMATION IS MANDATORY: this tool is a DRY RUN unless you pass the confirmation_code its own dry run returned. Call it first without execute, show the returned preview to the user, and only call it again with execute="<confirmation_code>" after the user has explicitly confirmed it. The code is derived from the order itself, so it applies only to that exact request. Never quote it back on your own initiative. The dry run echoes the rule that would replace the current one.

參數

order_idstring必填: Grid order ID to replace.
submitted_base_pricestring: Base price the grid is anchored to (decimal string).
upper_limit_pricestring: Upper price bound (decimal string).
lower_limit_pricestring: Lower price bound (decimal string).
trigger_price_typeinteger: Trigger price type: 1 = spread (absolute), 2 = percent.
trigger_spread_upstring: Upward trigger spread, absolute (decimal string; use with type 1).
trigger_spread_downstring: Downward trigger spread, absolute (decimal string; use with type 1).
trigger_percent_upstring: Upward trigger percent (decimal string; use with type 2).
trigger_percent_downstring: Downward trigger percent (decimal string; use with type 2).
multiple_triggerboolean: Whether one grid level may trigger multiple times.
time_in_forceinteger: Time in force: 0 = Day, 1 = GTC, 6 = GTD.
upper_limit_quantitystring: Quantity handled when the upper bound is reached (decimal string).
lower_limit_quantitystring: Quantity handled when the lower bound is reached (decimal string).
expire_timeinteger: Expiry time in unix seconds (use with GTD).
upper_limit_eventinteger: Action at upper bound: 1 = ignore (keep running), 2 = close at last price.
lower_limit_eventinteger: Action at lower bound: 1 = ignore (keep running), 2 = close at last price.
trigger_sell_depthinteger: Sell-side order-book depth (-5..5; 0 = use grid_order_type_up).
trigger_buy_depthinteger: Buy-side order-book depth (-5..5; 0 = use grid_order_type_down).
trigger_quantitystring: Quantity per trigger (decimal string).
support_shortsellboolean: Whether short selling is allowed.
rthinteger: Regular-trading-hours flag: 0 / 1 / 2.
grid_order_type_upstring: Sell-side order type when depth is 0: GMO / GLO / GTG.
grid_order_type_downstring: Buy-side order type when depth is 0: GMO / GLO / GTG.
executestring: The `confirmation_code` from this request's dry run. WITHOUT IT NOTHING IS SENT. Omitted (the default) makes this a DRY RUN: the request is validated and echoed back with a three-digit `confirmation_code`, and nothing reaches the exchange. Required protocol: call once without `execute`, show the returned preview to the user, and call again quoting the code only after the user has explicitly confirmed it. The code is single use, expires in 10 minutes, and applies only to this exact request — change any field and it stops working. A grid strategy keeps placing orders on its own once live, so never quote the code back on your own initiative.

grid_restart

grid_submit

Submit a grid trading order. DRY RUN unless execute is the confirmation_code from its own dry run: call once without execute, show the preview, then re-call quoting the code only after the user confirms.

參數

symbolstring必填: Security symbol, e.g. "700.HK".
settlement_currencystring必填: Settlement currency, e.g. "HKD".
submitted_base_pricestring: Base price the grid is anchored to (decimal string).
upper_limit_pricestring: Upper price bound (decimal string).
lower_limit_pricestring: Lower price bound (decimal string).
trigger_price_typeinteger: Trigger price type: 1 = spread (absolute), 2 = percent.
trigger_spread_upstring: Upward trigger spread, absolute (decimal string; use with type 1).
trigger_spread_downstring: Downward trigger spread, absolute (decimal string; use with type 1).
trigger_percent_upstring: Upward trigger percent (decimal string; use with type 2).
trigger_percent_downstring: Downward trigger percent (decimal string; use with type 2).
multiple_triggerboolean: Whether one grid level may trigger multiple times.
time_in_forceinteger: Time in force: 0 = Day, 1 = GTC, 6 = GTD.
upper_limit_quantitystring: Quantity handled when the upper bound is reached (decimal string).
lower_limit_quantitystring: Quantity handled when the lower bound is reached (decimal string).
expire_timeinteger: Expiry time in unix seconds (use with GTD).
upper_limit_eventinteger: Action at upper bound: 1 = ignore (keep running), 2 = close at last price.
lower_limit_eventinteger: Action at lower bound: 1 = ignore (keep running), 2 = close at last price.
trigger_sell_depthinteger: Sell-side order-book depth (-5..5; 0 = use grid_order_type_up).
trigger_buy_depthinteger: Buy-side order-book depth (-5..5; 0 = use grid_order_type_down).
trigger_quantitystring: Quantity per trigger (decimal string).
support_shortsellboolean: Whether short selling is allowed.
rthinteger: Regular-trading-hours flag: 0 / 1 / 2.
grid_order_type_upstring: Sell-side order type when depth is 0: GMO / GLO / GTG.
grid_order_type_downstring: Buy-side order type when depth is 0: GMO / GLO / GTG.
executestring: The `confirmation_code` from this request's dry run. WITHOUT IT NOTHING IS SENT. Omitted (the default) makes this a DRY RUN: the request is validated and echoed back with a three-digit `confirmation_code`, and nothing reaches the exchange. Required protocol: call once without `execute`, show the returned preview to the user, and call again quoting the code only after the user has explicitly confirmed it. The code is single use, expires in 10 minutes, and applies only to this exact request — change any field and it stops working. A grid strategy keeps placing orders on its own once live, so never quote the code back on your own initiative.

grid_suspend

grid_symbol_info

grid_trigger_history

history_candlesticks_by_date

history_candlesticks_by_offset

history_executions

history_market_temperature

history_orders

industry_peers

industry_rank

industry_valuation

industry_valuation_dist

institution_rating

institution_rating_detail

institution_rating_history

institution_rating_industry_rank

institutional_views

intraday

invest_relation

ipo_calendar

ipo_detail

ipo_listed

ipo_order_detail

ipo_orders

ipo_profit_loss

ipo_subscriptions

macrodata

macrodata_indicators

margin_ratio

market_status

market_temperature

news

news_detail

news_search

now

operating

option_chain_expiry_date_list

option_chain_info_by_date

option_quote

option_volume

option_volume_daily

order_detail

participants

profit_analysis

profit_analysis_detail

profit_analysis_realized

quant_run

quote

rank_categories

rank_list

replace_order

screener_indicators

screener_recommend_strategies

screener_search

screener_strategy

screener_user_strategies

security_facts

security_list

shareholder

shareholder_detail

shareholder_top

sharelist_add

sharelist_create

sharelist_delete

sharelist_detail

sharelist_list

sharelist_popular

sharelist_remove

sharelist_sort

short_margin

short_positions

short_trades

signal_detail

signals

statement_export

statement_list

static_info

stock_positions

submit_order

Submit a buy/sell order. DRY RUN unless execute is the confirmation_code from its own dry run: call once without execute, show the preview to the user, then re-call quoting the code only after they explicitly confirm.

參數

symbolstring必填: Security symbol, e.g. "700.HK"
order_typestring必填: Order type (HK supports all; US supports LO/MO/LIT/MIT/TSLPAMT/TSLPPCT only): - LO (Limit Order): requires submitted_price - ELO (Enhanced Limit Order, HK only): requires submitted_price - MO (Market Order): no price required - AO (At-auction Order, HK only): executed at auction price, no price required - ALO (At-auction Limit Order, HK only): requires submitted_price - ODD (Odd Lots Order, HK only): requires submitted_price, for non-standard lot sizes - LIT (Limit If Touched): requires submitted_price and trigger_price; activates when market price touches trigger_price - MIT (Market If Touched): requires trigger_price only; executes at market when trigger_price is touched - TSLPAMT (Trailing Limit If Touched by Amount): requires trailing_amount and limit_offset; trailing stop by fixed amount - TSLPPCT (Trailing Limit If Touched by Percent): requires trailing_percent (0-1) and limit_offset; trailing stop by percentage - SLO (Special Limit Order, HK only): requires submitted_price; cannot be replaced after submission
sidestring必填: Buy or Sell
submitted_quantitystring必填: Order quantity (number of shares)
time_in_forcestring必填: Order validity: "Day" (Day Order, expires end of session), "GTC" (Good Til Canceled), "GTD" (Good Til Date, requires expire_date)
submitted_pricestring: Limit price. Required for: LO, ELO, ALO, ODD, LIT, SLO
trigger_pricestring: Trigger (activation) price. Required for: LIT, MIT, TSLPAMT, TSLPPCT
limit_offsetstring: Limit offset from the trailing stop price. Required for: TSLPAMT, TSLPPCT
trailing_amountstring: Trailing amount (absolute price distance). Required for TSLPAMT
trailing_percentstring: Trailing percent as decimal (e.g. 0.05 = 5%). Required for TSLPPCT
expire_datestring: Expiry date (yyyy-mm-dd). Required when time_in_force is GTD
outside_rthstring: Outside regular trading hours: "RTH_ONLY" (regular trading hours only), "ANY_TIME" (any time including pre/post market), "OVERNIGHT" (overnight session, US only)
remarkstring: Order remark (max 255 characters)
executestring: The `confirmation_code` from this order's dry run. WITHOUT IT NOTHING IS SENT. Omitted (the default) makes this a DRY RUN: the request is validated and echoed back with a three-digit `confirmation_code`, and nothing reaches the exchange. Required protocol: call once without `execute`, show the returned preview to the user, and call again quoting the code only after the user has explicitly confirmed that exact order. The code is single use, expires in 10 minutes, and applies only to this exact order — change any field and it stops working. Never quote it back on your own initiative, and never in the same turn the user first asks.

today_executions

today_orders

top_movers

topic

topic_create

topic_create_reply

topic_detail

topic_replies

topic_search

trade_stats

trades

trading_days

trading_session

update_watchlist_group

valuation

valuation_comparison

valuation_history

valuation_rank

warrant_issuers

warrant_list

warrant_quote

watchlist

withdrawals

前置條件

已擁有 Longbridge 帳戶並完成開戶，或開通模擬帳戶
支援 MCP OAuth 2.1 的其他 AI 客戶端（見下方相容性說明）

客戶端接入

推薦優先從 ChatGPT 開始使用，因為 Longbridge 已經可以直接在 ChatGPT Plugins 中搜尋並授權。其他 MCP 客戶端的配置格式可能隨版本變更，請以客戶端官方文件為準。

ChatGPT

Longbridge 已經作為官方 ChatGPT App 提供。

在 ChatGPT 網頁版、桌面端或手機 App 中：

開啟 Plugins
搜尋 longbridge，或直接開啟 Longbridge ChatGPT App
選擇 Longbridge，並按提示完成授權登入

在 ChatGPT Plugins 中搜尋 Longbridge

授權 Longbridge ChatGPT App

完成授權後，每次提問時需在訊息前加上 @longbridge，否則 ChatGPT 不會調用 Longbridge 來查詢數據。例如：@longbridge 查詢我的當日訂單。

ChatGPT 中不含交易下單功能

由於 ChatGPT 平台規則限制，Longbridge ChatGPT App 不含下單及其他交易相關工具。如需使用交易功能，請改用 Claude Code、Cursor 等其他 MCP 客戶端。

Claude

Longbridge 已作為官方連接器上架 Claude 應用目錄。

在 claude.ai 網頁版或 Claude 桌面端中：

點擊 Customize → Connectors，然後點擊 Add 按鈕
在下拉選單中選擇 Browser Connectors，搜尋 longbridge
選擇 Longbridge，按提示完成授權登入

也可直接開啟 Claude - Longbridge Connector。

Claude Code

在終端執行以下命令：

claude mcp add --transport http longbridge https://mcp.longbridge.com

然後進入 claude 終端介面，輸入 /mcp，選擇 longbridge，再選擇 Authenticate 跟隨流程完成 OAuth 授權。

Codex

在終端執行以下命令：

codex mcp add longbridge --url https://mcp.longbridge.com

隨後在 Codex 中按提示完成 OAuth 授權流程。

Codex Desktop

點擊右下角 Settings → MCP Servers → Add Server
在 “Connect to a custom MCP” 介面填寫：
- Name：longbridge
- 類型：Streamable HTTP
- URL：https://mcp.longbridge.com
- 其他欄位留空
點擊 Save
回到 MCP Servers 列表，點擊 longbridge 條目上的 Authenticate 完成 OAuth 授權

Grok

開啟 Grok Connectors，新增自訂 MCP Server：

在左側邊欄選擇 Skills and Connectors → Connectors → New Connector → Custom
填寫：
- Name：Longbridge
- Server URL：https://mcp.longbridge.com
點擊 Add Connector，跟隨 Longbridge OAuth 2 授權流程完成新增

Cursor

Settings → MCP Servers → 添加 Remote MCP Server，填入上方地址即可。

Zed

在 settings.json 的 context_servers 欄位（key 名稱可自訂）中加入：

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

Cherry Studio

設定 → MCP 伺服器 → 添加，填入上方地址即可。

Manus

在 Manus 中開啟 Plugins 視窗，點擊右側的 Create 按鈕，從彈出選單中選擇 Import MCP by JSON，貼上以下 JSON 即可完成匯入：

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

OAuth 授權流程

Longbridge MCP 使用標準 OAuth 2.1 授權，你無需向客戶端提供 API 金鑰或 Token。

在 ChatGPT 中，授權會在從 Plugins 新增 Longbridge 時完成；在其他 MCP 客戶端中，通常由首次工具調用觸發瀏覽器授權流程。

AI 客戶端                  瀏覽器                    Longbridge
    |                        |                           |
    |--- 發起 MCP 連線 ------>|                           |
    |                        |-- 跳轉授權頁 ------------>|
    |                        |<- 展示登入 & 權限確認 ----|
    |                        |-- 登入並同意 ------------>|
    |<-- 返回授權憑證 --------|                           |
    |--- 攜帶憑證存取工具 ----------------------------------->|

步驟說明：

發起連線 — 在客戶端添加 Longbridge MCP 配置後，首次調用會觸發授權
瀏覽器跳轉 — 客戶端自動開啟瀏覽器，進入 Longbridge 登入與權限確認頁
登入並授權 — 使用 Longbridge 帳戶登入，查看並同意所請求的權限範圍（scope）
建立會話 — 授權完成後，客戶端取得憑證，MCP 工具即可使用
憑證維護 — 憑證依 OAuth 策略自動刷新；如需撤銷，前往 Longbridge 帳戶安全設定

客戶端相容性

Longbridge MCP 依賴 MCP OAuth 2.1 標準。若客戶端未完整實作該協議，將無法完成授權。

已知問題：Cherry Studio 早期版本不支援完整 OAuth 流程，請升級至最新版本。

如遇其他客戶端連線失敗，請確認客戶端版本並查閱其 MCP 支援文件。

客戶端無法開啟瀏覽器？

若客戶端的 OAuth 實作不完整或無法拉起瀏覽器，可改用授權碼授權：在 https://open.longbridge.com/connect 產生一次性授權碼，連接專用端點 https://mcp.longbridge.com/agent，讓 Agent 透過 authenticate 工具兌換。

安全建議

最小權限：授權時僅同意當前任務所需的 scope，避免過度授權
交易確認：涉及下單等交易操作時，在 AI 提示詞中明確要求執行前人工確認
憑證安全：OAuth 憑證由客戶端管理，避免將其複製至不受信任的環境
定期審查：定期在 Longbridge 帳戶安全設定中檢查並撤銷不再使用的授權

常見問題

OAuth 登入失敗

確認 Longbridge 帳戶狀態正常，已完成必要的身份驗證
在客戶端刪除現有配置後重新添加並發起授權
檢查當前帳戶是否支援所請求的 scope

已連線但部分工具不可用

帳戶或地區限制：特定市場或功能可能受帳戶等級或地區限制
scope 變更：如工具能力有更新，可能需要重新授權以取得新 scope

交易操作提示權限不足

檢查帳戶的交易權限和市場可交易資格
確認當前 MCP 會話的 OAuth scope 包含交易相關權限

Markdown 編輯