SODAX Builders MCP Server is an MCP (Model Context Protocol) server for AI coding assistants, designed to let developers directly access real-time protocol data and SDK documentation for SODAX cross-chain DeFi within their development workflow.
Purpose The server provides AI coding assistants with instant access to SODAX cross-chain API data, and includes built-in auto-synced cross-chain SDK documentation to help developers build cross-network DeFi integrations.
Main Capabilities
- Cross-network token swaps: supports swapping tokens across more than 20 networks.
- Money market rate queries: query money market lending rates and borrowing APY.
- Solver volume queries: view cross-network solver volume.
- Intent history retrieval: query intent history by transaction hash or wallet address.
- Cross-chain relay tracking: track relay packets and their execution status.
- SDK documentation: provides complete cross-chain SDK documentation; tools with the docs_ prefix automatically proxy from docs.sodax.com, and automatically update when the documentation changes, with no manual sync required.
Tool Categories (according to official materials)
- Network Configuration (9 tools)
- Intents & Solver (9 tools)
- Intent Relay (3 tools)
- AMM & Liquidity (2 tools)
- Money Market (6 tools)
- Partners & Token (6 tools)
- Cross-Chain SDK Documentation (dynamic)
Usage Add the MCP server URL to the AI coding assistant's configuration. The server is compatible with Claude, Cursor, VS Code, Windsurf, ChatGPT, and other agents that support MCP. A single connection provides access to all cross-network API tools and SDK documentation. For clients that do not support streamable HTTP (such as Gemini CLI), the SSE endpoint (SSE Transport, legacy) can be used.
After connecting, you can ask the AI coding assistant sample questions such as:
- Cross-network swaps and tokens: "Which networks does SODAX support for cross-chain swaps?" "Get swap tokens available cross-chain on Base" "How do I use the SODAX SDK to integrate cross-chain swaps?"
- Solver volume and intent history: "Show today's cross-network solver volume" "Query this intent transaction: 0x..." "Get the intent history for this wallet address" "Quote 100 USDC to SODA on Sonic" "What is the solver's current oracle price for bnUSD on Avalanche?"
- Cross-chain relay: "Track the relay packets for this source transaction: 0x..." "Has the packet with conn_sn=42 in this transaction been executed?"
- Money market and lending: "What are the lending rates in the SODAX money market?" "Show the borrowing APY for each asset" "Get my money market positions"
- SDK documentation: "How do I integrate the SODAX cross-chain SDK?" "Show a code example for cross-network token swaps" "What SDK methods are available for intent-based execution?"
Local Development and CI Every PR entering development / master runs .github/workflows/ci.yml, executing the same four checks as locally. Git hooks (husky + commitlint + lint-staged) are automatically installed via the prepare script in pnpm install: pre-commit runs pnpm checkTs, pnpm test, then lint-staged (runs biome check --write on staged files, applying formatting and safe lint fixes); commit-msg runs commitlint to check the Conventional Commits specification. In emergencies, hooks can be skipped once, but CI will still enforce the same checks on the PR.
Environment Variables and Deployment On startup, the server automatically loads the .env file (via Node's --env-file-if-exists flag, requiring Node ≥ 22.9.0). For local development, copy .env.example to .env; if .env does not exist, all variables fall back to default values. In production, Coolify injects directly into the process environment. Deployment is handled through Coolify using aBranch promotion process: Production tracks master, serving https://builders.sodax.com；Staging tracks development (internal only). Promotion process: feature branch → PR into development → automatically deployed to staging after merge; development → PR into master → automatically deployed to production after merge. Hotfixes can branch from master and PR directly to master, then be merged back into development. Deployment notes: the included nixpacks.toml automatically handles deployment; the environment variable NODE_ENV=production must be set.
Use cases Suitable for developers who need to query real-time SODAX cross-chain DeFi data, retrieve intent and solver information, track cross-chain relays, or consult cross-chain SDK documentation in an AI programming assistant to build cross-network DeFi integrations.
Limitations The materials do not provide information such as the server's fees, pricing, platform restrictions, or performance guarantees. Using the SSE endpoint is only suitable for clients that do not support streamable HTTP. Running locally requires Node ≥ 22.9.0.
