lazy-dinosaur/ccxt-mcp

한국어 버전(Korean version)
CCXT MCP Server is a server that allows AI models to interact with cryptocurrency exchange APIs through the Model Context Protocol (MCP). This server uses the CCXT library to provide access to more than 100 cryptocurrency exchanges and their trading capabilities.
## 🚀 Quick Start
bash
# Install the package globally
npm install -g @lazydino/ccxt-mcp
# Run with default settings
ccxt-mcp
# or run without installation
npx @lazydino/ccxt-mcp
## Installation and Usage
### Global Installation
bash
# Install the package globally
npm install -g @lazydino/ccxt-mcp
### Running with npx
You can run it directly without installation:
bash
# Using default settings
npx @lazydino/ccxt-mcp
# Using custom configuration file
npx @lazydino/ccxt-mcp --config /path/to/config.json
View help:
bash
npx @lazydino/ccxt-mcp --help
## Configuration
### Registering the MCP Server in Claude Desktop
1. Open Claude Desktop Settings:
Go to the Settings menu in the Claude Desktop app
Find the "MCP Servers" section
2. Add a New MCP Server:
Click the "Add Server" button
Server name: ccxt-mcp
Command: npx @lazydino/ccxt-mcp
Additional arguments (optional): --config /path/to/config.json
3. Save and Test the Server:
Save the settings
Test the connection with the "Test Connection" button
### Configuration Methods - Two Options
#### Option 1: Include Account Information Directly in Claude Desktop Settings (Basic Method)
This method includes CCXT account information directly in the Claude Desktop settings file (claudedesktopconfig.json):
json
"mcpServers": {
"ccxt-mcp": {
"command": "npx",
"args": ["-y", "@lazydino/ccxt-mcp"],
"mcpBearerToken": "YOURMCPTOKEN",
"accounts": [
"name": "bybitmain",
"exchangeId": "bybit",
"apiKey": "YOURAPIKEY",
"secret": "YOURSECRETKEY",
"defaultType": "spot"
},
"name": "bybitfutures",
"exchangeId": "bybit",
"apiKey": "YOURAPIKEY",
"secret": "YOURSECRETKEY",
"defaultType": "swap"
Using this method, you don't need a separate configuration file. All settings are integrated into the Claude Desktop configuration file.
#### Option 2: Using a Separate Configuration File (Advanced Method)
To separate account information into a separate configuration file, set up as follows:
1. Create a Separate Configuration File (e.g., ccxt-config.json):
json
"mcpBearerToken": "YOURMCPTOKEN",
"accounts": [
"name": "bybitmain",
"exchangeId": "bybit",
"apiKey": "YOURAPIKEY",
"secret": "YOURSECRETKEY",
"defaultType": "spot"
},
"name": "bybitfutures",
"exchangeId": "bybit",
"apiKey": "YOURAPIKEY",
"secret": "YOURSECRETKEY",
"defaultType": "swap"
> Important: The configuration file must contain an accounts array at the root level, as shown above.
> Important: If you run the server in HTTP+SSE mode (--sse), set mcpBearerToken in the same config file. Clients must send Authorization: Bearer on requests.
2. Specify the Configuration File Path in Claude Desktop Settings:
json
"mcpServers": {
"ccxt-mcp": {
"command": "npx",
"args": [
"-y",
"@lazydino/ccxt-mcp",
"--config",
"/path/to/ccxt-config.json"
> Note: When using a separate configuration file with the --config option, the server will look for the accounts array directly in the root of the JSON file, not in mcpServers.ccxt-mcp.accounts path.