ChartGaze Documentation

Overview

ChartGaze is a remote MCP server. Your AI (Claude, ChatGPT, Grok, custom agents) calls tools over HTTPS — it never needs raw OHLCV dumps or screenshot uploads. For full autonomous execution, use TrainFlow; ChartGaze is the context + account layer.

Connect your AI

Claude (directory)

1. Chat + → Connectors → + → Browse connectors
2. Search ChartGaze → Connect
3. Log in / sign up on ChartGaze when Claude opens that page
4. Tap ChartGaze in connectors for the chat, then ask e.g. gold bias vs next USD event

Custom URL fallback only if Browse has no ChartGaze: https://api.chartgaze.live/app

ChatGPT

Directory / Plugins Connect when listed (OAuth). Until then: Developer mode → custom MCP → same URL → ChartGaze login.

Grok (custom)

1. On grok.com (web), click + in the chat box → Connector → Custom
2. Name it ChartGaze and paste https://api.chartgaze.live/app (not www.chartgaze.live/mcp)
3. Complete ChartGaze OAuth when Grok redirects you

Microsoft Copilot

Consumer Copilot chat (copilot.microsoft.com / Bing chat) has no user setting to paste arbitrary MCP servers or install ChartGaze as a plugin. That matches Microsoft’s own guidance.

• Copilot Studio — build a custom agent and attach ChartGaze as an MCP / external tool (https://api.chartgaze.live/app); prefer OAuth.
• Microsoft 365 Copilot (work/school) — admins configure connectors / agents via Microsoft 365 admin tools; gallery / partner certification is a separate Microsoft path (often read-focused).
• GitHub Copilot / VS Code — developer MCP clients can use the same remote URL as other custom agents.

Claude Desktop / other MCP clients

Remote Streamable HTTP / SSE — no stdio wrapper required.

{
  "mcpServers": {
    "chartgaze": {
      "url": "https://api.chartgaze.live/app"
    }
  }
}

Custom agents / Cursor / other MCP clients: use https://api.chartgaze.live/app. SDKs use API host https://api.chartgaze.live with Bearer auth — see SDKs.

MCP tools (12)

Discoverable at runtime via tools/list or GET /mcp/tools. Call with POST /mcp/call.

# Example: multi-TF gold context
POST https://api.chartgaze.live/mcp/call
{
  "name": "get_market_context",
  "arguments": {
    "symbol": "XAUUSD",
    "include_events": true
  }
}

Auth & billing

Sign in at chartgaze.live (email/password, Google, or password reset via /auth/reset-password). MCP sessions use ChartGaze OAuth / bearer. Free tier: 10 MCP calls · no card (flat 1 call per tool on free). Top up call packs on Billing ($10 / 100, $100 / 1200).

Market data (general CAR + complements)

Analysis tools do not pull OHLCV from the user’s broker by default. They resolve each symbol against ChartGaze coverage:

• General CAR — shared warm feed (cTrader sidecar symbol map / optional general MetaAPI or CCXT). Covers majors, metals, many crypto & synthetics already.
• Complements — when someone connects an account whose server is not already covered, only symbols missing from general are mapped onto that account and kept warm. Same server → skip.
• Tool responses include market_data_source so the AI knows which feed served the candles.
• Balances, positions, propose/approve trades always use the user’s account_id from get_trading_accounts.

HTTP API

Base: https://api.chartgaze.live

SDKs

Official SDKs live under github.com/TrainFlow-AI. Use them for bots and backends; use MCP for conversational agents.

Python quick start

# pip install chartgaze
import os
from chartgaze import ChartGaze

client = ChartGaze(api_key=os.environ["CHARTGAZE_API_KEY"])
ctx = client.get_market_context(symbol="XAUUSD", include_events=True)
print(ctx)

Go quick start

// go get github.com/TrainFlow-AI/chartgaze-go-sdk
client := chartgaze.NewClient(os.Getenv("CHARTGAZE_API_KEY"))
ctx, err := client.GetMarketContext(ctx, "XAUUSD", true)
if err != nil { log.Fatal(err) }
fmt.Println(ctx)

Java quick start

// mvn install (from chartgaze-java-sdk)
ChartGazeClient client = new ChartGazeClient(System.getenv("CHARTGAZE_API_KEY"));
JsonNode ctx = client.getMarketContext("XAUUSD", true);
System.out.println(ctx);

Connect trading accounts

Dashboard → Accounts shows your slot usage (X / Y in use). Broker login for MT4/MT5 (MetaAPI), Spotware OAuth for cTrader, API keys for Binance, Bybit, OKX, Bitget, MEXC, Gate, Kraken, KuCoin, Crypto.com. Market tools work without a connect; slots are only for your book + trading/approve.

If you have no slots, Connect opens pricing ($15 or $50). Your AI never receives credentials — only balances/positions you authorize via get_trading_accounts. Idle MetaAPI accounts that are not serving market complements undeploy after ~6h; trading redeploys before execute.