Bring Strata Management
to Claude Desktop
Learn how to connect Urbanise to Claude Desktop 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 Claude Desktop?
Claude Desktop is the definitive way to connect Urbanise to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 12 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Urbanise in Claude Desktop
Urbanise and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Urbanise to Claude Desktop 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 Claude Desktop
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 Claude Desktop 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 Claude Desktop
Every tool call from Claude Desktop 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.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.