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. Claude and ChatGPT can search their public directories for ChartGaze and present the connector for you to connect. If it is not listed yet, they’ll explain that and guide you through custom MCP. 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

Claude and ChatGPT can search their public directories and show ChartGaze for you to connect if it is listed. If not, use this URL to add a custom connector. Directory approval may still be pending. Grok uses a custom connector.

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).

**MCP server URL (custom connector):** `https://api.chartgaze.live/app`

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

## 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 ChartGaze is not currently listed (approval may still be pending) and 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. Click **Connect**. Claude redirects to ChartGaze; have the user log in or create an account and authorize access.
5. After returning to Claude, select/enable ChartGaze for the chat if needed.

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)

By default ChartGaze is **read-only** (market + view accounts). Trading / order placement is off until the user enables it in ChartGaze:

- Dashboard → **Your AIs** → trading mode
- Prefer **Require approval** so proposed trades wait in Activity until they click Approve

Do **not** claim you can place live trades unless they confirm trading is enabled.

## 5. If they cannot open links

If you cannot search or display the directory listing for Claude, tell the user to search its public directory for ChartGaze. If they find it, have them click **Connect**; if they do not, explain it is not listed yet and provide the custom MCP path. Never claim a listing exists unless the directory search returns ChartGaze.

## 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

Tap Open in Claude, ChatGPT, or Grok on /agents. Claude and ChatGPT should search their public connector/app directory for ChartGaze themselves. If they find it, they should present it in chat for the user to click Connect. If they cannot find or present it, they should explain it is not listed yet (approval may be pending); only ask the user to search if the AI cannot search or show results.

If ChartGaze is not found: Claude → + → Connectors → Add connector → Add custom connector → name ChartGaze → https://api.chartgaze.live/app → Connect → ChartGaze OAuth. ChatGPT → Apps/Plugins → Add → Create custom MCP → name ChartGaze → same URL → Connect → ChartGaze OAuth. Grok: grok.com → + → Connector → Custom → name ChartGaze + same URL → Connect → ChartGaze OAuth. No dashboard API key required.

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

Trading stays read-only until you enable approval or live mode under Dashboard → Your AIs.

  • Claude and ChatGPT: directory if listed, custom connector if not
  • Grok: custom MCP connector
  • MCP URL: https://api.chartgaze.live/app
  • Docs: https://www.chartgaze.live/docs · SDKs: https://www.chartgaze.live/docs#sdks