Back to MCP Servers

Yardi Virtuoso MCP Server

Official Yardi Virtuoso MCP server. Securely connects AI assistants to Yardi property management data, work orders, and entity lookups via YardiOne.

Collaboration by Yardi Systems OAuth2 active
Overview

The Yardi Virtuoso MCP server is the official Model Context Protocol endpoint from Yardi Systems, released as part of the Virtuoso Connectors initiative announced at the 2025 Yardi Advanced Solutions Conference (YASC). It exposes real-time Yardi property, financial, and operations data to MCP-compatible AI clients, starting with Anthropic's Claude. The initial release focuses on work order management and entity autocomplete across the Yardi platform, with broader portfolio, financial modeling, and predictive maintenance capabilities on the roadmap.

The server is hosted by Yardi at https://mcp.virtuoso.ai/mcp using the streamable-HTTP transport and authenticates through YardiOne, so customers do not self-host any code. It is positioned for investment, property, and asset management professionals who want to query Yardi using natural language instead of manual report extraction. Because connectors are dedicated and hosted, Yardi states they preserve the existing privacy, security, and compliance posture of customer data.

This is a first-party, vendor-maintained integration rather than a community fork, and is currently in early access. Public technical documentation is limited, and additional LLM support beyond Claude is planned for 2026.

Tools

Tool Description
rfm_connectai_create_work_order Create a new work order with description, priority, and custom fields.
rfm_connectai_search_work_orders Search and filter existing work orders by date range, status, property, and other criteria.
rfm_workorder_mark_work_order_as_complete Mark a work order as complete and attach completion notes.
vn_mcpframework_get_autocomplete Get autocomplete suggestions for Yardi entities such as properties, vendors, tenants, and units.
vn_mcpframework_list_autocomplete_types List the entity types available for autocomplete lookup in the current Yardi tenant.
Setup Guide

Prerequisites

  • Active Yardi Virtuoso subscription with YardiOne credentials
  • Access to Virtuoso Connectors (currently in early access, contact your Yardi account team)
  • An MCP-compatible client such as Claude Desktop, Cursor, or Cline

Server endpoint

The server is hosted by Yardi. There is nothing to install locally.

https://mcp.virtuoso.ai/mcp

Transport: streamable-http

Claude Desktop / Cursor / Cline config

Add the following to your MCP client config (e.g. mcp.json in Cursor, or claude_desktop_config.json):

{
  "mcpServers": {
    "yardi-virtuoso": {
      "url": "https://mcp.virtuoso.ai/mcp"
    }
  }
}

Restart the client. On first use you will be prompted to authenticate with YardiOne. Once signed in, the five Yardi tools become available to the agent.

Notes

  • Available tools and scopes depend on your Yardi permissions and licensed modules.
  • Refer to help.virtuoso.ai and your Yardi support contact for product-specific documentation.
Use Cases
  • Create maintenance work orders in Yardi directly from a chat with your AI assistant, including priority and custom fields.
  • Triage open work orders by searching across status, date, and property to surface what needs attention today.
  • Close completed maintenance tickets in bulk by marking work orders complete with structured completion notes.
  • Resolve property, unit, vendor, and tenant references by natural language using the autocomplete tools, so agents can chain follow-up actions on the right entity.
  • Build property operations assistants that combine work order search with entity lookups to answer questions like "what is open at this property this week."
Example Prompts
  • "Create a high-priority work order for a leaking dishwasher at unit 204 of Maple Court."
  • "Show me all open work orders at Riverside Apartments created in the last 14 days."
  • "Mark work order 18342 as complete with note 'HVAC filter replaced, system tested.'"
  • "Find the vendor record that matches 'Acme Plumbing' and list any open work orders assigned to them."
  • "What entity types can I look up in Yardi right now?"
Pros
  • Official, vendor-hosted server maintained by Yardi, not a community fork.
  • Zero install: just point an MCP client at the hosted URL and authenticate with YardiOne.
  • Covers the highest-frequency property ops workflow (work order create, search, complete) plus entity autocomplete to ground other actions.
  • Built on the standard MCP streamable-HTTP transport, so it works with any compliant client.
Limitations
  • Early access: requires Yardi engagement and is not openly self-serve.
  • Narrow tool surface today (5 tools, focused on work orders and autocomplete). Financial modeling, portfolio, and predictive maintenance capabilities described in marketing are not yet exposed as discrete tools.
  • Public technical documentation is sparse; most setup and scope details come through Yardi support and partner pages rather than a published spec.
Alternatives
  • Yardi Kube MCP server (via Zapier or viaSocket) for coworking-specific Yardi Kube workflows.
  • Generic database or REST MCP servers wired to Yardi's existing SOAP/REST APIs, for customers who need broader read access today.
  • AppFolio or RealPage integrations via custom MCP servers for teams not on Yardi.