Urbanise MCP Server for Claude DesktopGive Claude Desktop instant access to 12 tools to Check Api Health, Create Maintenance Job, Get Client Profile, and more
Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.
Ask AI about this App Connector for Claude Desktop
The Urbanise app connector for Claude Desktop is a standout in the Erp Operations category — giving your AI agent 12 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Urbanise and 3,400+ MCP Servers from a single visual interface.
{
"mcpServers": {
"urbanise": {
// Your Vinkius token. get it at cloud.vinkius.com
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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
About 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.
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.
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.
The Urbanise MCP Server exposes 12 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
All 12 Urbanise tools available for Claude Desktop
When Claude Desktop connects to Urbanise through Vinkius, your AI agent gets direct access to every tool listed below — spanning strata-management, facility-management, building-operations, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.
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
Connect Urbanise to Claude Desktop via MCP
Follow these steps to wire Urbanise into Claude Desktop. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Open Claude Desktop Settings
claude_desktop_config.jsonAdd the MCP Server
mcpServers sectionRestart Claude Desktop
Start using Urbanise
Why Use Claude Desktop with the Urbanise MCP Server
Claude Desktop by Anthropic provides unique advantages when paired with Urbanise through the Model Context Protocol.
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 + Claude Desktop Use Cases
Practical scenarios where Claude Desktop combined with the Urbanise MCP Server delivers measurable value.
Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation
Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language
Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary
Learning and training: new team members can explore API capabilities conversationally without needing to read documentation
Example Prompts for Urbanise in Claude Desktop
Ready-to-use prompts you can give your Claude Desktop agent to start working with Urbanise immediately.
"List all property plans managed in my Urbanise account."
"Show me all active maintenance jobs for 'Sunset Heights'."
"Create a maintenance job: 'Fix leaking pipe in Room 402'."
Troubleshooting Urbanise MCP Server with Claude Desktop
Common issues when connecting Urbanise to Claude Desktop through the Vinkius, and how to resolve them.
Server not appearing after restart
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).Authentication error
Tools not showing in chat
Urbanise + Claude Desktop FAQ
Common questions about integrating Urbanise MCP Server with Claude Desktop.
How does Claude Desktop discover MCP tools?
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?
Can I connect multiple MCP servers simultaneously?
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.