The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Leaseclear MCP listing page.
A Model Context Protocol server that exposes LeaseClear lease Q&A.
Listed in the official MCP Registry as io.github.amadeuserras/leaseclear-mcp.
lease_qa — ask one question about lease terms; returns an answer grounded in the lease, or states that the lease is silentAdd this to your MCP client config (e.g. claude_desktop_config.json or Cursor mcp.json):
The package is on PyPI. uvx fetches and runs it as a local subprocess, communicating over stdio. uv required.
| 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 |
lease_qa usageArgument
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.
Tool call:
Output:
mcp[cli]) over stdiohttpx for LeaseClear API callspydantic-settings for schemas and configuv and uv_build for running and packagingUse the MCP Inspector to test the server interactively:
From a checkout, use uv run leaseclear-mcp instead of uvx leaseclear-mcp.
MIT