Lerian MCP Server
@LerianStudio
A MCP server to support all Lerian's platforms. Enables AI assistants to interact with Midaz's core banking APIs for automated ledger operations, account management, and transaction processing. Features comprehensive API coverage, real-time data access, and robust error handling
Overview
What is Lerian MCP Server?
Lerian MCP Server is an MCP gateway that connects AI assistants to the Lerian product portfolio for discovery, documentation, guided learning, SDK examples, live API contract inspection, and cross-product workflow execution. It supports MCP clients such as Claude Desktop, Cursor, Windsurf, Continue, and ChatGPT Desktop.
How to use Lerian MCP Server?
Install via the npx command and add the provided JSON configuration block to your MCP client’s settings file. Restart the client and ask a question like “What can you tell me about Lerian Midaz?”. For live API execution, configure base URLs, authentication tokens, or API keys through environment variables or a config file (created interactively with npx -y -p @lerianstudio/lerian-mcp-server@latest lerian-mcp-config).
Key features of Lerian MCP Server
- Unified portfolio discovery and documentation lookup
- Guided learning with topic and experience level
- SDK examples in Go, TypeScript, and JavaScript
- Live API contract discovery and safe execution
- Cross-product workflow planning and step execution
- Two-step mutation safety with confirmation and audit reason
Use cases of Lerian MCP Server
- Discover all Lerian products and their capabilities
- Learn a product feature like Tracer validation rules
- Generate Go code to create a Midaz ledger
- Inspect the Reporter API contract before creating a template
- Walk through validating Fetcher mappings before generating a report
FAQ from Lerian MCP Server
What MCP clients are supported?
The server works with Claude Desktop, Cursor, Windsurf, Continue, and ChatGPT Desktop.
Does Lerian MCP Server require API keys or tokens?
Documentation and discovery work immediately. Live API execution requires reachable product services and applicable tokens or API keys, configured via environment variables or config files.
How do I configure live API access?
Set environment variables like MIDAZ_AUTH_TOKEN and product base URLs, or run the interactive config command. Configuration is loaded from command-line flags, environment variables, or multiple config file paths in priority order.
Is there a safety model for mutations?
Yes. Mutating live API calls require confirmMutation: true and a mutationReason with a human-readable audit reason. Non-localhost HTTP URLs are rejected; HTTPS is required outside local development.
