Upbit MCP Server

If you want an AI assistant working directly with Upbit, the upbit mcp server is the bridge. A server implementation for Upbit Cryptocurrency Exchange OpenAPI using the Model Context Protocol (MCP). This project provides tools to interact with Upbit exchange services, such as retrieving market data (quotes, orderbooks, trade history, chart data), account information.

What Upbit does

A server implementation for Upbit Cryptocurrency Exchange OpenAPI using the Model Context Protocol (MCP). This project provides tools to interact with Upbit exchange services, such as retrieving market data (quotes, orderbooks, trade history, chart data), account information, creating and canceling orders, managing deposits/withdrawals, and performing technical analysis.

Key capabilities

• Market data retrieval (ticker, orderbook, trades, candle data)
• Account information (balance, order history)
• Order creation and cancellation
• Deposit and withdrawal functions
• Technical analysis tools

Installing the upbit mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply 2 environment variables: UPBIT_ACCESS_KEY, UPBIT_SECRET_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

Before you begin, you need to get your Upbit API keys: 1. Create an account on Upbit if you don't already have one 2. Go to the Upbit Developer Center 3. Create a new API key 4. Make sure to set appropriate permissions (read, trade, withdraw as needed) 5. Store your API keys(UPBIT_ACCESS_KEY, UPBIT_SECRET_KEY) in the

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Upbit sits in that group. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• Maintained by solangii, written in Python.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the upbit mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.