Bitpin MCP Server

Connect Bitpin to Claude, Cursor or any other MCP client and it stops being a tab you switch to. This repository provides an MCP server implementation for the Bitpin cryptocurrency exchange. The server exposes several tools for interacting with the Bitpin API, such as retrieving wallet balances, market data, order details, and. The bitpin mcp server is what makes that connection.

What the server does

• GetWalletsListAsync — Retrieve a list of wallet balances for various cryptocurrencies
• GetMarketsListAsync — Retrieve a list of all supported trading markets
• GetTickersListAsync — Retrieve the current price list of Bitpin's markets
• GetCurrenciesAsync — Retrieve a list of supported cryptocurrencies with details such as symbol, name, and tradability status
• GetOrderbooksAsync — Retrieve the open orders in a specific trading market
• GetMatchesAsync — Retrieve the latest executed trades for a specific market

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• GetWalletsListAsync — Retrieve a list of wallet balances for various cryptocurrencies
• GetMarketsListAsync — Retrieve a list of all supported trading markets
• GetTickersListAsync — Retrieve the current price list of Bitpin's markets
• GetCurrenciesAsync — Retrieve a list of supported cryptocurrencies with details such as symbol, name, and tradability status
• GetOrderbooksAsync — Retrieve the open orders in a specific trading market
• GetMatchesAsync — Retrieve the latest executed trades for a specific market
• CreateLimitOrderAsync — Place a limit order to buy or sell a cryptocurrency at a specified price
• CreateMarketOrderAsync — Place a market order to instantly buy or sell at the best available price
• CreateStopLimitOrderAsync — Place a stop-limit order to buy or sell once a specific stop price is reached
• CreateOcoOrderAsync — Place an OCO (One Cancels the Other) order to manage both limit and stop-limit orders simultaneously
• GetOrdersAsync — Retrieve your list of orders
• GetCompeletedOrdersAsync — Retrieve details of your completed orders (executed trades)

Credentials and setup notes

Configuration is passed through the environment: BITPIN_API_KEY, BITPIN_API_SECRET, BITPIN_API_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• .NET 9 or higher - The BitpinClient NuGet package - Access to the Bitpin API (API Key and Secret)

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Bitpin's toolset — GetWalletsListAsync, GetMarketsListAsync, GetTickersListAsync and 11 more — is a fair guide to whether it matches your workflow. It is maintained by Kamyab7; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Bitpin.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.