builders-sodax

This MCP server exposes SODAX cross-network DeFi data and SDK documentation through a set of tools that you can query from any MCP-compatible agent. The server provides two main tool categories: Cross-Network API Data and DeFi & Token Data, plus dynamic Cross-Chain SDK Documentation tools that proxy content from GitBook. You can list available tools, call specific endpoints for swaps, lending, volume, and intents, and fetch real-time SDK docs. To begin, connect your MCP client to the sodax-builders MCP server URL and then start issuing tool calls such as sodax_get_supported_chains to discover networks, sodax_get_swap_tokens to retrieve tokens across chains, sodax_get_transaction to inspect an individual intent, and sodax_get_volume for solver activity. For SDK docs, use the docs_* tools to search, list, health-check, and refresh documentation through the proxied GitBook source. This setup enables live cross-network DeFi data and auto-updating SDK docs directly in your development workflow.

Prerequisites: Node.js (recommended LTS), a package manager (pnpm is used in this project), and Git. You may also run via Docker if you prefer containerized deployment.

1. Clone the repository

• git clone https://github.com/your-org/gosodax-builders-sodax-mcp-server.git
• cd gosodax-builders-sodax-mcp-server

2. Install dependencies

• pnpm install

3. Build (if applicable) and start in development or production mode

• pnpm dev # development mode
• pnpm build # production build
• pnpm start # production server

If you prefer Docker deployment:

4. Build and run with Docker

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

Environment variables (examples):

• PORT=3000
• TRANSPORT=http
• NODE_ENV=production

Tips and common considerations:

• The MCP config uses the node command with a path to your server entry (server.js). Adjust the path if your build outputs to a different entry file.
• Environment variables PORT and TRANSPORT control how the server is exposed and how MCP clients connect. Set TRANSPORT to http for standard REST-like MCP access or to stdio if integrating with in-process tooling.
• The included nixpacks.toml (referenced in deployment docs) helps with deployment in supported environments; ensure PORT and NODE_ENV are configured as shown in deployment notes.
• If you run via Docker, remember to map ports accordingly and consider using docker-compose for multi-service deployments. Check for updates to the SDK docs via the docs_* tools to keep SDK guidance current.
• When upgrading, re-run pnpm install to refresh dependencies and rebuild if necessary.