bit2me

This MCP server exposes Bit2Me tools through the MCP protocol, enabling AI assistants to securely access real-time market data, manage wallets, execute trades, and interact with Bit2Me’s Earn (staking) and Loans features. The server normalizes responses for LLM consumption and provides a catalog of 47 tools grouped into General, Broker (Simple Trading), Wallet, Pro Trading, Earn, and Loan categories. To use it, configure an MCP client to call the tools (e.g., wallet_get_pockets, trade_execute_order, earn_get_positions, loan_get_details) with optional JWT session tokens for session-based authentication. Supply API keys and secrets via environment variables or per-request parameters as described in the repository’s documentation. The server supports secure internal transfers between Wallet, Pro, and Earn and enforces permission-based access control via API keys. For QA environments, you can point the client to a different gateway URL if needed.

Basic usage flow:

• Authenticate with Bit2Me using API keys (recommended) or a JWT session token for multi-tenant scenarios.
• Call the desired MCP tool (e.g., wallet_get_pockets, pro_trade_order, earn_manage_strategy, loan_create) through your MCP client.
• Handle normalised responses with consistent payloads and metadata as described in the TOOL DOCUMENTATION.

Prerequisites:

• Node.js v18 or higher
• Access to a Bit2Me account with API keys configured

Installation steps:

1. Clone the repository:

git clone https://github.com/bit2me-devs/bit2me-mcp.git
cd bit2me-mcp

2. Install dependencies:

npm install

3. Configure environment variables:

• Create a .env file based on the example:

cp .env.example .env

• Edit .env and add your Bit2Me credentials and optional settings:

BIT2ME_API_KEY=YOUR_BIT2ME_ACCOUNT_API_KEY
BIT2ME_API_SECRET=YOUR_BIT2ME_ACCOUNT_API_SECRET

# Optional Configuration
BIT2ME_GATEWAY_URL=https://gateway.bit2me.com  # Default gateway URL
BIT2ME_REQUEST_TIMEOUT=30000
BIT2ME_MAX_RETRIES=3
BIT2ME_RETRY_BASE_DELAY=1000
BIT2ME_LOG_LEVEL=info

4. Build the project:

npm run build

5. Run the server (example using Node):

# Start locally (adjust as needed for your environment)
npx ts-node src/index.ts

Note: The deployment method you choose (npx, uv, docker, etc.) should reflect your environment. The provided README primarily documents the Node.js build/run workflow.

• Security: Never commit API keys to version control. Use environment variables or secret management.
• If you use JWT session tokens (jwt parameter), the server will use cookie-based authentication instead of API keys.
• For QA/staging, you can override BIT2ME_GATEWAY_URL to point to test endpoints.
• The MCP server includes rate limit handling with retries and exponential backoff. Be mindful of the per-request data volumes to avoid hitting rate limits.
• The CLI/tooling references and endpoint descriptions are available in TOOLS_DOCUMENTATION.md and data/tools.json for integration and tooling detail.