Lerian MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Set the logging level (e.g., debug) | |
| ERROR_LOGGING | No | Enable error logging (logs stored in ./logs/ directory) | |
| LERIAN_DOCS_URL | No | Custom documentation URL for Lerian products | |
| PERFORMANCE_TRACKING | No | Enable performance tracking (logs stored in ./logs/ directory) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lerianA | Unified 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. |
| portfolio-workflowA | Cross-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. |
| midaz-discoverA | Discover 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-executeA | Execute 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. |
| fetcher-discoverA | Discover 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-executeA | Execute 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. |
| reporter-discoverA | Discover 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-executeA | Execute 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. |
| matcher-discoverA | Discover 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-executeA | Execute 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. |
| tracer-discoverA | Discover 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-executeB | Execute Tracer API actions. Use tracer-discover first to inspect rule/limit transitions, validation request bodies, audit filters, and operational endpoints before calling this tool. |
| flowker-discoverA | Discover 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-executeA | Execute 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. |
| underwriter-discoverA | Discover 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-executeA | Execute 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| help-me-start | Show me what I can do with this Lerian MCP server and how to get started quickly |
| help-with-api | Show me how to use the live product API tools in this MCP server |
| help-me-learn | Get personalized Lerian learning guidance based on your role and experience |
| create-transaction-wizard | Guide me through creating a transaction step by step with my actual Midaz data |
| debug-my-balance | Help me understand and troubleshoot balance issues with my accounts |
| setup-my-org | Guide me through setting up a new organization with ledgers, accounts, and initial configuration |
| explain-my-data | Help me understand my current Midaz data, balances, and transaction patterns |
| check-file-balances | Analyze CSV, TXT, or JSON files to find account UUIDs and check their balances in Midaz |
| check-external-balance | Check the balance of external accounts for specific assets in Midaz ledgers |
| discover-midaz-hierarchy | Explore the complete Midaz hierarchy: organizations → ledgers → assets → accounts → portfolios |
| show-all-tools | Display the current Lerian MCP tool catalog, prompt surface, and recommended entry points |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Each product-specific tool clearly targets a distinct product, and the discover/execute split is unambiguous. The two meta tools (lerian and portfolio-workflow) serve separate discovery and cross-product workflow purposes, so there is no overlap or confusion between any tools.
The 14 product tools follow a highly consistent <product>-discover/<product>-execute pattern. However, the 'lerian' and 'portfolio-workflow' tools deviate from this convention, introducing a minor inconsistency that prevents a perfect score.
With 16 tools, the count is slightly above the typical 3-15 range, but every tool is necessary to cover seven distinct products, each requiring discovery and execution, plus two meta tools. The size is justified by the multi-product scope.
The tool set provides complete coverage for each product with both discovery and execution capabilities, including full CRUD operations. The addition of a unified documentation tool and a cross-product workflow tool ensures no dead ends and covers the entire lifecycle from exploration to execution.