ZakuraFX API & MCP connector

Overview

One endpoint, 10 tools. Your AI tool calls them in the middle of a conversation to read prices, candles, the calendar and the desk's own record. Nothing here places a trade or changes an account.

Authentication

Every request carries your key in the Authorization header:

Authorization: Bearer YOUR_KEY

• The key is shown once, when you create it. Only a hash of it is stored, so a lost key cannot be shown again: delete it and create a new one.
• The key works on every plan. What it can call follows your plan at the moment of each request: upgrade and the same key opens more, with no new key needed.
• Changing your password switches off keys made before the change. The owner can revoke access at any time.
• HTTPS only. Always use the https:// address: a plain http:// request is redirected, but a key sent that way has already crossed the network unencrypted, so replace it.
• Send the key only in the Authorization header, never in a URL.

Connect

Endpoint (HTTPS, POST only): https://zakurafx.com/api/mcp

The word http in the commands below is the name of the MCP transport, not the address: the connection is always encrypted HTTPS.

Claude Code

claude mcp add --transport http zakurafx https://zakurafx.com/api/mcp \
  --header "Authorization: Bearer YOUR_KEY"

Cursor and other MCP clients that take a URL and headers

{
  "mcpServers": {
    "zakurafx": {
      "type": "http",
      "url": "https://zakurafx.com/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_KEY" }
    }
  }
}

Claude Desktop

Claude Desktop's config file (claude_desktop_config.json) starts local programs only, so connect through the mcp-remote bridge. It needs Node.js installed.

{
  "mcpServers": {
    "zakurafx": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://zakurafx.com/api/mcp", "--header", "Authorization:${AUTH_HEADER}"],
      "env": { "AUTH_HEADER": "Bearer YOUR_KEY" }
    }
  }
}

Connecting from the claude.ai website (sign in instead of a key) is not available yet. Use Claude Code, Claude Desktop or Cursor with a key.

Raw requests

List the tools (a tool your plan does not open says which plan does):

curl -X POST https://zakurafx.com/api/mcp \
  -H "Authorization: Bearer YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Call a tool:

curl -X POST https://zakurafx.com/api/mcp \
  -H "Authorization: Bearer YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"get_candles","arguments":{"symbol":"XAUUSD","interval":"1h","limit":3}}}'

Each tool answers with the data twice: as JSON text in content for any client, and as an object in structuredContent:

{
  "jsonrpc": "2.0",
  "id": 2,
  "result": {
    "content": [{ "type": "text", "text": "{\"symbol\":\"XAUUSD\",\"interval\":\"1h\",\"bars\":[…]}" }],
    "structuredContent": {
      "symbol": "XAUUSD", "interval": "1h", "live": true, "fetchedAt": "…",
      "bars": [{ "t": "…", "o": …, "h": …, "l": …, "c": … }, …]
    }
  }
}

Tools reference

Every tool is read-only: it reads data and never trades, writes or pays. A tool marked Pro+ answers a Free key with a short note saying which plan opens it.

Plans & limits

Bar caps are ceilings: the source holds fewer on slower timeframes (about 400 on 1h and above), so a large limit returns what there is. Every request counts toward the hourly limit, including the few your AI tool sends when it connects. Past the limit the server answers 429 with a Retry-After header. All keys together also share one site-wide limit of 600 requests an hour. Each plan has 100 of them reserved, so one plan's keys cannot use up the hour for the others; once a plan's reserve and the shared remainder are used, its keys get 429 until the hour resets.

See plans and prices

Errors

Rules

• Read-only. The API never places trades, changes your account or takes payment.
• Signals are the desk's read, not advice. Confidence is the desk's score, never a probability.
• One key per member. Do not share it or resell the data. The owner can revoke access at any time.

Get a key

1. Sign in and fill in the form below: what it is for, what you will build, and how you will connect.
2. The owner reviews and approves the request. Then come back here and create your key.
3. Add the connector to your AI tool with the key (see Connect above).

Risk disclaimer

Trading foreign exchange and CFDs on margin carries a high level of risk and may not be suitable for all investors. Past performance of any signal or analysis is not indicative of future results. You could lose some or all of your initial investment.