@stablecoinxyz
Basic information
MCP Server for Brale API -
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
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.
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.
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.
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.
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.
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.
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`.
Agent-Native Terminal
MCP-first toolbox for agents: namespaced key-value storage, a FIFO queue, auth, and a handful of stateless utility tools (JWT decode, hashing, cert inspection, CIDR math). Free while in early access. This repository is a
DrUrls audits websites for SEO, and its MCP server lets Claude, ChatGPT, Claude Code, Cursor or VS Code work with those audits directly: list your sites with their latest score and grade, read each issue across SEO, perf
Catch intent conflicts before code conflicts. The open-source coordination protocol for coding agents, built above Git.
Leadpages MCP is a remote MCP server available at https://mcp.leadpages.com.
Comments