JTX Markets MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@JTX Markets MCP Servershow me my open positions"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@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 KeyScope: 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.jsonWindows:
%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.
Related MCP server: polygon-mcp
Tools (Phase 1 — read-only)
Tool | Purpose |
| Balance / Available / Withdrawable / Locked / uPNL / rPNL with plain-English explanations of what each number means |
| Open positions with entry, mark, uPNL, liquidation price |
| Open (resting) orders — symbol, side, type, price, size, id |
| Recent fills. Optional |
| Funding payments received or paid |
| Every listed symbol with mark + 24h volume |
| 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 |
| ✅ | — | Public API key from |
| ✅ | — | HMAC-SHA384 secret; shown once at key creation |
| ✅ | — | Engine client_id UUID |
|
|
| |
| derived from | 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
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/jtxmarketsofficial/jtx-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server