Gmx Mcp
Give your agent broad GMX perpetuals, options, and position data while you build trading analytics, alerts, or research copilots.
Overview
io.github.junct-bot/gmx-mcp is a MCP server for the Build phase that offers 139 tools for GMX perpetuals, options, and position data to your coding agent.
What is this MCP server?
- 139 MCP tools for GMX perpetuals, options, and position-related data
- Streamable HTTP remote at gmx.mcp.junct.dev
- Version 1.1.0 from junct-bot/gmx-mcp on GitHub
- Wide tool count suited to deep agent research on derivatives exposure
- Read-oriented protocol MCP—verify behavior before any automated trading logic
- 139 MCP tools for perpetuals, options, and position data
- Server version 1.1.0
- Remote URL: https://gmx.mcp.junct.dev/mcp
What problem does it solve?
GMX has many data surfaces and your agent keeps hallucinating position or market fields because you lack a unified tool layer.
Who is it for?
Advanced indie builders creating GMX-focused dashboards, research agents, or integration tests that need rich derivatives data during development.
Skip if: Beginners who only need a simple price feed or anyone expecting a fully audited trade-execution stack with no manual verification.
What do I get? / Deliverables
You register one remote GMX MCP and let the agent query perps, options, and positions through 139 named tools while you build analytics or monitoring features.
- 139 GMX-oriented MCP tools callable from your agent
- Richer derivatives-aware code and docs during build
- Consolidated GMX data access instead of many ad hoc endpoints
Recommended MCP Servers
Journey fit
GMX MCP lands in Build because solo founders connect it while coding integrations—not as a substitute for launch-day marketing or ops monitoring alone. Integrations matches a large remote tool surface (139 tools) meant to be called from the agent during backend and dashboard work.
How it compares
Broad 139-tool GMX data MCP—not Hyperliquid’s minimal 2-tool stub or a generic CEX REST skill.
Common Questions / FAQ
Who is gmx-mcp for?
Developers building perps or DeFi products who use MCP-enabled agents and want GMX market and position data without writing dozens of API wrappers.
When should I use gmx-mcp?
Use it during Build when implementing features that read GMX perpetuals, options, or positions—alerts, UI backends, or agent research—not for casual one-off price checks unless you already run MCP.
How do I add gmx-mcp to my agent?
Configure https://gmx.mcp.junct.dev/mcp as a streamable-http remote MCP server in your client, restart, and confirm the GMX tool set (139 tools) is available to the agent.