Build

MCP Setup

Install the Lev MCP server in your AI client, sign in through Auth0, and verify the connection with a read-only call before you build workflows.

Updated April 2026

Before You Start

You need:

  • A Lev account with access to the data you plan to query. MCP tools inherit your existing Lev permissions.
  • An MCP-compatible client: Claude Code, Claude Desktop, Cursor, or another client that supports streamable HTTP and OAuth.
  • A browser reachable from the machine running the client — the Auth0 sign-in flow opens in your default browser.
Service-to-service integrations

If you are building a backend sync job or a headless service, use the REST API with an API key instead of MCP. MCP is designed for interactive clients.

Environments

Install in Your Client

Coming soon

Client-specific install instructions for Claude Code, Claude Desktop, Cursor, and other MCP clients will be published here when the Lev MCP server is generally available. Reach out to your Lev contact for early access.

Sign In with Auth0

The first tool call against the MCP server triggers an OAuth sign-in flow backed by Auth0:

  1. The client discovers the authorization server from <mcp-server-url>/.well-known/oauth-authorization-server.
  2. Your default browser opens to the Auth0 hosted sign-in page.
  3. After you authenticate, Auth0 redirects back to the client with an authorization code.
  4. The client exchanges the code for an access token (an RS256-signed JWT) and stores it.
  5. Subsequent tool calls reuse the JWT until it expires, at which point the client silently refreshes.

You do not need to set Authorization headers or manage tokens yourself — the client handles both sides of the flow. For the token lifecycle, scopes, and account switching, see MCP Authentication.

Validate the Connection

Before you build anything meaningful, verify the install with three bounded checks. Your client should accept these as natural-language prompts.

  1. Confirm identity and account. Ask: "Use the Lev MCP server to get my profile." The client should call get_my_profile and return your email, user ID, and available accounts.
  2. Confirm a read tool works. Ask: "List my first five deals in Lev." The client should call list_deals with limit=5.
  3. Confirm the tool catalog looks right. Ask the client to list the Lev MCP tools it has discovered. You should see 27 tools at launch across deals, contacts, companies, lenders, placements, pipelines, term sheets, market data, and account. Three additional lender-discovery tools (search_lenders_for_deal, get_lender_search_results, search_lender_directory) are documented but not yet live.

If any of the three fail, jump to Troubleshoot before retrying.

Troubleshoot

Next steps
More in this section
MCP Authentication
Details on the OAuth flow the Lev MCP server uses, which scopes are granted, how tokens are refreshed, and how to switch between accounts during a session.
MCP Errors & Limits
Reference for error conventions, rate limits, circuit-breaker behavior, request tracing, and known gaps in the Lev MCP server.
MCP Overview
Understand the Lev MCP server — its purpose, architecture, supported tools, and where it fits relative to the Lev External API v2.
MCP Tools
Complete catalog of the tools exposed by the Lev MCP server, including read/write classification, parameters, response shape, and links to the matching REST reference. Covers the 27 tools live at launch plus 3 lender-discovery tools coming soon.