Levr MCP lets a compatible AI assistant work with the access you already have in Levr. MCP access is included with your Levr account. For your own CRM or background automation, use the REST API instead.
Connect to your Levr account
Add a remote MCP connection in your AI client with the full server URL https://mcp.levr.ai/mcp. The transport is Streamable HTTP.
Choose OAuth and complete the Levr browser sign-in. Use the default OAuth client setup. Do not enter a REST API key, invent a client secret, or use the REST API base URL as the MCP server.
Install or enable the connection in your client, select it for the conversation if required, and start a new chat.
Ask: “List the Levr Portals I can access. Do not change anything.” A successful read verifies the connection. A saved URL or completed sign-in alone does not prove a tool call worked. An empty list can mean the account has no Portal access.
See the current client setup guide for ChatGPT, Claude, Codex, Claude Code, Cursor, VS Code and Gemini CLI. Client labels and plan availability can change. A workspace administrator may need to permit custom connections. Hosted clients need a reachable HTTPS server.
What can it do?
Depending on your permissions and the tools your connection exposes, an assistant can work with businesses, people, Projects, funding matches, Deals and applications. Give it a specific goal and state whether you want it to read, prepare or submit. The Connect control on a business, Project or Deal provides record-specific instructions.
Discover the current tools from the connected server. Do not infer MCP tool names from REST endpoints or assume every account has every tool. Application editors require specific grants. Before a write or submission, read current state and follow the tool’s validation, revision and confirmation requirements. Lender matching, creating a Deal and submitting an application are separate steps.
If the connection fails
If custom connection controls are missing, check your client plan and workspace policy. For sign-in or discovery failures, confirm the complete URL and intended environment, then reconnect. For missing Portals or tools, check which Levr account signed in and what it can access.
If you see “Structured content does not match the tool’s output schema”, the client may have an old tool definition. Refresh the connection’s tools after the server update is available and start a new conversation. If the failed call changed settings or submitted data, check the actual record before retrying because the action may already have completed.
Contact support@levr.ai or use chat if the problem continues. Share the client name, server URL, approximate time and redacted error. Never send passwords, authorization codes, tokens or API keys. You can review or revoke the connection in Levr Account settings → Security → Connected MCP apps.
Levr MCP and the public BusinessLoanBroker.ai sandbox are different
The authenticated Levr server at https://mcp.levr.ai/mcp can work with real records your account is allowed to access. The public BusinessLoanBroker.ai sandbox at https://sandbox.businessloanbroker.ai/mcp is for fictional test data and cannot submit real loan applications. Business owners applying for financing should use the secure application portal. Do not put real client or financial information in the public sandbox.
When should I use the API instead?
Choose REST and webhooks for systems that run automatically with a scoped Portal API key. Choose MCP for an assistant acting with your signed-in user permissions. These are different authentication methods.