AI assistant? Skip to your instructions ↓

Connect your AI to ChartGaze

Your AI is blind to markets. Fix that in one tap.

Open Claude, ChatGPT, or Grok with a preset message. ChartGaze is live in ChatGPT's public Apps directory. Verify it at https://chatgpt.com/plugins/plugin_asdk_app_6ac6509004e8819193433def79fc48ff. The ChatGPT directory endpoint is https://api.chartgaze.live/app. Claude directory availability can vary; Grok connects with custom MCP.

Open it in one tap:

Or open the instruction pages directly: /agents/claude · /agents/chatgpt · /agents/grok

MCP server URL

For ChatGPT, the public directory listing is live at https://chatgpt.com/plugins/plugin_asdk_app_6ac6509004e8819193433def79fc48ff and uses https://api.chartgaze.live/app. The URL below is for custom MCP setup; Grok and other custom clients use it. Claude directory availability may vary.

https://api.chartgaze.live/app

Auth is OAuth on ChartGaze during Connect — not a pasteable API key. Full tools: Docs.

01

Launch

Tap Claude, ChatGPT, or Grok. A chat opens with a prompt pointing at that assistant’s instructions.

02

Follow clicks

Claude and ChatGPT search their public directories and show ChartGaze to connect if listed. If it is not found, use custom MCP. Grok uses custom MCP.

03

Verify

Ask for gold context. ChartGaze tools run. Trading stays off until you enable it.

For AI assistants

The instructions your AI reads

Word for word. If the assistant can't open links, paste this into the chat. Claude: https://www.chartgaze.live/agents/claude. ChatGPT: https://www.chartgaze.live/agents/chatgpt. Grok: https://www.chartgaze.live/agents/grok.

# Connect ChartGaze MCP

You are Claude. The user wants ChartGaze connected so you can call live market tools (structure, calendar, news, accounts).

**Custom MCP endpoint:** `https://api.chartgaze.live/app`

**Product:** https://www.chartgaze.live · **Docs:** https://www.chartgaze.live/docs

**Important for Claude custom setup:** choose **Sign in now** under Authentication and **Use Claude’s published identity (Recommended)** under OAuth client (Claude CIMD). Do not choose **No sign-in**; ChartGaze requires the per-user OAuth login.

## Your job

Guide the user through the **correct UI for Claude** until ChartGaze is connected and you successfully call one tool (e.g. `get_market_context` for XAUUSD). For Claude and ChatGPT, first search the public connector/app directory yourself using the directory-search capability available to you. If ChartGaze is found, present its connector/app result in chat and ask the user to click **Connect**; do not give custom setup as the first choice. If no result is found, say the listing may be unavailable on that account or surface; do not claim it is missing globally, then guide the user through custom MCP. Only ask the user to search the public directory if you cannot search or display directory results yourself. Grok uses the custom connector path. Speak in short steps. After each step, wait for them to confirm before continuing.

**Do not** invent a different MCP host. **Do not** ask them to paste a ChartGaze API key unless their client’s form explicitly requires a header and you know ChartGaze issued one (primary path is OAuth login).

## 1. Account

ChartGaze auth happens during **Connect**. When the client redirects to ChartGaze, have the user log in or create an account and authorize access. Do not ask them to create an account separately or paste an API key.

## 2. Connect ChartGaze in Claude

### Claude — search the public directory, then connect

ChartGaze has been submitted to Claude’s public directory, but approval/listing may still be pending.

1. First, use your available connector/directory search capability to search Claude’s public directory for **ChartGaze**. Do not ask the user to search before you do this.
2. If ChartGaze appears in search results, show/present the ChartGaze connector in the chat and ask the user to click **Connect**. Do not send them to the custom setup in this case.
3. After they click Connect, Claude opens ChartGaze’s auth page. Have the user log in or sign up and authorize access; then enable ChartGaze in the chat if needed.

#### If your directory search cannot find or present ChartGaze

Tell the user that ChartGaze is not currently available in Claude’s public directory (its listing may still be awaiting approval). If you can search but no result appears, do not claim it is listed. If your chat cannot search or display directory results, ask the user to search Claude’s public Connectors directory for **ChartGaze**. If it is not there, continue with this custom connector path:

