Bring Geospatial Intelligence
to LlamaIndex
Learn how to connect LandTech to LlamaIndex and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the LandTech MCP Server?
Connect your LandTech account to any AI agent and access property intelligence through natural conversation.
What you can do
- Land Search — Search parcels by location, size, and zoning criteria
- Ownership Analysis — Browse ownership records and title information
- Planning Applications — Track planning permissions and application status
- Site Assessment — Access environmental, flood risk, and constraint data
- Development Tracking — Monitor construction activity and project pipelines
How it works
1. Subscribe to this server
2. Enter your LandTech API Key
3. Start searching properties from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Property Developers — search for development sites and track planning
- Estate Agents — access land data and ownership information
- Planners — monitor applications and constraints
Built-in capabilities (12)
Check connection
Get property-level info
Get property title info
Get planning info
Get policy details
Find similar sales
Get regional insights
Check development risks
List regional policies
List portfolio sites
Find land for development
Find planning applications
Why LlamaIndex?
LlamaIndex agents combine LandTech tool responses with indexed documents for comprehensive, grounded answers. Connect 12 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.
- —
Data-first architecture: LlamaIndex agents combine LandTech tool responses with indexed documents for comprehensive, grounded answers
- —
Query pipeline framework lets you chain LandTech tool calls with transformations, filters, and re-rankers in a typed pipeline
- —
Multi-source reasoning: agents can query LandTech, a vector store, and a SQL database in a single turn and synthesize results
- —
Observability integrations show exactly what LandTech tools were called, what data was returned, and how it influenced the final answer
LandTech in LlamaIndex
LandTech and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect LandTech to LlamaIndex through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for LandTech in LlamaIndex
The LandTech MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in LlamaIndex only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
LandTech for LlamaIndex
Every tool call from LlamaIndex to the LandTech MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I search for land parcels and development sites?
Yes. Search parcels by location, size, zoning, and constraints. Results include ownership, planning history, and environmental data.
How does LandTech authentication work?
LandTech uses a custom X-API-Key header (not Bearer) for all requests against app.land.tech/api.
Can I track planning applications?
Yes. Browse planning applications with status, decision dates, and details. Monitor new submissions and decisions in any area.
How does LlamaIndex connect to MCP servers?
Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
Can I combine MCP tools with vector stores?
Yes. LlamaIndex agents can query LandTech tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
Does LlamaIndex support async MCP calls?
Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.
BasicMCPClient not found
Install: pip install llama-index-tools-mcp