Bitso

You run a specialized MCP server that connects to the Bitso API to retrieve withdrawals and fundings data. It provides authenticated access, filtering and pagination, dual transport modes for production and development, and strong tooling to ensure reliability and developer experience.

How to use

You interact with the Bitso MCP Server through an MCP client. The server exposes tools to list and fetch withdrawals and fundings, with secure request signing and flexible filters. In production, you can run in stdio mode for Claude Desktop or in HTTP mode for development, and you can monitor behavior through structured logs.

How to install

Prerequisites you need on your machine:

Step-by-step commands you should run to set up and begin using the server:

npm install

cp .env.example .env

Edit the .env file to provide your Bitso API credentials.

npm run build

npm run start:http

For running in Claude Desktop (stdio transport), you can also start with this approach after building:

npm start

Or run the compiled entry point directly:

node dist/src/index.js

Additional setup and usage notes

Configure your Claude Desktop to connect to the MCP server in stdio mode by supplying the runtime command and environment variables. Example configuration shows the server name and how to pass API credentials.

Available tools

list_withdrawals

List withdrawals with optional filtering such as currency, limit, marker, method, origin_id, status, and wid.

get_withdrawal

Retrieve a single withdrawal by its unique ID (wid).

get_withdrawals_by_ids

Fetch multiple withdrawals by a comma-separated list of IDs (wids).

get_withdrawals_by_origin_ids

Retrieve withdrawals using origin IDs supplied by the client.

list_fundings

List fundings with optional filters such as limit, marker, method, status, and fids.

get_funding

Fetch a single funding by its ID (fid).