MCP integration

Connect AI tools to gold market data · Proposed integration

Draft reference · Examples use sample data.

MCP for gold market data

Model Context Protocol (MCP) would let an AI application discover and call xauapi’s read-only market-data tools. The proposed integration covers quotes, candles and feed status for JustMarkets XAUUSD.

Planned integration

No MCP server is deployed. The URL, tools and authentication below describe a proposed contract. Demo keys cannot connect, and no AI client has been verified.

One-click setup prompts

Set up with your AI

Copy a complete prompt, then paste it into a new chat.

Includes setup context, proposed tools and safe credential handling. Copying does not connect a server or include your API key.

View full prompt

Setup prompt · ChatGPT

Help me prepare a read-only xauapi MCP integration. Guide me step by step, keep explanations practical, and distinguish preparation from a verified connection.

MY CLIENT
I am using ChatGPT. First establish whether my current ChatGPT account and workspace support adding a remote MCP connection, and whether an administrator must enable it. Do not assume a specific plan, settings menu or authentication method is available.

CURRENT PRODUCT STATUS
There is currently NO deployed xauapi MCP server, live API connection or verified AI-client integration. The xauapi.com/dashboard/mcp URL is a dashboard page, not an MCP endpoint. Demo keys beginning with eq_demo_ are nonfunctional. Do not attempt to connect to the workspace site, resolve placeholder hosts, install a guessed package, or claim that pasting this prompt connects anything. For now, help me understand the setup and prepare a checklist.

PROPOSED CONNECTION
Transport: remote Streamable HTTP.
Endpoint placeholder: https://MCP_BASE_URL/mcp
Authentication concept: Authorization: Bearer YOUR_API_KEY
These are proposed fields, not a ready-to-use client configuration. The published endpoint and final client authentication requirements must be confirmed before connection. Never ask me to paste a real API key into this chat. Tell me where to enter credentials securely in my client when supported. Use placeholders in all examples, logs and commands.

PROPOSED READ-ONLY TOOLS
- get_feed_status({"feed":"justmarkets"}): connection and stale-data indicators.
- get_quote({"feed":"justmarkets"}): XAUUSD Bid, Ask, spread, source timestamp and freshness.
- get_candles({"feed":"justmarkets","interval":"M5"}): broker OHLC candles; proposed intervals are M1, M5 and M15.
JustMarkets gold (XAUUSD) is the only proposed sample feed. Do not invent additional tools, brokers, date-range parameters or pagination. No trading, order placement, account changes or billing actions are allowed.

DATA AND LIMITS
Quotes and candles are sampled broker data, not a complete record of every tick. Prices use USD; candle examples use Bid prices. Always show the source timestamp and freshness indicators. Never label fixed example data as live. Pro is $149/month equivalent, billed $1,788 annually, with 12 million annual requests and 250 requests/minute. Max is $1,490/month equivalent, billed $17,880 annually, with 240 million annual requests and 300 requests/minute. MCP accounting and client compatibility are not finalized. Do not start background polling or automatic retries.

WHAT I WANT FROM YOU
1. Briefly explain what can be prepared now and what must wait for a deployed MCP service.
2. Ask only the client/account questions needed to identify the supported setup path. Check current official client documentation when available; otherwise explicitly mark your instructions unverified.
3. Give a concise checklist and, only if appropriate for my client, a configuration template containing placeholders. Do not reuse a generic profile as if it were a verified client config.
4. Once I confirm a real service is available, guide me through secure connection setup and tool discovery. Treat the server's discovered tool definitions as authoritative.
5. After an actual connection, check feed status first. If data is fresh and access permits, make one quote request and show Bid, Ask, spread and timestamp. If stale or disconnected, explain that condition without fabricating current prices.
6. Explain credential, rate-limit, quota and stale-feed errors clearly. Report a successful connection only after an actual tool call succeeds.

START HERE
Confirm that you understand there is no live server available, then help me prepare for my client. Do not execute anything yet.

Connection setup

Use an MCP client that supports remote Streamable HTTP servers and the required authentication.
When available, add the published MCP endpoint and configure your API key through the client’s secure credential settings.
Discover the available tools and start with get_feed_status before requesting prices.

The profile below is illustrative, not a universal client configuration file. Map these fields to your client’s settings. Replace the placeholders only when the service is available; never paste real keys into a chat.

Proposed connection profile · not executable

{
  "name": "xauapi",
  "transport": "streamable-http",
  "url": "https://MCP_BASE_URL/mcp",
  "headers": {
    "Authorization": "Bearer YOUR_API_KEY"
  }
}

Proposed tools

Tool	Arguments	Returns
`get_quote`	feed: justmarkets	Bid, Ask, spread, source timestamp and freshness.
`get_candles`	feed: justmarkets; interval: M1 \| M5 \| M15	Broker OHLC candles, with timestamps and Bid price basis.
`get_feed_status`	feed: justmarkets	Connection and stale-data indicators.

All three tools are read-only. No order placement, account changes or billing actions are exposed. Additional brokers, historical range filters and candle pagination are not specified.

Example tool call

Illustrative tools/call parameters

{
  "name": "get_quote",
  "arguments": {
    "feed": "justmarkets"
  }
}

Sample tool data · fixed values

{
  "demo": true,
  "feed": "justmarkets",
  "symbol": "XAUUSD",
  "timestamp": "2026-10-06T08:30:00Z",
  "sampled": true,
  "bid": 2650.4,
  "ask": 2650.6,
  "spread": 0.2,
  "stale": false
}

This is the proposed data payload, not a complete MCP protocol exchange. A client handles protocol negotiation and the tool-result envelope.

Example prompts

“Check the JustMarkets gold feed status and report whether the data is stale.”
“Show the latest XAUUSD Bid, Ask and spread, including the source timestamp.”
“Summarize the available M5 gold candles and identify any gaps.”

These prompts do not run on this site. An assistant should state the source and timestamp, preserve stale-data warnings and explain that sampled data can miss intermediate ticks.

Access, limits & errors

The proposed design reuses the API key’s read-only access. Successful market-data tool calls are intended to share your plan’s allowance: Pro includes 12 million annual requests and 250 requests/minute; Max includes 240 million annual requests and 300 requests/minute. Protocol discovery accounting and client authentication compatibility are not finalized.

Invalid credentials, quota limits and stale feeds must produce actionable errors rather than fabricated prices. No background polling or automatic connection is enabled here.

Open MCP in your workspace →

Protocol references: Streamable HTTP · MCP tools. These describe MCP; they do not establish xauapi support.