Lerian MCP Server

Lerian MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. A Model Context Protocol (MCP) server for Lerian portfolio discovery, documentation, learning, SDK examples, live product API discovery/execution, and cross-product workflows.

What you get

This server connects MCP clients such as Claude Desktop, Cursor, Windsurf, Continue, and ChatGPT Desktop to the Lerian product portfolio. It gives AI assistants a structured way to discover Lerian products, read official documentation, generate implementation examples, inspect live API contracts, execute configured product APIs, and guide multi-product operational workflows.

What the assistant can call

Once Lerian is connected, these are the calls the assistant has available:

• 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 — discover and midaz-execute
• fetcher — discover and fetcher-execute
• reporter — discover and reporter-execute
• matcher — discover and matcher-execute
• tracer — discover and tracer-execute
• flowker — discover and flowker-execute
• underwriter — discover and underwriter-execute
• confirmMutation — true

Setting it up

The server ships on npm as @lerianstudio/lerian-mcp-server, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Configuration and credentials

You will need 8 environment variables: LERIAN_DOCS_URL, MIDAZ_ONBOARDING_URL, MIDAZ_TRANSACTION_URL, MIDAZ_CRM_URL, MIDAZ_LEDGER_URL, MIDAZ_AUTH_TOKEN, FETCHER_MANAGER_URL, FETCHER_AUTH_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Lerian's toolset — lerian, portfolio-workflow, midaz and 7 more — is a fair guide to whether it matches your workflow. It is maintained by LerianStudio; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 10 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Lerian.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the lerian mcp server does with a few real requests.