Skip to main content
Glama
Bithumb MCP Server

Bithumb MCP Server

Bithumb MCP Server

Korean version available here

@zereight/bithumb-mcp

Bithumb MCP (Model Context Protocol) Server. Allows interaction with the Bithumb API to fetch cryptocurrency information and manage transactions.

Related MCP server: Bitso MCP Server

Usage

Installing via Smithery

To install bithumb-mcp for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @zereight/bithumb-mcp --client claude

Using with Claude, Roo Code, Cline, etc.

Add the following configuration to your MCP settings file (e.g., mcp_settings.json):

{
  "mcpServers": {
    "bithumb-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@zereight/bithumb-mcp@latest"
      ],
      "env": {
        "BITHUMB_API_KEY": "YOUR_BITHUMB_API_KEY", // Required
        "BITHUMB_SECRET_KEY": "YOUR_BITHUMB_SECRET_KEY" // Required
      },
      "disabled": false
    }
  }
}

Note: Always use @latest tag to ensure you are using the most recent version with all bug fixes and improvements.

Using with Cursor (or direct CLI)

When using with Cursor or running directly, you can set up environment variables and run the server as follows:

env BITHUMB_API_KEY=YOUR_BITHUMB_API_KEY \
    BITHUMB_SECRET_KEY=YOUR_BITHUMB_SECRET_KEY \
    npx @zereight/bithumb-mcp
  • BITHUMB_API_KEY (Required): Your Bithumb API key.

  • BITHUMB_SECRET_KEY (Required): Your Bithumb secret key.

