mcp-server-usdd

An MCP server for the USDD protocol across TRON, Ethereum, and BNB Smart Chain. The current version focuses on three core surfaces: Vault/CDP, PSM, and USDD Savings.

Scope

Current implementation focuses on:

• Vault lifecycle: open, deposit collateral, mint USDD, repay, withdraw, close
• PSM lifecycle: inspect fees, swap into USDD, swap out of USDD
• Savings lifecycle: inspect USDD Savings, deposit, withdraw
• Risk and monitoring for vaults: summaries, oracle status, collateral buffers
• Token preflight checks: balances, allowances, approvals

Supported Networks

Prerequisites

• Node.js 20+
• Optional but recommended:
  • TRONGRID_API_KEY for more reliable TRON access
  • dedicated ETH_RPC_URL
  • dedicated BSC_RPC_URL

Developer

Installation

git clone https://github.com/decentralized-usd/mcp-server-usdd
cd mcp-server-usdd
npm install

Usage

npm start
npm run start:http
npm run dev

Configuration

Wallet Setup (Automatic)

The server uses @bankofai/agent-wallet for encrypted local wallet storage. On first startup it will automatically initialize ~/.agent-wallet/ and create a default wallet if none exists.

On startup, the server will:

1. Check for existing wallets in ~/.agent-wallet/
2. If none are found, auto-generate a new encrypted wallet
3. Display the derived TRON and EVM addresses in the console

You can also manage wallets via CLI or MCP tools:

CLI (agent-wallet)

# Import an existing private key or mnemonic
npx agent-wallet add

# Generate a new wallet
npx agent-wallet generate

# List all wallets
npx agent-wallet list

# Switch active wallet
npx agent-wallet activate <wallet-id>

MCP Tools (runtime)

# Optional for automated/CI setups
export AGENT_WALLET_PASSWORD="your_wallet_password"

# Strongly recommended — avoids TronGrid 429 rate limiting on mainnet
export TRONGRID_API_KEY="your_trongrid_api_key"

Client Configuration

Claude Desktop

Add the following config to:

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mcp-server-usdd": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@usdd/mcp-server-usdd"],
      "env": {
        "TRONGRID_API_KEY": "your_trongrid_api_key"
      }
    }
  }
}

Claude Code

Create .mcp.json in the project root directory:

{
  "mcpServers": {
    "mcp-server-usdd": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@usdd/mcp-server-usdd"],
      "env": {
        "TRONGRID_API_KEY": "your_trongrid_api_key"
      }
    }
  }
}

Cursor

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "mcp-server-usdd": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@usdd/mcp-server-usdd"],
      "env": {
        "TRONGRID_API_KEY": "your_trongrid_api_key"
      }
    }
  }
}

Tools

Common

Vault

PSM

USDD Savings

Prompts

Architecture

mcp-server-usdd/
├── src/
│   ├── core/
│   │   ├── chains.ts
│   │   ├── abis.ts
│   │   ├── tools.ts
│   │   ├── prompts.ts
│   │   ├── resources.ts
│   │   └── services/
│   │       ├── clients.ts
│   │       ├── contracts.ts
│   │       ├── protocol.ts
│   │       ├── vault.ts
│   │       ├── psm.ts
│   │       ├── savings.ts
│   │       ├── tokens.ts
│   │       ├── wallet.ts
│   │       └── utils.ts
│   ├── index.ts
│   └── server/
│       ├── server.ts
│       └── http-server.ts
└── build/

Notes

• Vault writes assume the configured wallet can sign on the target chain.
• ERC20/TRC20 flows often require approve_token first.
• TRON, ETH, and BSC deployments have similar USDD protocol structure but different addresses and token decimals.
• This version intentionally excludes migration and auction actions so we can iterate the Vault + PSM + USDD Savings core first.

Security Considerations

• Private keys are encrypted and stored locally in ~/.agent-wallet/.
• Private keys are never returned by MCP tools.
• The optional AGENT_WALLET_PASSWORD is intended for automation and CI environments.
• Write operations should be treated as state-changing actions and reviewed carefully before execution.
• Vault prompts include risk-review steps so borrowing decisions are checked against current collateral health.
• Test on a safe environment or with small amounts before using mainnet-sized positions.
• Be cautious with large or unlimited token approvals when using approve_token.
• Never share local MCP client configuration files if they contain private keys or sensitive RPC credentials.

Example Conversations

• "What vault types are available on Ethereum?" -> AI calls get_supported_ilks with network=eth and summarizes the supported vault collateral types.
• "Open a TRX-A/USDT-A/WBTC-A vault on Tron and mint 500 USDD" -> AI uses open_usdd_vault: checks wallet, reviews oracle status, executes deposit_and_mint, then verifies the new vault risk.
• "Am I close to liquidation on vault 123?" -> AI calls get_vault_summary and analyze_vault_risk, then explains the health factor and collateral buffer.
• "Repay part of my vault debt on BSC" -> AI uses manage_vault_lifecycle with action=repay: checks USDD balance and allowance, calls repay_usdd, then verifies the updated vault state.
• "Close my vault and withdraw the collateral" -> AI uses repay_and_close_vault: checks debt, balance, allowance, calls close_vault, then confirms the vault state after repayment.
• "What are the current PSM fees on Ethereum?" -> AI calls get_psm_status with network=eth and reports fee-in, fee-out, and whether swaps are enabled.
• "Swap 10,000 USDT into USDD through the PSM" -> AI uses use_psm: checks PSM status, then calls psm_swap_to_usdd and reports the transaction result.
• "Swap 5,000 USDD back to USDC on BSC" -> AI calls get_psm_status, then executes psm_swap_from_usdd and reminds the user to re-check balances.
• "What is my USDD balance on Tron?" -> AI calls get_protocol_overview to identify the USDD token address, then calls get_token_balance.
• "Do I have enough allowance for the USDT PSM?" -> AI calls check_allowance with the token and PSM spender, then suggests approve_token only if needed.
• "What is the current USDD Savings status on Ethereum?" -> AI calls get_savings_status and summarizes total assets, savings rate, and wallet shares.
• "Deposit 2,000 USDD into sUSDD" -> AI uses use_savings: checks savings status, calls deposit_savings, then re-checks savings metrics.
• "Withdraw 500 USDD from sUSDD on BSC" -> AI calls get_savings_status, executes withdraw_savings, and confirms the updated share balance.

License

MIT License Copyright (c) 2026 USDD