# leaseclear-mcp [Health: Active]

**Category:** 🏠 Real Estate  
**Repository:** https://github.com/amadeuserras/leaseclear-mcp  
**GitHub Stars:** 0  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/leaseclear-mcp

## Description
An MCP server that exposes LeaseClear

## Tools
Capabilities this server exposes over MCP:

- **lease_qa** — 
    Ask one neutral, precise question about lease terms. Returns an answer grounded
    in the lease, or states that the lease does not address the question.
    

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "leaseclear-mcp": {
    "command": "uvx",
    "args": ["leaseclear-mcp"]
  }
}
```

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/leaseclear-mcp/readme_