Let your AI agent build your SODAX integration

In May, SODAX announced SDK V2 with built-in support for agentic workflows. This page is the hands-on part: how to point Claude Code, Cursor, VS Code, Windsurf or ChatGPT at SODAX so your agent stops guessing and starts building from real values. The short version: add one URL to your agent’s MCP config.

https://builders.sodax.com/mcp

From that point the agent can read the live list of supported networks and swap tokens, pull a swap quote, inspect money market reserves and user positions, look up an intent by hash, and search the SODAX developer docs while it writes your code. No API key is required.

The Builders MCP never holds a key and never signs. The one tool that touches a transaction, sodax_relay_submit_tx, takes a transaction that is already signed and finalized and hands it to the intent relay. Your code builds the transaction and your wallet signs it.

Add it to your agent

Most MCP clients accept the same JSON block:

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

Claude Code
Cursor
VS Code / Copilot
Windsurf, ChatGPT and others

One command from your project root:

claude mcp add --transport http sodax-builders https://builders.sodax.com/mcp

Put the JSON block above in .cursor/mcp.json for a single project, or add it under Settings → MCP to make it global.

VS Code uses its own schema. Servers live under servers and the transport is named. Save this as .vscode/mcp.json:

{
  "servers": {
    "sodax-builders": {
      "type": "http",
      "url": "https://builders.sodax.com/mcp"
    }
  }
}

Windsurf, ChatGPT, Claude Desktop, Cline, Goose and Roo Code are all listed as compatible on builders.sodax.com. Add https://builders.sodax.com/mcp using your client’s own MCP config format. For clients that do not speak streamable HTTP, such as Gemini CLI, use the SSE endpoint instead: https://builders.sodax.com/sse.

What the agent can reach

The live tools cover the same public data as the SODAX HTTP API, so answers reflect today’s configuration rather than whatever the model saw in training. A few of the ones you will lean on while building:

You want to know	Tool
Which networks SODAX supports	`sodax_get_supported_chains`
Which tokens can be swapped, optionally per network	`sodax_get_swap_tokens`
Chains, tokens and protocol settings in one call	`sodax_get_all_config`
Spoke chain configs with contract addresses and RPCs	`sodax_get_all_chains_configs`
Hub (Sonic) assets that represent spoke tokens	`sodax_get_hub_assets`
A swap quote	`sodax_get_solver_quote`
Money market assets, rates and reserves	`sodax_get_money_market_assets`, `sodax_get_money_market_reserve_assets`
A wallet’s lending and borrowing position	`sodax_get_user_position`
The status of an intent or transaction	`sodax_get_intent`, `sodax_get_transaction`, `sodax_get_user_transactions`
Whether a cross-network message has landed	`sodax_relay_get_transaction_packets`

Alongside the live data sit the documentation tools. They proxy search and full-page fetch over docs.sodax.com and stay in sync as the docs change, so the agent can pull the current integration guide instead of recalling an old one. If docs ever look unavailable, docs_health checks the connection and docs_refresh reconnects.

Three layers, one workflow

The MCP is one of three pieces SODAX ships for agents. Each covers a different gap. 1. Builders MCP: live data and docs. A hosted server the agent calls at runtime. It answers “which tokens can be swapped from Base today?” or “why did this intent fail?” with current values. 2. @sodax/skills: version-locked SDK knowledge. Skill files installed into your repo that teach the agent the right v2 API shapes, patterns and anti-patterns for @sodax/sdk, @sodax/dapp-kit, @sodax/wallet-sdk-core and @sodax/wallet-sdk-react. Training data drifts; these files match the SDK version you ship. Install them with the skills CLI from your repo root:

npx skills@latest add icon-project/sodax-sdks/packages/skills

That lands five skills: sodax-build, a front-door skill that interviews you and turns an idea into a product brief, plus one mode-gated skill per SDK package (sodax-sdk, sodax-dapp-kit, sodax-wallet-sdk-core, sodax-wallet-sdk-react). Each package skill switches between integration mode for new v2 code and migration mode for porting v1. To preview the skills before installing, add --list. To confirm what landed:

npx skills list

Prefer a devDependency, or working in a web chat? Use npm and point your agent at the router file:

pnpm add -D @sodax/skills

Then add a line to your project rules telling the agent to read node_modules/@sodax/skills/AGENTS.md before writing any @sodax/* code. When you bump the SDK, re-run the npx skills command or bump @sodax/skills so the knowledge moves with it. 3. skill.md and llms.txt: discoverability. Any agent that can fetch a URL can start from sodax.com/skill.md, a hosted umbrella skill that routes to the granular sodax-* skills and lists the gotchas that cause silent failures, such as calling sodax.config.initialize() before config lookups and checking result.ok instead of using try/catch. sodax.com/llms.txt and docs.sodax.com/llms.txt give agents a clean index of canonical pages. Skills keep the generated code correct. The MCP keeps the values inside it real. Install both.

A realistic first prompt

With the MCP connected and skills installed in a fresh Next.js app, try something like:

“Add a swap page that lets a user swap USDC on Base into SOL on Solana using @sodax/dapp-kit. Before writing code, confirm both tokens are live on SODAX and show me a current quote for 100 USDC.”

Here is how the agent can work through it with the tools above:

Pick the right skills

For a React dapp, the skills route the agent to sodax-wallet-sdk-react for wallet connection and sodax-dapp-kit (or its narrower swap child) for the swap flow, both in integration mode.

Check live support

It calls sodax_get_supported_chains and sodax_get_swap_tokens filtered to Base and Solana, so the token list in your UI comes from current SODAX config.

Read the current guide

It searches the docs through the MCP for the dapp-kit swap guide and follows today’s version of it.

Get a real quote

It resolves the pair to hub (Sonic) assets, as the Builders MCP docs describe, and calls sodax_get_solver_quote, giving you a real number to sanity-check before any code ships.

Write the code

It writes the page with the patterns the skill enforces, such as reading result.ok on Result-returning calls and discriminating on error.code.

Confirm the swap you sign

After you sign a small mainnet swap in your own wallet, it uses sodax_get_user_transactions, sodax_get_intent and sodax_relay_get_transaction_packets to confirm the intent and track delivery to Solana.

SODAX is mainnet-only, so that last step is a real swap. Start small. This workflow is already proven in the wild: the community app Swaps without Borders went from an empty Next.js app to a mainnet swap in an afternoon using the Builders MCP.

Reference

Builders MCP docs

Client setup, tool overview and how the MCP pairs with skills.

AI Integration Guide

Every way to install and wire @sodax/skills.

MCP server source

The open-source Builders MCP server.

SDK V2 announcement

The May 2026 launch post.

​Add it to your agent

​What the agent can reach

​Three layers, one workflow

​A realistic first prompt

​Reference

Builders MCP docs

AI Integration Guide

MCP server source

SDK V2 announcement

Add it to your agent

What the agent can reach

Three layers, one workflow

A realistic first prompt

Reference