Xtquantai MCP Server

面向迅投 QMT / 投研终端的 Agent Skills 仓库：把量化策略开发的领域知识（因子回测、信号生成、实盘模板等）封装为标准 SKILL.md 技能，安装后可在 Claude Code、Cursor、Codex、Gemini CLI、Kimi Code 等 70+ AI 编程工具中直接使用。. Exposed over MCP by the xtquantai mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

Its toolset

Everything the assistant can do here goes through one of these:

• qmt-future-trade — 🚧 规划中
• qmt-live-strategy-template — 🚧 规划中
• qmt-live-signal-feishu — 🚧 规划中
• Windsurf — .windsurf/skills/ 或 .agents/skills/
• OpenCode — .opencode/skills/、.claude/skills/、.agents/skills/

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at skills on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Xtquantai's toolset — qmt-future-trade, qmt-live-strategy-template, qmt-live-signal-feishu and 2 more — is a fair guide to whether it matches your workflow. It is maintained by dfkai; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Xtquantai's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the xtquantai mcp server does with a few real requests.