Lerian MCP Server

macOS location:~/Library/Application Support/Claude/claude_desktop_config.json

Windows location:%APPDATA%\Claude\claude_desktop_config.json

{ "mcpServers": { "lerian": { "command": "npx", "args": ["-y", "@lerianstudio/lerian-mcp-server@latest"] } } }

Cursor, Windsurf, Continue, ChatGPT Desktop

Add the same MCP server block to your client's MCP configuration:

{ "mcpServers": { "lerian": { "command": "npx", "args": ["-y", "@lerianstudio/lerian-mcp-server@latest"] } } }

- Midaz: unified double-entry ledger — organizations, ledgers, accounts, balances, transactions, and CRM behind a single service.
- Fetcher: datasource connection, schema discovery, and asynchronous extraction service.
- Reporter: template-driven report generation, datasource management, metrics, and artifacts.
- Matcher: reconciliation engine for matching Midaz transactions against external systems.
- Tracer: transaction validation engine with rules, limits, validations, and auditability.
- Flowker: workflow orchestration platform for providers, executors, webhooks, and execution flows.
- Underwriter: jurisdiction-aware lending surface for loan products and schedule preview.
- All: portfolio-wide discovery, documentation search, and comparison.

The server exposes a small core plus live API pairs for each supported product.

- lerian: unified portfolio tool for docs, learning, SDK examples, discovery, and search.
- portfolio-workflow: cross-product workflow discovery, planning, stateful sessions, and step execution.

- midaz-discoverandmidaz-execute
- fetcher-discoverandfetcher-execute
- reporter-discoverandreporter-execute
- matcher-discoverandmatcher-execute
- tracer-discoverandtracer-execute
- flowker-discoverandflowker-execute
- underwriter-discoverandunderwriter-execute

Theleriantool is the primary read-oriented entry point.

Tool: lerian Parameters: product midaz | fetcher | reporter | matcher | tracer | flowker | underwriter | all operation discover | docs | learn | sdk | search topic Topic to inspect, learn, or search language go | typescript | javascript, for SDK examples useCase Specific implementation scenario for SDK examples experienceLevel beginner | intermediate | advanced format summary | detailed | examples-only includeExamples true | false maxResults 1-50, for search

{ "product": "midaz", "operation": "learn", "topic": "transactions", "experienceLevel": "beginner" }

Live API access is intentionally two-step.

{ "intent": "list-resources" }

{ "intent": "describe-action", "resource": "transactions", "action": "create" }

- Execute with the exact contract returned by discovery:

{ "resource": "transactions", "action": "create", "pathParams": { "organizationId": "...", "ledgerId": "..." }, "body": { "description": "Example transaction" }, "confirmMutation": true, "mutationReason": "Create example transaction requested by operator" }

- confirmMutation: true
- mutationReasonwith a human-readable audit reason

Useportfolio-workflowwhen the task spans multiple Lerian products.

- fetcher-to-reporter: validate extraction mappings with Fetcher, then generate or inspect Reporter reports.
- matcher-to-fetcher-to-midaz: configure Matcher reconciliation, use Matcher discovery over Fetcher, and inspect Midaz ledger-side data.

- list-workflows
- describe-workflow
- plan
- create-session
- get-session
- list-sessions
- execute-step
- execute-next

Workflow sessions return an opaquesessionToken. Keep it private.

The server works immediately for documentation and discovery. Live API execution requires reachable product services and, where applicable, tokens or API keys.

Configuration sources, in priority order:

- Command-line--configor--config-file
- Environment variables
- ./lerian-mcp-config.json
- ./midaz-mcp-config.json
- ~/.lerian/mcp-config.json
- ~/.midaz/mcp-config.json
- ~/.config/lerian/mcp-config.json
- ~/.config/midaz/mcp-config.json
- Platform global config paths

Create or update configuration interactively:

npx -y -p @lerianstudio/lerian-mcp-server@latest lerian-mcp-config

Midaz is a single unified ledger service reached through one base URL. Onboarding, accounts, balances, transactions, and CRM are all resources of that one service, so there is exactly one Midaz URL to configure.

LERIAN_DOCS_URL=https://docs.lerian.studio LOG_LEVEL=info MIDAZ_BASE_URL=http://localhost:3002 MIDAZ_AUTH_TOKEN=... MIDAZ_API_TIMEOUT=30000 FETCHER_MANAGER_URL=http://localhost:4006 FETCHER_AUTH_TOKEN=... REPORTER_MANAGER_URL=http://localhost:4005 REPORTER_AUTH_TOKEN=... MATCHER_BASE_URL=http://localhost:4018 MATCHER_AUTH_TOKEN=... TRACER_BASE_URL=http://localhost:4020 TRACER_API_KEY=... FLOWKER_BASE_URL=http://localhost:4021 FLOWKER_AUTH_TOKEN=... FLOWKER_API_KEY=... UNDERWRITER_BASE_URL=http://localhost:8080 UNDERWRITER_AUTH_TOKEN=...

Breaking change: Midaz configuration. Releases before 4.0.0 expected four separate Midaz URLs, one per legacy service (onboarding, transaction, CRM, ledger). Those variables are gone — they are not read and not accepted. PointMIDAZ_BASE_URLat your unified Midaz ledger instead, and keepMIDAZ_AUTH_TOKENas is. Nothing else in the configuration changed.