BloFin Setup

Guide users through setting up and configuring the BloFin MCP server for trading on BloFin exchange.

Prerequisites

• Node.js (v18+) and npm installed
• A BloFin account at blofin.com

Setup Steps

1. Install blofin-mcp

npm install -g blofin-mcp

Or install locally:

git clone https://github.com/your-org/blofin-mcp.git
cd blofin-mcp
npm install
npm run build

2. Create BloFin API Keys

Direct the user to BloFin API Management:

1. Log in to BloFin
2. Navigate to Account > API Management
3. Click Create API Key
4. Set permissions:
   • READ — view balances, order history, positions
   • TRADE — place and cancel orders
   • TRANSFER — move funds between accounts
5. Set a Passphrase (remember this)
6. (Recommended) Bind to IP whitelist for security
7. Save the API Key and Secret Key — the secret is shown only once

3. Configure MCP Server

Add the blofin MCP server to your agent's MCP configuration (e.g. mcp.json or settings.json):

{
  "mcpServers": {
    "blofin": {
      "command": "node",
      "args": ["/path/to/blofin-mcp/dist/index.js"],
      "env": {
        "BLOFIN_API_KEY": "your-api-key",
        "BLOFIN_API_SECRET": "your-api-secret",
        "BLOFIN_PASSPHRASE": "your-passphrase",
        "BLOFIN_BROKER_ID": "your-broker-id (optional)",
        "BLOFIN_BASE_URL": "https://openapi.blofin.com"
      }
    }
  }
}

Replace /path/to/blofin-mcp with the actual installation path (e.g., the global npm path or the local clone directory).

4. Base URL Configuration

• Default is demo trading if BLOFIN_BASE_URL is not set
• Always start with demo trading to verify your setup works correctly
• Switch to production only after successful demo testing

5. Verify Connection

After configuration, verify the setup works:

1. Use get_apikey_info to verify API key permissions and status
2. Use get_tickers with instId: "BTC-USDT" to test public data access
3. Use get_balance to verify authenticated access
4. Check that the API key has the expected permissions (readOnly field: 0 = Read+Write, 1 = Read only)

6. Troubleshooting

Environment Variables Reference

Security Best Practices

• Never share or expose your API secret and passphrase
• Always bind API keys to specific IP addresses in production
• Use the minimum required permissions for your use case
• Regularly rotate API keys
• Start with READ permission only and upgrade as needed