Bring Geospatial Intelligence
to Cursor
Learn how to connect LandTech to Cursor 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 Cursor?
Cursor's Agent mode turns LandTech into an in-editor superpower. Ask Cursor to generate code using live data from LandTech and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
LandTech in Cursor
LandTech and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect LandTech to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
