MCP Server REST API & WebSocket Real-time Push Interface Financial Data API Documentation SDK & Developer Tools Official iTick MCP Server providing REST API queries and WebSocket real-time data subscriptions for basics, stocks, indices, futures, funds, forex, and cryptocurrencies.

Introduction to MCP Server

The official iTick MCP Server is a standardized protocol server launched by the iTick financial data platform, built on the Model Context Protocol (MCP). It provides a unified entry point for AI assistants (such as Claude Desktop, Cursor, etc.) to access financial data. This server encapsulates iTick's high-quality data capabilities in global forex, stocks, indices, futures, funds, and cryptocurrencies. It supports REST API batch queries and WebSocket real-time push notifications. Developers only need to configure an API Key to instantly call professional financial data within AI dialogue environments, significantly lowering the barrier to data integration.

Features

Developer-Friendly: Standardized and easy-to-use interfaces, concise documentation, and rich examples for quick integration.
Comprehensive Product Coverage: Real-time and historical data for multi-market stocks, forex, indices, cryptocurrencies, and more.
Versatile Scenarios: Suitable for quantitative teams, fintech applications, and professional analysis.
Robust Infrastructure & Service: Professional data sources, multi-region acceleration, and link hot backups, focusing on real-time performance and stability.
Customization: Institutional and professional users can negotiate customized data solutions.

iTick API Types and Project Scope

Type	Description	This MCP
REST	Retrieve quotes, K-lines, etc., via market data endpoints; requests must include authentication information such as tokens as per documentation.	Implemented (Only REST capabilities covered by HTTP GET)
Websocket	Publish/subscribe model pushing orders, trades, market data, etc., to reduce polling.	Not Implemented
FIX	High-throughput, institutional-grade connections; currently primarily for institutional clients.	Not Implemented (Non-REST)

For FIX access (institutional only), please contact official support: Telegram @iticksupport, WhatsApp +852 59046663.

Technical Support (Summary)

Email: support@itick.org (Please include environment, identity, and problem description in the subject line)
Business Hours: Monday to Friday, 9:00–18:00 (Hong Kong Time); emergency production issues are subject to official announcements.
Non-Business Hours: Log in to itick.org to contact online customer service via instant messaging.

Deployment

uv build + upx (Recommended Method)

Build using uv and compress with upx to generate a lightweight, distributable MCP stdio executable.

# Install uv (if not already installed)
curl -LsSf https://astral.sh/uv/install.sh | sh

# Install upx (if not already installed)
# macOS: brew install upx
# Linux: sudo apt install upx

# Build + Compress
uv build

The build artifact is located in the dist/ directory and can be directly used for MCP stdio mode (Cursor / Claude Desktop / OpenCode):

Quick Configuration

Supported platforms:

✨ Cursor
✨ Claude Desktop
✨ OpenCode

Manual Configuration of Environment Variables

Variable	Description
`TOKEN`	Required (at runtime): Request header `token`, see REST documentation
`ITICK_API_BASE`	Optional, default `https://api.itick.org` (consistent with documentation examples). If your environment uses `https://api.itick.io`, set it to this address

export TOKEN="your_token"
# export ITICK_API_BASE="https://api.itick.io"

Run (stdio)

itick-mcp
# or
# Start via HTTP transport
python3 -m itick_mcp_server  --transport http
# Start via SSE transport
python3 -m itick_mcp_server  --transport sse
# Start via STDIO transport
python3 -m itick_mcp_server

Cursor / Claude Desktop

{
  "mcpServers": {
    "itick": {
      "command": "uvx",
      "args": [
        "itick-mcp"
      ],
      "env": {
        "TOKEN": "your_token"
      }
    }
  }
}

OpenCode

OpenCode uses the mcp key in opencode.json / opencode.jsonc. For local services, set type to local, command to a string array, and environment variables in environment (different from Cursor's mcpServers / env). Minimal example:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "itick": {
      "type": "local",
      "enabled": true,
      "command": ["uvx", "itick-mcp"],
      "environment": {
        "TOKEN": "your_token"
      }
    }
  }
}

MCP Tool Overview

Corresponds to paths in the REST documentation:

Basic

symbolList → GET /symbol/list
symbolHolidays → GET /symbol/v2/holidays

Stocks (Additional)

stockInfo → GET /stock/info
stockIpo → GET /stock/ipo
stockSplit → GET /stock/split

Product Lines (stock / crypto / forex / indices / future / fund)

Tool Name	REST
`{prefix}Tick`	`GET /{prefix}/tick`
`{prefix}Quote`	`GET /{prefix}/quote`
`{prefix}Depth`	`GET /{prefix}/depth`
`{prefix}Kline`	`GET /{prefix}/kline`
`{prefix}Ticks`	`GET /{prefix}/ticks`
`{prefix}Quotes`	`GET /{prefix}/quotes`
`{prefix}Depths`	`GET /{prefix}/depths`
`{prefix}Klines`	`GET /{prefix}/klines`

In batch interfaces, codes is a comma-separated list. K-line parameters in tools are k_type, encoded as kType in requests; optional et (timestamp in milliseconds), limit.

The tool name for single stock K-line remains stockKline as in the early Java example.

Code Structure

client.py — HTTP GET, ITICK_API_BASE / TOKEN
tools_register.py — Register all REST tools
server.py — FastMCP entry point