leaseclear-mcp
A Model Context Protocol server that exposes LeaseClear lease Q&A.
Listed in the official MCP Registry as io.github.amadeuserras/leaseclear-mcp.
Tools
lease_qa— ask one question about lease terms; returns an answer grounded in the lease, or states that the lease is silent
Usage
Add this to your MCP client config (e.g. claude_desktop_config.json or Cursor mcp.json):
{
"mcpServers": {
"lease-qa": {
"command": "uvx",
"args": ["leaseclear-mcp"]
}
}
}
The package is on PyPI. uvx fetches and runs it as a local subprocess, communicating over stdio. uv required.
Optional environment variables
| Variable | Description | Default |
|---|---|---|
LEASECLEAR_API_KEY |
Use the server with your own LeaseClear account | LeaseClear demo mode |
LEASECLEAR_API_URL |
Override the API endpoint (local or private instances) | LeaseClear production backend |
{
"mcpServers": {
"lease-qa": {
"command": "uvx",
"args": ["leaseclear-mcp"],
"env": {
"LEASECLEAR_API_KEY": "lc_...",
"LEASECLEAR_API_URL": "https://..."
}
}
}
}
lease_qa usage
Argument
question(string, required) — one question about the lease
_meta
document_ids(string[], optional) — UUIDs of the documents to query. Omitted means all.
Security: The _meta field is used to pass metadata to the tool call that the model doesn't see. Having document_ids there is intentional: it prevents cross-document prompt injection because the model is never able to choose which documents it has access to. See a real-world example in LeaseOps: prompt injection and the tenants table.
MCP Python SDK example
Tool call:
result = await session.call_tool(
name="lease_qa",
arguments={
"question": "How much is the security deposit for Yuna Kim?"
},
meta={
"document_ids": [
"a1b2c3d4-e5f..."
]
}
)
Output:
{
"answer": "The security deposit is $6,400.00. This deposit is held in Owner's Broker's trust account [california-johnson-kim §4]."
}
Project structure
leaseclear-mcp/
├── src/leaseclear_mcp/
│ ├── server.py # MCP server + lease_qa
│ ├── leaseclear.py # LeaseClear HTTP client
│ ├── schemas.py
│ └── config.py
├── tests/
├── pyproject.toml
├── .env.example
└── README.md
Local Development
git clone https://github.com/you/leaseclear-mcp.git
cd leaseclear-mcp
uv sync
cp .env.example .env
uv run pytest
uv run ruff check .
uv run pyright
Debugging
Use the MCP Inspector to test the server interactively:
npx @modelcontextprotocol/inspector uvx leaseclear-mcp
From a checkout, use uv run leaseclear-mcp instead of uvx leaseclear-mcp.
License
MIT
Metadata
Release files for leaseclear-mcp 0.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| leaseclear_mcp-0.1.3.tar.gz | 5.2 kB | Without provenance | Details for leaseclear_mcp-0.1.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| leaseclear_mcp-0.1.3-py3-none-any.whl | Python 3 | none | any | Details for leaseclear_mcp-0.1.3-py3-none-any.whl |
Total release size: 12.5 kB
Release files / leaseclear_mcp-0.1.3.tar.gz
| Download URL | leaseclear_mcp-0.1.3.tar.gz |
|---|---|
| Size | 5.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b59b384da73fbcc72023488999ddc4fe82015c2a088a182e215f03f43871d61b
|
|
BLAKE2b-256 checksum How to use checksums |
7681f99646977afb8dfcc1826d1ddfd171694a1f9b2ab1854d2f0b85b1e5d146
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.21 {"installer":{"name":"uv","version":"0.11.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / leaseclear_mcp-0.1.3-py3-none-any.whl
| Download URL | leaseclear_mcp-0.1.3-py3-none-any.whl |
|---|---|
| Size | 7.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
23a9a58f29c92c29e6b5a069374978353e2883014bbcf7ff9ff5899134f73b45
|
|
BLAKE2b-256 checksum How to use checksums |
881d7e85a8dfdca28f717bc5d9c8bfce25abaf745e745065a78d4e9388ecd4de
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.21 {"installer":{"name":"uv","version":"0.11.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for leaseclear-mcp 0.1.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.