MCP SERVER · OFFICIAL PROJECTOne gateway to seven Lerian products — read the docs, generate SDK examples, inspect a live API contract, then execute against it with a stated reason on the record.
LABSCO SUMMARY
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.
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
USE CASES
Read the documentation and work through guided learning at your own level before touching an API.
Generate an SDK example for your language and use case, then check it against the live contract.
Describe the action first to learn the required path parameters and body, then execute with a stated reason.
Run the fetcher-to-reporter workflow rather than wiring the two products together by hand.
Inspect the matching run and exception endpoints, then execute against the context and sources you configured.
Look at the rules and limits, then filter the audit investigation to the case in question.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
fetcher-discoverDiscover Fetcher manager resources, actions, and execution contracts. Use this before fetcher-execute to inspect path params, required headers like organizationId/productName, body shapes, and supported migration/fetcher job operations.
fetcher-executeExecute Fetcher manager API actions. Use fetcher-discover first to inspect the required organizationId/productName context, path params, query params, and request body shape before calling this tool.
flowker-discoverDiscover Flowker API resources, actions, and execution contracts. Use this before flowker-execute to inspect workflow definitions, execution start requirements, provider and executor configuration payloads, audit filters, dashboard summaries, and webhook method/path behavior.
flowker-executeExecute Flowker API actions. Use flowker-discover first to inspect auth expectations, Idempotency-Key requirements for workflow execution start, provider and executor configuration payloads, and webhook method/path behavior.
lerianUnified portfolio tool for Lerian products. Discover supported products and current MCP coverage, access documentation and learning resources, generate SDK examples, and search across the portfolio. Live API execution is available through product-specific tools for Midaz, Fetcher, Reporter, Matcher, Tracer, Flowker, and Underwriter, with cross-product workflow support available via portfolio-workflow.
matcher-discoverDiscover Matcher API resources, actions, and execution contracts. The current live slice covers contexts, sources, field maps, discovery-over-Fetcher endpoints, matching runs, exceptions, disputes, governance, reporting, and system operations. Use this before matcher-execute to inspect headers, path params, query filters, payload requirements, and export behavior.
matcher-executeExecute Matcher API actions. The current live slice covers contexts, sources, field maps, discovery-over-Fetcher endpoints, matching runs, exceptions, disputes, governance, reporting, and system operations. Use matcher-discover first to inspect payloads, required headers, and reporting export behavior.
midaz-discoverDiscover Midaz API resources, actions, and schemas. Use this BEFORE calling midaz-execute to find the right resource+action and understand required parameters. Supports listing all resources, describing specific resources/actions, searching, and filtering by component.
midaz-executeExecute Midaz API operations. Use midaz-discover first to find the right resource+action and required parameters, then call this tool to execute. Supports all CRUD operations across organizations, ledgers, assets, accounts, transactions, balances, holders, aliases, and more.
portfolio-workflowCross-product workflow tool for orchestrating guided steps across Lerian products. Supports workflow discovery, readiness planning, stateful workflow sessions, step execution, and execute-next progression. Implemented workflows include fetcher-to-reporter and matcher-to-fetcher-to-midaz.
reporter-discoverDiscover Reporter manager resources, actions, and execution contracts. Use this before reporter-execute to inspect multipart requirements for templates, request headers like X-Idempotency, report download behavior, and the available template/report/deadline/datasource endpoints.
reporter-executeExecute Reporter manager API actions. Use reporter-discover first to inspect multipart requirements for template upload/update, request headers like X-Idempotency, and binary download behavior for report artifacts.
tracer-discoverDiscover Tracer API resources, actions, and execution contracts. Use this before tracer-execute to inspect rule/limit operations, validation payloads, audit investigation filters, and operational endpoints.
tracer-executeExecute Tracer API actions. Use tracer-discover first to inspect rule/limit transitions, validation request bodies, audit filters, and operational endpoints before calling this tool.
underwriter-discoverDiscover Underwriter API resources, actions, and execution contracts. Use this before underwriter-execute to inspect jurisdiction discovery, loan product lifecycle actions, schedule preview payloads, and the example endpoints currently mounted by the service.
underwriter-executeExecute Underwriter API actions. Use underwriter-discover first to inspect bearer-auth requirements for protected routes, loan product path/query contracts, and the schedule preview payload where decimal amounts are encoded as strings.
BEFORE YOU INSTALL
16 tools when we connected. The *-execute tools call live APIs. The package is 3.7.1 while the documentation describes migrating to 4.0.0, so check version-specific settings.
npx on PATH
All 4 documented clients run the server on your machine.
CONTEXT COST
Rated by the size of the 16 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
npx -y @lerianstudio/lerian-mcp-server@latest{
"mcpServers": {
"lerian": {
"command": "npx",
"args": [
"-y",
"@lerianstudio/lerian-mcp-server@latest"
]
}
}
}MCP servers
j-about
freee
openaccountants