Bring Strata Management
to Cursor
Learn how to connect Urbanise 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 Urbanise MCP Server?
Connect your Urbanise property management account to any AI agent and simplify how you coordinate building operations, financial records, and community engagement through natural conversation.
What you can do
- Property Management — List all property plans and retrieve detailed metadata for your managed ecosystem.
- Occupant & Strata Support — List residents and owners to manage communications and community directories.
- Maintenance Control — Create, list, and track maintenance jobs and facility tasks directly from your agent.
- Financial Visibility — Query ledger data, billing records, and property budgets to stay on top of your accounts.
- Supply Chain — List managed suppliers and service providers associated with your property plans.
- Asset Tracking — Monitor building equipment and infrastructure assets managed in the FM module.
How it works
1. Subscribe to this server
2. Enter your Urbanise Region, Client ID, and Access Token
3. Start managing your properties and facility maintenance from Claude, Cursor, or any MCP client
Who is this for?
- Property Managers — quickly retrieve occupant lists and verify property budgets via simple AI commands.
- Facility Managers — schedule maintenance jobs and track asset health directly from the workspace.
- Strata Management Companies — coordinate supplier lists and monitor financial ledgers for entire property portfolios.
Built-in capabilities (12)
Verify Urbanise API connectivity
Requires job title and description. Schedule a new maintenance task
Get authenticated client details
List chart of accounts
List active event webhooks
List infrastructure equipment
Retrieve ledger and billing info
List facility maintenance tasks
List property suppliers
List budgets for plans
List residents and owners
List all property plans
Why Cursor?
Cursor's Agent mode turns Urbanise into an in-editor superpower. Ask Cursor to generate code using live data from Urbanise 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
Urbanise in Cursor
Urbanise and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Urbanise 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 Urbanise in Cursor
The Urbanise 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
Urbanise for Cursor
Every tool call from Cursor to the Urbanise MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I create a new maintenance job for a property via AI?
Yes! Use the create_maintenance_job tool and provide a title and description. This will instantly register a new task in the Facility Management (FM) module.
How do I see all residents living in a specific property plan?
Run the list_property_occupants query. Your agent will retrieve the complete list of owners and residents across your managed property plans.
Is it possible to check the remaining budget for a building via AI?
Absolutely. Use the list_property_budgets query to retrieve the current budget definitions and allocations for your managed properties.
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.