# How to connect Longbridge to Hermes Agent (no API keys) > Connect Longbridge to Hermes with ClawLink in one click — 147 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/hermes/longbridge Most guides for giving Hermes Agent Longbridge access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Longbridge setup: pair once in the browser and your always-on Hermes agent can act on Longbridge for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect Hermes to Longbridge. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Longbridge** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **Paste this into Hermes to set up ClawLink:** > Set up ClawLink for Hermes and tell me when it's ready. > 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable` > 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait. > 3. I'll approve it in my browser, then reply "approved". > 4. When I say approved, finish setup: `hermes clawlink finish` > 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready. **Alternative for any agent (no plugin needed):** if the Hermes Agent plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect longbridge # connect Longbridge (browser OAuth) npx -y @useclawlink/cli actions longbridge # list available actions npx -y @useclawlink/cli run longbridge --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above walks Hermes through this. By hand, it is four commands and a browser approval: ```bash hermes plugins install ClawLink-HQ/hermes-plugin --enable hermes clawlink begin # prints an approval link — open it and approve hermes clawlink finish # after approving in the browser hermes clawlink test ``` Then connect Longbridge in the [ClawLink dashboard](https://claw-link.dev/dashboard) — a one-click OAuth approval, no API keys. Verify the connection by asking Hermes: > Use Longbridge to mcp account balance and walk me through the result in plain English. ### Using a different agent? The Hermes plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Longbridge is connected in the dashboard, that agent calls the same 147 Longbridge tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Longbridge MCP for Hermes Looking for a Longbridge MCP server for Hermes Agent? ClawLink connects Longbridge to Hermes Agent and exposes 147 Longbridge tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using OpenClaw instead? The [OpenClaw Longbridge integration](https://claw-link.dev/openclaw/longbridge) works the same way. ## What the Hermes Agent Longbridge integration can do 147 Longbridge tools are ready for Hermes Agent once the account is connected. The 30 below are the ones people reach for most; your agent can call all 147. ### 30 of 147 Longbridge tools for Hermes | Tool | What it does | |---|---| | **Mcp account balance** `longbridge_mcp_account_balance` | Get account cash balance and asset summary | | **Mcp ah premium** `longbridge_mcp_ah_premium` | Get A/H share premium historical K-line data | | **Mcp ah premium intraday** `longbridge_mcp_ah_premium_intraday` | Get A/H share premium intraday time-share data | | **Mcp alert list** `longbridge_mcp_alert_list` | Get all configured price alerts | | **Mcp anomaly** `longbridge_mcp_anomaly` | Get market anomaly alerts (unusual price/volume changes) | | **Mcp bank cards** `longbridge_mcp_bank_cards` | List linked withdrawal bank cards for the current account | | **Mcp broker holding** `longbridge_mcp_broker_holding` | Get top broker holding data for a symbol (HK stocks only; sourced from HKEX CCASS participant | | **Mcp broker holding daily** `longbridge_mcp_broker_holding_daily` | Get daily holding history for a specific broker (by broker_id) in a symbol (HK stocks only | | **Mcp broker holding detail** `longbridge_mcp_broker_holding_detail` | Get full broker holding detail list for a symbol (HK stocks only; sourced from HKEX CCASS | | **Mcp brokers** `longbridge_mcp_brokers` | Get broker queue (HK stocks only) | | **Mcp business segments** `longbridge_mcp_business_segments` | Get current-period business segment revenue breakdown for a symbol (name, percent, total | | **Mcp business segments history** `longbridge_mcp_business_segments_history` | Get historical business segment revenue trends (by period and category) | | **Mcp calc indexes** `longbridge_mcp_calc_indexes` | Calculate financial indexes for symbols | | **Mcp candlesticks** `longbridge_mcp_candlesticks` | Get candlestick data (OHLCV) | | **Mcp capital distribution** `longbridge_mcp_capital_distribution` | Get capital distribution for a symbol | | **Mcp capital flow** `longbridge_mcp_capital_flow` | Get capital inflow/outflow time series | | **Mcp cash flow** `longbridge_mcp_cash_flow` | Get cash flow records (deposits, withdrawals, dividends) | | **Mcp company** `longbridge_mcp_company` | Get company overview | | **Mcp consensus** `longbridge_mcp_consensus` | Get financial consensus estimates for upcoming periods | | **Mcp constituent** `longbridge_mcp_constituent` | Get the constituents of an index or the asset allocation of an ETF | | **Mcp corp action** `longbridge_mcp_corp_action` | Get corporate actions (splits, buybacks, name changes) | | **Mcp dca check** `longbridge_mcp_dca_check` | Check whether given symbols support DCA recurring investment | | **Mcp dca history** `longbridge_mcp_dca_history` | Get execution history records for a DCA plan by plan_id | | **Mcp dca list** `longbridge_mcp_dca_list` | List DCA recurring investment plans | | **Mcp dca stats** `longbridge_mcp_dca_stats` | Get DCA investment statistics | | **Mcp deposits** `longbridge_mcp_deposits` | List deposit history for the current account | | **Mcp depth** `longbridge_mcp_depth` | Get order book depth for a symbol | | **Mcp dividend** `longbridge_mcp_dividend` | Get dividend history for the symbol | | **Mcp dividend detail** `longbridge_mcp_dividend_detail` | Get detailed dividend distribution scheme | | **Mcp estimate max purchase quantity** `longbridge_mcp_estimate_max_purchase_quantity` | Estimate maximum buy/sell quantity for a symbol | ## Example prompts **Mcp Account Balance** > Use Longbridge to mcp account balance and walk me through the result in plain English. **Mcp Ah Premium** > Use Longbridge to mcp ah premium and walk me through the result in plain English. **Mcp Ah Premium Intraday** > Use Longbridge to mcp ah premium intraday and walk me through the result in plain English. **Mcp Alert List** > Use Longbridge to mcp alert list and walk me through the result in plain English. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Longbridge working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Longbridge app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Longbridge through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Longbridge. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Longbridge actions to the runtime in a format your agent can reliably use. | 147 tools for Longbridge are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Longbridge to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Hermes Agent users instead. You install the plugin once, connect Longbridge in the browser, and the 147 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### Hermes paired but still can't use Longbridge Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ### Connection succeeds but no tools appear Reconnect Longbridge from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Longbridge tools Longbridge tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Longbridge call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Longbridge returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### OAuth finished in the browser but the account is still missing Try reconnecting Longbridge and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete. ### Is there a Hermes Agent Longbridge integration? Yes. ClawLink is the fastest way to connect Hermes to Longbridge: link your Longbridge account once in the browser and Hermes Agent can call the Longbridge API through 147 ready-made tools — no custom code or token handling. ### How do I connect Longbridge to Hermes with ClawLink? Install the plugin with `hermes plugins install ClawLink-HQ/hermes-plugin --enable`, then pair once: run `hermes clawlink begin`, approve the link in your browser, and run `hermes clawlink finish`. Connect Longbridge in the dashboard and Hermes can use it from the next message — no config files or API keys to manage. ### How long does it take to connect Longbridge to Hermes Agent? About two minutes. Sign in, click Connect next to Longbridge in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Longbridge up myself? The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Longbridge working from chat. ### Hermes paired but still can't use Longbridge Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ## Related - [Hermes PostHog integration](https://claw-link.dev/hermes/posthog) — Track user behavior and feature flags - [Connect DataforSEO](https://claw-link.dev/hermes/dataforseo) — SEO data APIs for keywords, SERP, and site audits - [Connect Metabase](https://claw-link.dev/hermes/metabase) — Metabase is an open-source business intelligence tool that lets you ask questions about your data and visualize answers as charts, graphs, and dashboards.