About blofin-setup
A setup guide for configuring the BloFin MCP server, aimed at users connecting BloFin exchange access to an agent. It covers installation, API credentials, demo and production endpoints, verification, and troubleshooting.
Key features
- 01Install blofin-mcp
- 02Create and configure API keys
- 03Set demo or production endpoint
- 04Verify server connection
- 05Troubleshoot common setup issues
Use cases
- 01Install the server with npm
- 02Configure credentials in MCP settings
- 03Test access on demo trading
- 04Diagnose API authentication or connectivity issues
MCP support
Guides users in adding and configuring the BloFin MCP server in an agent's MCP configuration, then verifying its API access.
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ blofin/ blofin-skills-hub --skill blofin-setupAfter installing, type/blofin-setupin Claude Code to confirm it loaded.
Details
From the project READMEBloFin 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/blofin/blofin-mcp.git
cd blofin-mcp
npm install
npm run build
2. Create BloFin API Keys
Direct the user to BloFin API Management:
- Log in to BloFin
- Navigate to Account > API Management
- Click Create API Key
- Set permissions:
READ— view balances, order history, positionsTRADE— place and cancel ordersTRANSFER— move funds between accounts
- Set a Passphrase (remember this)
- (Recommended) Bind to IP whitelist for security
- 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
| Environment | Base URL | Use Case |
|---|---|---|
| Demo Trading | https://demo-trading-openapi.blofin.com | Testing, learning, paper trading |
| Production | https://openapi.blofin.com | Real money trading |
- Default is demo trading if
BLOFIN_BASE_URLis 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:
- Use
get_apikey_infoto verify API key permissions and status - Use
get_tickerswithinstId: "BTC-USDT"to test public data access - Use
get_balanceto verify authenticated access - Check that the API key has the expected permissions (
readOnlyfield: 0 = Read+Write, 1 = Read only)
6. Troubleshooting
| Issue | Solution |
|---|---|
| Signature verification failed | Check that API secret and passphrase are correct; ensure no extra spaces |
| IP not in whitelist (152406) | Add your current IP to the API key's whitelist on BloFin |
| Access key expired (152402) | Keys without IP binding expire after 90 days; recreate or bind an IP |
| Rate limit (429) | Reduce request frequency; REST API limit is 500/min per IP |
| Connection timeout | Check your network; verify the base URL is correct |
Environment Variables Reference
| Variable | Required | Description |
|---|---|---|
BLOFIN_API_KEY | Yes | Your BloFin API key |
BLOFIN_API_SECRET | Yes | Your BloFin API secret key |
BLOFIN_PASSPHRASE | Yes | The passphrase set when creating the API key |
BLOFIN_BROKER_ID | No | Broker ID for order attribution (provided by BloFin) |
BLOFIN_BASE_URL | No | API base URL (defaults to demo trading endpoint) |
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
READpermission only and upgrade as needed