Builders Sodax MCP Server

SODAX Builders MCP Server

SODAX MCP server for AI coding assistants. Access live cross-network (cross-chain) API data: swap tokens across 19+ networks, query money market rates, look up solver volume, and search intent history. Includes full cross-chain SDK documentation that auto-syncs from SODAX developer docs. Build cross-network DeFi integrations with real-time protocol data directly in your development workflow.

One-liner: SODAX MCP server: live cross-network DeFi API data and auto-updating SDK docs for 19+ networks. Query swaps, lending, solver volume, and intent history from your AI coding assistant.

Quick Start

Add the MCP server URL to your AI coding assistant's configuration:

{
  "mcpServers": {
    "sodax-builders": {
      "url": "https://builders.sodax.com/mcp"
    }
  }
}

Works with Claude, Cursor, VS Code, Windsurf, ChatGPT, and other MCP-compatible agents. One connection gives you access to all cross-network API tools and SDK documentation.

SSE Transport (Legacy)

For clients that don't support streamable HTTP (e.g. Gemini CLI), use the SSE endpoint instead:

{
  "mcpServers": {
    "sodax-builders": {
      "url": "https://builders.sodax.com/sse"
    }
  }
}

Tools

Network Configuration (8 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)

Tools prefixed with docs_ are automatically proxied from the GitBook MCP at docs.sodax.com. They update automatically when documentation changes — no manual sync needed.

Example Prompts

Once connected, try asking your AI coding assistant:

Cross-Network Swaps & Tokens

• "What networks does SODAX support for cross-chain swaps?"
• "Get available swap tokens across chains on Base"
• "How do I integrate cross-chain swaps with the SODAX SDK?"

Solver Volume & Intent History

• "Show me cross-network solver volume for today"
• "Look up this intent transaction: 0x..."
• "Get intent history for this wallet address"
• "Quote me 100 USDC into SODA on Sonic"
• "What's the current oracle price the solver has for bnUSD on Avalanche?"

Cross-Chain Relay

• "Track the relay packets for this source tx: 0x..."
• "Has packet conn_sn=42 from this tx been executed yet?"

Money Market & Lending

• "What are the lending rates on SODAX money market?"
• "Show me borrowing APY rates across assets"
• "Get my money market position"

SDK Documentation

• "How do I integrate with the SODAX cross-chain SDK?"
• "Show me code examples for cross-network token swaps"
• "What SDK methods are available for intent-based execution?"

Data Sources

Local Development

# Install dependencies
pnpm install

# Run in development mode
pnpm dev

# Build for production
pnpm build

# Start production server
pnpm start

# Run the test suite (unit tests for drift-check logic)
pnpm test

CI & Local Checks

Every PR into development/master runs .github/workflows/ci.yml, which executes the same four checks you can run locally:

Git hooks (husky + commitlint + lint-staged)

pnpm install installs the hooks automatically via the prepare script:

• pre-commit — runs pnpm checkTs, pnpm test, then lint-staged (which runs biome check --write on staged files, applying both formatting and safe lint fixes).
• commit-msg — runs commitlint against the Conventional Commits spec. Messages like feat: add X pass; bad message is rejected.

To skip the hooks in a one-off emergency:

HUSKY=0 git commit -m "your message"

Don't make a habit of it — CI will still enforce the same checks on the PR.

Environment Variables

The server auto-loads a .env file on startup (via Node's --env-file-if-exists flag — requires Node ≥ 22.9.0). Copy .env.example to .env for local development; if no .env exists, every variable falls back to the default below. In production, Coolify injects these directly into the process environment.

Deployment

Environments

The server is deployed via Coolify with a branch-based promotion flow:

• Production — tracks master, serves https://builders.sodax.com
• Staging — tracks development (internal-only)

Promotion flow:

1. Feature branches → PR into development → auto-deploys to staging on merge.
2. development → PR into master → auto-deploys to production on merge.

Hotfixes can branch off master and PR directly into master, then be merged back into development.

Docker

docker build -t builders-sodax-mcp-server .
docker run -p 3000:3000 builders-sodax-mcp-server

Docker Compose

docker-compose up -d

Deployment notes

The included nixpacks.toml handles deployment automatically. Set these environment variables:

• PORT=3000
• NODE_ENV=production

API Endpoints

Related

• SODAX — sodax.com
• SDK Documentation — docs.sodax.com (proxied automatically)

License

MIT