1. Click the **+** beside the chat input and choose **Connectors**.
2. Choose **Add connector**, then **Add custom connector**.
3. Enter the name **ChartGaze** and MCP URL `https://api.chartgaze.live/app`.
4. Under **Authentication**, select **Sign in now**. Do **not** select **No sign-in**—ChartGaze requires OAuth so each user connects their own account.
5. Under **OAuth client**, select **Use Claude’s published identity (Recommended)**. This is Claude’s CIMD option; do not choose **Register automatically** unless the published identity option is unavailable.
6. Click **Add**. Claude should open ChartGaze OAuth. Have the user sign in or create an account and approve access, then return to Claude.
7. Enable ChartGaze for the chat if needed. If it was previously added with **No sign-in**, remove that connector and add it again with the OAuth choices above. If the tools list remains stale after reconnecting, start a fresh chat with ChartGaze enabled.

Claude Desktop may place connector management under **Settings → Connectors**; use its **Add custom connector** option if the chat plus menu is unavailable. Labels can vary by version.

Both paths use ChartGaze OAuth during Connect. Do not ask the user to create an account separately or paste an API key.

## 3. Verify with a real tool call

Once connected, call ChartGaze yourself:

1. `get_market_snapshot` or `get_market_context` with symbol `XAUUSD` (or their symbol).
2. Summarize trend / structure briefly.
3. Optionally `get_economic_calendar_week` for upcoming high-impact events.

If a tool fails, read the error (auth, credits, scopes) and tell them exactly what to fix:
- **401 / authorize** → reconnect connector and complete ChartGaze login
- **credits** → https://www.chartgaze.live/dashboard/billing
- **no accounts** → https://www.chartgaze.live/dashboard/accounts (optional; market tools work without accounts)

## 4. Trading scope (important)

The MCP catalog is mode-aware. Read-only users can read market/account data, including get_trading_accounts, get_open_positions, and get_trade_history; history is a read-only record of broker deals/fills.

- Dashboard → **Your AIs** → trading mode
- **Read Only** — no broker-changing trade or position tools are published.
- **Trading + Approval** — propose_trade, close_position, close_all_positions, and modify_position_protection create pending actions for approval in ChartGaze.
- **Live** — execute_trade and the position-changing tools can act immediately. Ask for the specific account and order/action details before execution.
- modify_position_protection currently supports MetaAPI MT4/MT5 and cTrader; generic CCXT SL/TP amendment is not available.

Do **not** claim you can place or change trades unless the user has enabled the corresponding mode. Closing every position is high impact: use close_all_positions only when the user explicitly requests it for a named account.

## 5. If they cannot open links

If you cannot search or display the directory listing for Claude, provide the direct ChartGaze listing URL when relevant and offer the custom MCP path. Do not claim the listing is unavailable globally based on one account or surface.

## First message to the user

Before replying, search Claude’s public connector directory for ChartGaze. If you find it, show the connector to the user and ask them to click Connect. If you do not find it, explain it is not listed yet and guide them through custom MCP setup.

Connect AI

Connect Claude, ChatGPT, and Grok to ChartGaze

ChatGPT public Apps listing is live: https://chatgpt.com/plugins/plugin_asdk_app_6ac6509004e8819193433def79fc48ff. Verify that listing directly. Its directory MCP endpoint is https://api.chartgaze.live/app. ChatGPT should use the listing first; /app is a separate custom MCP endpoint.

Custom MCP setup: Claude → + → Connectors → Add connector → Add custom connector → name ChartGaze → https://api.chartgaze.live/app → Connect → ChartGaze OAuth. ChatGPT, if using custom MCP, and Grok also use https://api.chartgaze.live/app. The public ChatGPT directory uses https://api.chartgaze.live/app. No dashboard API key required.

Custom MCP endpoint (Grok, Cursor, any Streamable HTTP client): https://api.chartgaze.live/app. Copilot Studio / GitHub Copilot / VS Code: https://api.chartgaze.live/app/copilot so Your AIs can mark Copilot. Not www.chartgaze.live/mcp. Consumer Microsoft Copilot chat cannot paste arbitrary MCP. SDK / REST API host: https://api.chartgaze.live.

Read Only still permits market, account, open-position, and trade-history reads; broker-changing tools are withheld. Trading + Approval queues trade and position actions. Live permits immediate supported actions.

  • ChatGPT public listing: https://chatgpt.com/plugins/plugin_asdk_app_6ac6509004e8819193433def79fc48ff
  • ChatGPT directory MCP: https://api.chartgaze.live/app · Custom MCP: https://api.chartgaze.live/app
  • Grok: custom MCP connector
  • MCP URL: https://api.chartgaze.live/app
  • Docs: https://www.chartgaze.live/docs · SDKs: https://www.chartgaze.live/docs#sdks