Log inSubmit server
Leaseclear MCP logo

Leaseclear MCP

Ask grounded questions about lease terms through LeaseClear using a single MCP tool.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Leaseclear MCP

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "leaseclear-mcp": {
      "command": "uvx",
      "args": [
        "leaseclear-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 1 tools correctly (3d ago).

Overview

The leaseclear-mcp MCP server connects MCP clients to LeaseClear lease Q&A through a local stdio process. Its lease_qa tool accepts one question and returns an answer grounded in the lease, or reports that the lease is silent. Optional metadata can restrict the query to specified document IDs without exposing those IDs to the model. Use it when an agent needs to retrieve answers from lease documents through LeaseClear.

Use cases

  • Ask an agent to find a specific lease term
  • Restrict questions to selected lease documents
  • Run lease Q&A from Claude Desktop or Cursor
  • Point lease queries at a private LeaseClear endpoint

Key features

  • Lease-term question answering
  • Grounded answers or silent-lease responses
  • Optional document ID filtering
  • Stdio MCP transport
  • Configurable LeaseClear API key and endpoint

Tools1

What Leaseclear MCP lets your agent do. Expand a tool for its parameters.

Verified live~76 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

5/5 checks healthy over the last 42d

What it can do

From the 1 tool this server returned when we ran it.

Read-only tools · 1
Network at startup2 connections
Files written at startupNone

Observed 2026-10-20 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 1d ago via OSV.dev · leaseclear-mcp (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

Last commit2mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed1Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Leaseclear MCP works

What leaseclear-mcp MCP server does

The leaseclear-mcp MCP server exposes LeaseClear lease Q&A to MCP-compatible clients. It provides one tool, lease_qa, for asking a single question about lease terms. The response is grounded in the available lease content and can state that the lease is silent when the requested information is not present.

This fits workflows where an AI client needs to answer questions such as security-deposit, rent, or other lease-term queries through LeaseClear. The server does not expose a broad collection of lease-management tools; its documented capability is question answering over lease documents.

How it works

The leaseclear-mcp MCP server runs as a local Python subprocess and communicates with the MCP client over stdio. The recommended launch command uses uvx, which retrieves and runs the package from PyPI. The client sends a required question string to lease_qa.

Document selection is passed through MCP call metadata rather than the visible tool arguments. The optional document_ids metadata value is an array of document UUIDs. If it is omitted, the query covers all documents available to the server. Keeping document IDs in metadata prevents the model from selecting which documents it can access, according to the project’s documented security rationale.

LeaseClear requests are made through the project’s HTTP client. The default target is the LeaseClear production backend, with an option to point the server at a local or private endpoint.

Setup and configuration

Add an MCP server entry to the client configuration, using uvx leaseclear-mcp as the command and argument. The uv tool must be installed on the host. The README gives examples for Claude Desktop and Cursor configuration files.

By default, the package runs in LeaseClear demo mode. Set LEASECLEAR_API_KEY to use an account-specific LeaseClear key. Set LEASECLEAR_API_URL when the API endpoint needs to be changed, such as for a local or private instance. Neither variable is required for the documented default setup.

For local development, the repository uses uv sync, a .env file copied from .env.example, and checks with pytest, Ruff, and Pyright. The MCP Inspector can launch the package for interactive testing.

Tools and capabilities

  • lease_qa: accepts one required question string about lease terms.
  • Returns an answer grounded in the lease or indicates that the lease does not address the question.
  • Supports optional document_ids metadata to constrain the documents queried.
  • Uses LeaseClear through an HTTP API, with configurable authentication and endpoint settings.

Limitations and notes

The documented interface contains only one MCP tool, so each call asks one lease question rather than submitting a batch of questions. Answers depend on the lease documents available to LeaseClear. If the relevant term is absent, the tool reports that the lease is silent rather than supplying an unsupported answer.

The server uses stdio transport in the provided configuration. A LeaseClear API key is optional for demo mode but is needed when using an account-specific LeaseClear setup. The project is licensed under MIT.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Leaseclear MCP

leaseclear-mcp is an MCP server that connects AI clients to LeaseClear lease Q&A through a local stdio process. Its main tool, lease_qa, accepts one lease-term question and returns an answer grounded in the lease or says the lease is silent. Optional document IDs can limit queried documents.

Run it with `uvx leaseclear-mcp` after installing `uv`. Add that command and argument to your MCP client configuration; `uvx` fetches and runs the PyPI package as a local stdio subprocess.

Yes, leaseclear-mcp works with Cursor through its `mcp.json` configuration. Define a server using the `uvx` command and `leaseclear-mcp` argument, and optionally provide LeaseClear environment variables.

Pass document UUIDs in the MCP call metadata under `document_ids`. Omitting that metadata queries all available documents, while metadata-based selection keeps the document scope from being chosen by the model.

Set `LEASECLEAR_API_KEY` for an account-specific LeaseClear connection and `LEASECLEAR_API_URL` to override the default production endpoint. Without the key, the documented default is LeaseClear demo mode.

Related MCP servers

All in Real Estate All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewLeaseclear MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/leaseclear-mcp?style=directory)](https://allmcps.com/mcp/leaseclear-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/leaseclear-mcp"><img src="https://allmcps.com/api/badge/leaseclear-mcp?style=directory" alt="Leaseclear MCP on AllMCPs" /></a>