Tools 🛠️

  1. get_ticker

    • Fetches cryptocurrency ticker information.

    • Inputs:

      • coinCode (string, required): The cryptocurrency symbol (e.g., BTC, ETH).

    • Returns: Ticker information (JSON string).

  2. get_orderbook

    • Fetches order book information.

    • Inputs:

      • coinCode (string, required): The cryptocurrency symbol (e.g., BTC, ETH).

    • Returns: Order book details (JSON string).

  3. get_transaction_history

    • Fetches recent transaction history.

    • Inputs:

      • coinCode (string, required): The cryptocurrency symbol (e.g., BTC, ETH).

    • Returns: Transaction history (JSON string).

  4. get_assets_status

    • Fetches asset deposit/withdrawal status.

    • Inputs:

      • orderCurrency (string, required): The cryptocurrency symbol (e.g., BTC, ETH).

    • Returns: Deposit/withdrawal status (JSON string).

  5. get_candlestick

    • Fetches candlestick data.

    • Inputs:

      • orderCurrency (string, required): The cryptocurrency symbol (e.g., BTC, ETH).

      • paymentCurrency (string, required): Payment currency (e.g., KRW, BTC).

      • chartIntervals (string, required): Chart interval (e.g., '1m', '3m').

    • Returns: Candlestick data (JSON string).

  6. post_account

    • Fetches member account information and fees.

    • Inputs:

      • coinCode (string, required): The cryptocurrency symbol (e.g., BTC, ETH).

    • Returns: Account information (JSON string).

  7. get_balance

    • Fetches account balance.

    • Inputs:

      • coinCode (string, optional): The cryptocurrency symbol (e.g., BTC, ETH) or ALL.

    • Returns: Balance information (JSON string).

  8. post_wallet_address

    • Fetches member's coin deposit wallet address.

    • Inputs:

      • coinCode (string, optional): The cryptocurrency symbol (e.g., BTC, ETH).

    • Returns: Wallet address (JSON string).

  9. post_ticker_user

    • Fetches member's recent virtual asset transaction information.

    • Inputs:

      • orderCurrency (string, required): The cryptocurrency symbol (e.g., BTC, ETH).

    • Returns: Transaction information (JSON string).

  10. post_orders

    • Fetches member's order details.

    • Inputs:

      • order_currency (string, required): Order currency symbol.

      • orderId (string, optional): Order ID.

      • type (string, optional): Order type (bid or ask).

      • count (number, optional): Number of orders to retrieve.

      • after (number, optional): Retrieve orders after this timestamp.

    • Returns: Order details (JSON string).

  11. post_order_detail

    • Fetches details of a specific member order.

    • Inputs:

      • orderId (string, required): Order ID.

      • orderCurrency (string, required): Cryptocurrency symbol (e.g., BTC, ETH).

    • Returns: Order details (JSON string).

  12. post_user_transactions

    • Fetches member's transaction completion history.

    • Inputs:

      • searchGb (number, required): Search type (0: all, 1: buy complete, etc.).

      • orderCurrency (string, required): Cryptocurrency symbol (e.g., BTC, ETH).

      • offset (number, optional): Start index for retrieval.

      • `count» (number, optional): Number of transactions to retrieve.

    • Returns: Transaction history (JSON string).

  13. post_place

    • Places a limit order (buy/sell).

    • Inputs:

      • `orderCurrency» (string, required): Cryptocurrency symbol (e.g., BTC, ETH).

      • `units» (number, required): Order quantity.

      • `price» (number, required): Order price.

      • `type» (string, required): Order type (bid or ask).

    • Returns: Order placement confirmation (JSON string).

  14. post_cancel

    • Cancels an order.

    • Inputs:

      • `type» (string, required): Order type (bid or ask).

      • `orderId» (string, required): Order ID to cancel.

      • `orderCurrency» (string, required): Cryptocurrency symbol (e.g., BTC, ETH).

    • Returns: Cancellation confirmation (JSON string).

  15. post_market_buy

    • Places a market buy order.

    • Inputs:

      • `units» (number, required): Quantity to buy.

      • `orderCurrency» (string, required): Cryptocurrency symbol (e.g., BTC, ETH).

    • Returns: Order placement confirmation (JSON string).

  16. post_market_sell

    • Places a market sell order.

    • Inputs:

      • `units» (number, required): Quantity to sell.

      • `orderCurrency» (string, required): Cryptocurrency symbol (e.g., BTC, ETH).

    • Returns: Order placement confirmation (JSON string).

  17. post_withdrawal_coin

    • Requests a coin withdrawal.

    • Inputs:

      • `units» (number, required): Withdrawal quantity.

      • `address» (string, required): Withdrawal address.

      • `currency» (string, optional): Cryptocurrency symbol (e.g., BTC, ETH).

      • `destination» (string, optional): Destination tag/memo (if required).

    • Returns: Withdrawal request confirmation (JSON string).

  18. post_withdrawal_krw

    • Requests a KRW withdrawal (Deprecated by Bithumb).

    • Inputs:

      • `bank» (string, required): Bank code and name.

      • `account» (string, required): Account number.

      • `price» (number, required): Withdrawal amount.

    • Returns: Withdrawal request confirmation (JSON string).

Environment Variables

Before running the server, you must set the following environment variables:

BITHUMB_API_KEY=YOUR_BITHUMB_API_KEY
BITHUMB_SECRET_KEY=YOUR_BITHUMB_SECRET_KEY

License

MIT License

Available Tools

19 tools
get_assets_statusC

Get asset deposit/withdrawal status (Public)

Inputs: orderCurrency (required).

get_balanceC

Get account balance (Private)

Inputs: coinCode.

get_btciB

Get Bithumb Index (BTMI, BTAI) information (Public)

get_candlestickC

Get Candlestick data (Public)

Inputs: orderCurrency (required), paymentCurrency (required), chartIntervals (required).

get_orderbookC

Get order book information (Public)

Inputs: coinCode (required).

get_tickerC

Get cryptocurrency ticker information (Public)

Inputs: coinCode (required).

get_transaction_historyB

Get recent transaction history (Public)

Inputs: coinCode (required).

post_accountC

Get member account information and fees (Private)

Inputs: coinCode (required).

post_cancelC

Cancel an order (Private)

Inputs: type (required), orderId (required), orderCurrency (required).

post_market_buyC

Place a market buy order (Private)

Inputs: units (required), orderCurrency (required).

post_market_sellC

Place a market sell order (Private)

Inputs: units (required), orderCurrency (required).

post_order_detailC

Get details of a specific member order (Private)

Inputs: orderId (required), orderCurrency (required).

post_ordersC

Get member's order details (Private)

Inputs: order_currency (required), orderId, type, count, +1 more.

post_placeC

Place a limit order (buy/sell) (Private)

Inputs: orderCurrency (required), units (required), price (required), type (required).

post_ticker_userC

Get member's recent virtual asset transaction information (Private)

Inputs: orderCurrency (required).

post_user_transactionsC

Get member's transaction completion history (Private)

Inputs: searchGb (required), orderCurrency (required), offset, count.

post_wallet_addressC

Get member's coin deposit wallet address (Private)

Inputs: coinCode.

post_withdrawal_coinC

Request a coin withdrawal (Private)

Inputs: units (required), address (required), currency, destination.

post_withdrawal_krwC

Request a KRW withdrawal (Private, Deprecated by Bithumb)

Inputs: bank (required), account (required), price (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting specific resources like balance, orders, or transactions, but there is some overlap between post_orders and post_order_detail, and post_ticker_user and post_user_transactions could be confused as both relate to member transaction information. Descriptions help clarify, but minor ambiguity exists.

    Naming Consistency4/5

    Tools follow a consistent verb_noun pattern with 'get_' for public data and 'post_' for private actions, but the naming is slightly inconsistent as 'post_account' and 'post_place' use generic verbs, while others like 'post_market_buy' are more specific. Overall, the pattern is predictable and readable.

    Tool Count4/5

    With 19 tools, the count is slightly high but reasonable for a cryptocurrency exchange server covering public data and private trading operations. It includes essential functions like order management, balance checks, and transactions, though it might feel a bit heavy compared to simpler servers.

    Completeness5/5

    The tool set provides comprehensive coverage for a cryptocurrency exchange domain, including public market data (e.g., ticker, orderbook), private account management (e.g., balance, wallet), and full order lifecycle (place, cancel, detail). No obvious gaps are present, enabling agents to handle typical trading workflows effectively.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      Interact with Upbit cryptocurrency exchange services to retrieve market data, manage accounts, and execute trades. Simplify your trading experience with tools for order management, deposits, withdrawals, and technical analysis.
      10
      17
      MIT
    • A
      license
      D
      quality
      D
      maintenance
      Enables interaction with the Bitso cryptocurrency exchange API to access withdrawals and fundings data. Provides comprehensive tools for listing, filtering, and retrieving withdrawal and funding transactions with proper authentication and error handling.
      6
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables interaction with the Upbit cryptocurrency exchange through public market data tools and optional private trading tools. Supports getting ticker data, orderbooks, trades, account information, and executing trading operations through natural language.
      19
      20 npm
      2
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to interact with Bitget cryptocurrency exchange for spot and futures trading. Supports real-time market data, order management, account balances, leverage control, and position tracking with demo trading capabilities.
      17
      6
      MIT