MCP Bybit API Interface

Name: MCP Bybit API Interface
Author: dlwjdtn535

@dlwjdtn535

Repository

About MCP Bybit API Interface

No overview available yet

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mcp-bybit-server": {
      "command": "uv",
      "args": [
        "sync"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is MCP Bybit API Interface?

MCP Bybit API Interface is an MCP (Model Context Protocol) server that provides a convenient interface to the Bybit V5 API. It allows users to fetch market data, manage account information, and place or cancel orders through MCP tools. The server is intended for developers and traders who want to interact with Bybit programmatically via AI assistants or custom workflows.

How to use MCP Bybit API Interface?

Clone the repository, install dependencies with uv sync, and run mcp-bybit-server over stdio. Configure your MCP client (e.g., Claude Desktop) by adding the server definition to its settings file with environment variables for your Bybit API credentials, testnet flag, and trading enablement. The server can also be run via Docker. Trading tools are disabled by default and must be explicitly enabled with TRADING_ENABLED=true.

Key features of MCP Bybit API Interface

Fetches real-time market data (orderbook, kline, tickers, etc.)
Manages account balances, positions, and order history
Places, amends, and cancels orders with safety caps
Provides pre-flight order validation before execution
Supports testnet for safe experimentation
Hard‑blocks all mutating tools when READONLY_MODE=true
Caps single order notional value to 100 USDT by default
Offers a composite market_snapshot tool for quick overview

Use cases of MCP Bybit API Interface

Fetching live market data for analysis or trading decisions
Automating trade execution with safety limits and validation
Monitoring portfolio balances and open positions
Backtesting or simulating orders on the Bybit testnet
Building AI‑assisted trading interfaces via MCP tools

FAQ from MCP Bybit API Interface

How do I enable trading on the server?

Set the environment variable TRADING_ENABLED=true. By default, trading is disabled and all mutating tools (place_order, cancel_order, etc.) will return an error.

What is the default order size limit?

MAX_ORDER_SIZE_USDT defaults to 100 USDT. This caps the estimated notional value of a single order to guard against accidental large trades.

Does the server support the Bybit testnet?

Yes. Set TESTNET=true in the environment variables to use the Bybit testnet. Combine with TRADING_ENABLED=false for a fully read‑only test setup.

What API key permissions are needed?

Reading market data requires Read permission. Placing trades requires Trade permission. Checking wallet balances requires Wallet permission. IP restrictions are recommended.

What transport does the server use?

The server communicates over stdio. It is designed to be run as a subprocess by an MCP client (e.g., Claude Desktop) via the command line or Docker.

Comments

More Developer Tools MCP servers

Smithery CLI

smithery-ai

Install, manage and develop MCP servers and skills for agents

788

TalkToFigma

sonnylazuardi

TalkToFigma: MCP integration between AI Agent (Cursor, Claude Code, Codex) and Figma, allowing Agentic AI to communicate with Figma for reading designs and modifying them programmatically.

6.9K