What MCP Is
The Model Context Protocol is an open standard for connecting AI clients to external tools and data. An MCP server advertises a set of tools (callable functions) and resources (read-only data) to any compliant client. The client handles authentication, tool discovery, and human review; the server handles the business logic.
What the Lev MCP Server Does
The Lev MCP server is a thin, opinionated translation layer on top of the Lev API:
- It authenticates users through Auth0, not through static API keys. Each user sees the data their Lev account permits.
- It registers 63 tools across deals (including checklists and Office generation for PowerPoint, Word, and Excel), documents, vaults, contacts, companies, notes, lenders, placements, pipelines, term sheets, market data, billing, and account context.
- It returns JSON strings tuned for LLM consumption — list tools wrap results with
total,showing, andhas_more; detail tools return a single resource. - It translates errors into human-readable strings so models can surface the cause to the user without parsing HTTP envelopes.
It is not a replacement for the REST API. Most tools ultimately call /api/external/v2/* on lev-backend. Office generation tools start a Cortex agent run instead.
Architecture
MCP Client (Claude, Cursor, …)
│ Streamable HTTP (POST /mcp)
▼
Lev MCP Server (FastMCP, Python)
├── Auth0 JWT verification (RS256, JWKS)
├── Tool registry (63 tools across 12 groups)
└── Async API client (retries, circuit breaker)
│ Authorization: Bearer <jwt>
│ X-Origin-App: mcp
▼
Lev API- Transport. Streamable HTTP. No stdio, no SSE — one persistent connection per session.
- Runtime. Python, FastMCP, gunicorn + uvicorn workers in production.
- Reliability. A circuit breaker trips after 5 consecutive 5xx responses with a 30-second cooldown. 429s do not trip the breaker — rate limits are expected, not outages.
- Observability. Every tool call forwards an
X-Request-Idto lev-backend. AGET /healthendpoint reports version, upstream API reachability, and circuit-breaker state.
When to Use MCP
The Lev MCP server expects a live user session. Do not point headless services at it — use an API key against the REST API instead.
What's in the Box
- Deals — search, read, create, update, delete, move through pipelines, search indexed source-backed facts (including
sidebarNodeIdfor Index citations), and generate PowerPoint presentations, Word credit memos, and Excel underwriting models. - Documents and vaults — browse a deal's Deal Rooms and Resources, and list, open, and download uploaded files.
- Checklists — read Deal Room checklist sections, tasks, assignees, expected document types, and task-linked files.
- Lender matching — run Lev's AI lender match for a deal, read the ranked lenders with their match scores and loan programs, and reveal a matched lender contact's details. You can also look up a lender by name with
search_lendersor by id withget_lender. - CRM — contacts and companies with full CRUD.
- Notes — read, create, update, and delete free-text notes on deals and contacts.
- Placements and term sheets — open and advance lender outreach, record and revise quotes, and read the resulting state.
- Market data — current SOFR, Prime, Treasury rates; asset type classifications.
- Billing — subscription state and credit balance for the active account.
- Account — profile, available accounts, team members, and live account switching.
For the full catalog with parameters and return shapes, see MCP Tools.