MCP Setup

Before you start

• 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, Claude.ai, Cursor, VS Code, 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.

Environments

Pick the right endpoint for where you are in the build.

1. Install in your client

   Register the Lev MCP server with your client so the tools show up in its catalog.

   ClaudeChatGPTClaude CodeCursorVS CodeOther

   In Claude Desktop or claude.ai, open Settings → Connectors → Add custom connector. Fill in the fields below, click Add, then sign in when the browser opens.

   Connector detailsCopy

   Name:             Lev
   URL:              https://mcp.lev.com/mcp
   OAuth Client ID:  FPVfGZHwa9wvqhLwmXiaZyJPEjnaVAZB

   The first tool call triggers an OAuth sign-in flow backed by Auth0 — see MCP Authentication for the full token lifecycle.

   The Lev server appears in your client's MCP integrations list once the config is saved and the client is restarted.
2. Sign in with Auth0

   Complete an OAuth sign-in so the client holds a JWT it can send with every tool call.

   1. Trigger the first tool call. The client discovers the authorization server from <mcp-server-url>/.well-known/oauth-authorization-server.
   2. Sign in on the Auth0 page. Your default browser opens to the Auth0 hosted sign-in — complete authentication there.
   3. Let the client exchange the code. Auth0 redirects back with an authorization code; the client exchanges it for an RS256-signed JWT and stores it securely.
   4. Reuse the token automatically. Subsequent tool calls reuse the JWT until it expires, then the client silently refreshes — you never set Authorization headers yourself.

   For the token lifecycle, scopes, and account switching, see MCP Authentication.

   You're back in the client with an active session — no visible authentication prompts on subsequent calls.
3. Validate the connection

   Run three bounded checks to prove the server is reachable, authenticated, and returning the right data before you trust it with real work.

   1. Confirm identity and account. Ask the client "Use the Lev MCP server to get my profile." — it 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." — it should call list_deals with limit=5 and return real data.
   3. Confirm the tool catalog looks right. Ask the client to list the Lev MCP tools it has discovered — you should see 30 live tools across deals, contacts, companies, lenders, placements, pipelines, term sheets, market data, billing, and account.

   Lender discovery tools (preview)

   Three additional lender-discovery tools (search_lenders_for_deal, get_lender_search_results, search_lender_directory) are documented but not yet live.

   All three prompts return account-aware replies. If any fail, jump to Troubleshoot before retrying.

Troubleshoot

Match the symptom you see to the matching row before retrying the validate checks.

Next: MCP Tools — explore the tool surface now that the connection is live.

Sharing this with a non-technical teammate? Send them the Lev MCP Quickstart — a one-pager with the install box and a few real prompts to try.