Every product is a pair, and the execute half expects the exact contract the discover half returned — resources, path parameters, body schema. That removes the usual failure mode of an agent guessing at an API surface it has never seen. The mutation gate is the other thing worth noting: a write does not happen without confirmMutation and a written reason, so the audit trail records why, not just what. The two documented cross-product workflows, fetcher-to-reporter and matcher-to-fetcher-to-midaz, are where the portfolio framing actually pays off.
A gateway to the Lerian portfolio: Midaz the double-entry ledger, Fetcher for extraction, Reporter for templated reports, Matcher for reconciliation, Tracer for transaction validation, Flowker for workflow orchestration, and Underwriter for lending. Two core tools plus a discover-and-execute pair per product.
- One read-oriented entry point across the whole portfolio: discover which products exist and what is covered, look up official documentation, work through guided learning at beginner, intermediate or advanced level, generate SDK examples in Go, TypeScript or JavaScript for a named use case, and search across everything (lerian).
- A deliberate two-step for anything live: discovery returns the resources, actions, path and query parameters, body schemas, examples and execution hints, and execution takes the exact contract that came back (midaz-discover, midaz-execute).
- Ledger operations across organizations, ledgers, assets, accounts, transactions, balances, holders and aliases (midaz-discover, midaz-execute).
- Datasource connection, schema discovery and asynchronous extraction jobs, with the organizationId and productName context surfaced by discovery before you call (fetcher-discover, fetcher-execute).
- Template-driven reporting including multipart template upload, idempotency headers and binary report download (reporter-discover, reporter-execute).
- Reconciliation over contexts, sources, field maps, matching runs, exceptions, disputes, governance and reporting exports (matcher-discover, matcher-execute).
- Transaction validation with rules, limits, validation payloads and audit investigation filters (tracer-discover, tracer-execute).
- Workflow orchestration over definitions, execution starts requiring an Idempotency-Key, provider and executor configuration, webhooks and dashboard summaries (flowker-discover, flowker-execute).
- Jurisdiction-aware lending: loan product lifecycle actions and schedule previews, where decimal amounts are encoded as strings (underwriter-discover, underwriter-execute).
- Guided multi-product sequences with readiness planning, stateful sessions and step-by-step progression — the implemented ones being fetcher-to-reporter and matcher-to-fetcher-to-midaz (portfolio-workflow).
Nothing to read the documentation side: `npx -y @lerianstudio/lerian-mcp-server@latest` and the portfolio tool works. The execute tools reach whatever Lerian APIs you have configured, so live access depends on your own deployment — Underwriter's protected routes want bearer auth, Flowker's execution start wants an Idempotency-Key, and Reporter's template upload is multipart. Any mutating call additionally requires confirmMutation set to true and a human-readable mutationReason.
One command — npx -y @lerianstudio/lerian-mcp-server@latest