Real-Time Stock Market Data for OpenCode如何为 OpenCode 接入实时股票市场数据

OpenCode can reason, remember context, schedule work, and invoke tools, but a language model's training data is not a live market feed. A market-data connection closes that freshness gap for research summaries, watchlist checks, volatility alerts, dashboard prototyping, and data-quality investigations.

The key boundary is equally important: this use case provides evidence for analysis; it does not authorize trading. Quotes can be delayed, venue-specific, consolidated, adjusted, or contractually restricted. Treat “real time” as a documented property of a feed and subscription, not a label inferred from a recent-looking number.

Why not send a WebSocket directly into the model?

A continuous feed is application state, not conversational context. Let a stream consumer handle reconnects, ordering, deduplication, backpressure, and cache updates. OpenCode should request a bounded snapshot or aggregate through a tool. This controls token use and makes calls reproducible.

1. Define freshness before choosing a provider

Specify asset class, exchanges, trade or quote data, maximum acceptable age, extended-hours behavior, history depth, and whether results will be displayed or redistributed. Then compare provider documentation and entitlements. A developer plan may expose a different feed from a paid production plan.

2. Build a provider-neutral adapter

Map vendor fields into one typed contract. Normalize symbol conventions, timestamps, currency, session status, corporate-action adjustments, and typed errors. Keep provider-specific fields under an optional metadata object.

3. Expose narrow read tools

Start with operations such as get_quote, get_bars, and get_market_status. Put limits on symbols, date ranges, granularity, and response size. Do not expose arbitrary URLs, arbitrary SQL, or provider administration.

4. Register the MCP server in OpenCode

OpenCode supports local MCP servers over stdio and remote servers over Streamable HTTP. In OpenCode V2, define a unique server name under mcp.servers. Keep the market-data key in an environment variable, not in the prompt or repository. For a remote server that uses an API key, set oauth to false and pass a scoped header. See the official OpenCode MCP server documentation for the current schema.

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "servers": {
      "market-data": {
        "type": "local",
        "command": ["node", "./tools/market-data-mcp.mjs"],
        "environment": {
          "MARKET_DATA_API_KEY": "{env:MARKET_DATA_API_KEY}"
        },
        "codemode": true,
        "timeout": 10000
      }
    }
  }
}

OpenCode connects configured servers automatically unless disabled is true. Keep codemode enabled unless you intentionally want every tool exposed directly, and use OpenCode permissions to deny operations outside the read-only surface. Confirm the connection with opencode2 mcp list.

5. Prompt for evidence, not confidence

Require OpenCode to state symbol, value type, event time, receipt time, provider/feed, session, currency, and delay classification. If data is stale or the market is closed, the answer should say so before interpreting the move.

6. Test degraded states

Use recorded fixtures for deterministic tests, then run an opt-in live smoke test. Exercise rate limiting, provider timeouts, malformed payloads, symbol not found, closed sessions, stale cache, partial batches, and reconnect recovery.