JTX Markets MCP Server
Enables read-only querying of JTX Markets account and market data, including balance, positions, orders, trades, funding history, and market summaries, through natural language in MCP-compatible clients.
README
@jtxmarkets/mcp-server
Model Context Protocol server for JTX Markets — query your account and market data from Claude Desktop (and other MCP-compatible clients) in plain English.
Phase 1 (this release): read-only. Positions / orders / trades / balance / funding / market data. Trade-placement tools land in Phase 2.
Quick start
1. Create a Read-scoped API key
- Sign in to staging-app.jtxmarkets.com (or the production dashboard once it's live)
- Go to
/account/api→ Additional API Keys → + Create API Key - Scope: Read — the MCP server can't submit orders. This is Phase 1.
- (Optional) Add your machine's public IP to the IP allowlist
- Copy the
api_keyandsecret— the secret is shown only once
2. Find your Client ID
Your engine client_id is on /account/overview under the "API Info" section, or you can copy it from your dashboard URL.
3. Add to Claude Desktop config
Open claude_desktop_config.json:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
Add an mcpServers.jtx-markets entry:
{
"mcpServers": {
"jtx-markets": {
"command": "npx",
"args": ["-y", "@jtxmarkets/mcp-server"],
"env": {
"JTX_MARKETS_API_KEY": "your-api-key-here",
"JTX_MARKETS_API_SECRET": "your-api-secret-here",
"JTX_MARKETS_CLIENT_ID": "11111111-1111-1111-1111-111111111111",
"JTX_MARKETS_ENV": "production"
}
}
}
}
4. Restart Claude Desktop
Open a new chat, click the tools icon, and you should see jtx-markets listed with a green dot.
Tools (Phase 1 — read-only)
| Tool | Purpose |
|---|---|
get_balance |
Balance / Available / Withdrawable / Locked / uPNL / rPNL with plain-English explanations of what each number means |
get_positions |
Open positions with entry, mark, uPNL, liquidation price |
get_orders |
Open (resting) orders — symbol, side, type, price, size, id |
get_trades |
Recent fills. Optional symbol filter + limit (default 25) |
get_funding_history |
Funding payments received or paid |
list_markets |
Every listed symbol with mark + 24h volume |
get_market_summary |
Mark / funding rate / next funding / open interest / 24h volume for one symbol |
Example prompts
- "How much can I withdraw right now?" — calls
get_balance, distinguishes Available from Withdrawable - "Show me my open ETH-PERP positions" — calls
get_positions - "Which of my open orders are furthest below the mark?" — combines
get_orders+get_market_summary - "Total funding received this month on BTC-PERP?" — calls
get_funding_historyand sums
Environment variables
| Name | Required | Default | Notes |
|---|---|---|---|
JTX_MARKETS_API_KEY |
✅ | — | Public API key from /account/api |
JTX_MARKETS_API_SECRET |
✅ | — | HMAC-SHA384 secret; shown once at key creation |
JTX_MARKETS_CLIENT_ID |
✅ | — | Engine client_id UUID |
JTX_MARKETS_ENV |
production |
production (default). staging will resolve once the staging engine host is provisioned. |
|
JTX_MARKETS_BASE_URL |
derived from JTX_MARKETS_ENV |
Override for self-host / testing |
Default is production because staging DNS has not yet been provisioned. Once a staging-engine.jtxmarkets.com host exists you can flip to staging first to test against non-live money.
Safety notes
- This is Phase 1. It cannot place, modify, or cancel orders. It cannot withdraw. It literally does not have those endpoints wired up.
- API keys are scoped. The recommended
Readscope is enforced by the engine on every request (perp-engine auth middleware). If a key is compromised, aReadkey still can't drain funds — worst case is disclosure of account state. - Withdrawals never touch MCP. They require email verification code + TOTP + admin approval on the dashboard. That flow does not translate to natural language and never will.
- Do not share a chat containing active JTX Markets tool calls — it exposes account state to whoever sees the transcript.
Development
npm install
npm test # 34 tests, all TDD-first
npm run build # emits dist/
License
MIT © JTX Markets — markets@jtxmarkets.com
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。