Brale API MCP Server

What is Brale API MCP Server?

The Brale API MCP Server is a Model Context Protocol server that provides a secure wrapper around the Brale API for stablecoin issuance and orchestration operations. It enables AI assistants to interact with Brale API endpoints for account management, transfers, address management, and configuration, supporting both Bearer token and OAuth2 client credentials authentication. It is built with TypeScript and Zod validation and includes comprehensive error handling.

How to use Brale API MCP Server?

Clone the repository, install dependencies with npm install, and create a .env file with your Brale API credentials (BRALE_CLIENT_ID and BRALE_CLIENT_SECRET). Run the server in production with npm start or in development with npm run dev. Before using any Brale endpoints, configure authentication using the brale_auto_configure tool (for OAuth2 using environment variables) or brale_configure tool (for manual bearer token or client credentials). Then use tools such as brale_get_accounts, brale_get_transfers, brale_create_account, brale_create_transfer, brale_get_automations, and others to interact with Brale API.

Key features of Brale API MCP Server

• Secure authentication via Bearer token and OAuth2 client credentials
• Type-safe with TypeScript and Zod validation
• Comprehensive error handling with meaningful messages
• Runtime configuration of API credentials
• Focus on read-only operations for safe data retrieval
• Auto token refresh with 5-minute buffer for OAuth2

Use cases of Brale API MCP Server

• AI assistant retrieving account details and balances for stablecoin accounts
• Automating transfer creation between accounts, addresses, or financial institutions
• Managing external financial institutions (bank accounts) for ACH/wire transfers
• Setting up automated deposit addresses or onramps via automations
• Creating new customer accounts with KYB details for stablecoin issuance

FAQ from Brale API MCP Server

What authentication methods does the server support?

The server supports OAuth2 client credentials (recommended) and Bearer token authentication. OAuth2 is configured via environment variables and automatically handles token refresh. Bearer tokens can be provided manually using the brale_configure tool.

Is the server limited to read-only operations?

The README states the server focuses on read-only operations for safety, but it also provides tools for creating accounts (brale_create_account), transfers (brale_create_transfer), external addresses, financial institutions, and automations, so it supports both read and write operations.

How do I configure the server with environment variables?

Set BRALE_CLIENT_ID and BRALE_CLIENT_SECRET in a .env file, then use the brale_auto_configure tool (optionally with a custom base URL) to automatically configure authentication. The server will obtain and manage OAuth2 tokens.

What debugging tools are available?

The server includes file-based logging to mcp-debug.log in development, MCP Inspector for interactive testing (npm run inspector), and real-time log viewing with npm run logs. Production mode runs without logging overhead.

What dependencies are required to run the server?

Node.js and npm are required. The project uses tsx to run TypeScript directly without a build step. All dependencies are installed via npm install.