bitpin

This MCP server implementation for Bitpin exposes a suite of tools that let you interact with the Bitpin API to manage wallets, markets, orders, and trades. The tools include functionality to retrieve wallet balances, list markets and tickers, fetch currencies and order books, view matches (executed trades), and create or manage different order types such as limit, market, stop-limit, and OCO orders. Through the MCP server, you can programmatically access and automate trading workflows, query your orders, and monitor completed trades in a structured, standardized way. To use the server, configure the Bitpin API credentials and run the MCP service so the tools become available to your LLM or automation layer. The server is designed to be driven by the MCP infrastructure, exposing the Bitpin client-backed tools via the configured transport (STDIO in the example).

Prerequisites:\n- .NET 9 or higher\n- The BitpinClient NuGet package\n- Access to the Bitpin API (API Key and Secret)\n\nStep-by-step installation:\n1) Install .NET 9+ SDK on your machine. Verify with:\nbash\ndotnet --version\n\n2) Create a new project or open your Bitpin MCP server project. Ensure the project references the BitpinClient package, for example:\nxml\n<PackageReference Include=\"BitpinClient\" Version=\"X.Y.Z\" />\n\n3) Obtain Bitpin API credentials (API Key and Secret) and place them securely, either in environment variables or in a configuration file.\n4) Add MCP server configuration to your application settings as shown in the README example.\n5) Build and run the MCP server.\nbash\ndotnet build\ndotnet run --project path/to/your/MCPServer.csproj\n

Tips and notes:\n- Ensure your Bitpin API credentials are kept secure and not committed to version control. Use environment variables or a secrets manager.\n- The MCP server configuration shown uses STDIO transport with a single BitpinExchange server entry. You can adapt the command and environment variables to your deployment environment.\n- If you run tests or perform live trading, be mindful of API rate limits and the risks associated with real orders. Some tests that create real orders may be ignored or should be executed with caution.\n- Environment variables in the config (BITPIN_API_KEY, BITPIN_API_SECRET, BITPIN_API_URL) map to the BitpinClient settings used in code.\n- If you switch to a different transport or hosting environment, update the mcpServers entry accordingly (e.g., Docker, node, or python transports).