Connect Yardi Virtuoso to Well
Connect Yardi Virtuoso to make it reachable from conversation and your agents in Well. Yardi Virtuoso exposes no structured records to sync today, so this is a reach connection, not a data feed.
What Well pulls from Yardi Virtuoso
Yardi Virtuoso feeds Yardi Virtuoso into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Yardi Virtuoso’s access.
| From Yardi Virtuoso | In Well | Relation | |
|---|---|---|---|
| Yardi Virtuoso | Workspace context | Reachable from |
- Sync mode
- MCP hybrid
- Refresh
- live + reconciliation reads
- Direction
- Yardi Virtuoso → Well
What Well does with your Yardi Virtuoso connection
Connect
Connect Yardi Virtuoso over OAuth (MCP DCR): Well registers a client through Yardi Virtuoso's OAuth Dynamic Client Registration and you approve on Yardi Virtuoso's side, so the password never reaches Well; Well holds only a scoped token it can refresh.
Sync
Connecting Yardi Virtuoso makes it reachable from your workspace; Yardi Virtuoso exposes no structured records for Well to sync into the data model today.
Enrich
With no records to ingest, Yardi Virtuoso adds reach without enrichment; entity resolution and categorisation run for connectors that bring structured data in.
Available
Yardi Virtuoso is reachable from conversation and agents in your workspace; once it exposes structured records they land alongside the rest of your connected tools.
Questions Yardi Virtuoso unlocks
Ask in plain language. Well answers from your connected Yardi Virtuoso connection, resolved against the rest of your stack.
Ask anything about your Yardi Virtuoso connection
Ask about your Yardi Virtuoso connection…
Connect Yardi Virtuoso in three steps
- 01
Authorise Yardi Virtuoso via MCP
From Well's Connections panel, search for Yardi Virtuoso and click Connect. Well discovers Yardi Virtuoso's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Yardi Virtuoso's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP servermcp.virtuoso.ai/mcp
- 02
Make it reachable
The connection puts Yardi Virtuoso within reach of your workspace and its agents. Yardi Virtuoso exposes no structured record for Well to map into an invoice, transaction, or account today, so there is no records table to set up and Well will not invent one to fill the step.
- Mappingnone (reach-only)
- 03
Use it from your workspace
Use the connection to let an agent reach Yardi Virtuoso in the same place it reaches the rest of your stack. If Yardi Virtuoso later exposes structured entities that map onto what Well captures, the data-flow section would reflect the real records.
- Availabilityreachable as soon as connect completes
This is a reach-and-availability connection, not a records feed, so nothing backfills.
How Yardi Virtuoso stays secure with Well
Well connects to Yardi Virtuoso's MCP server (mcp.virtuoso.ai/mcp) via the Model Context Protocol. The MCP server handles credential issuance through OAuth Dynamic Client Registration, so Well never holds a long-lived Yardi Virtuoso secret. Because Yardi Virtuoso maps no structured entity today, the token simply makes Yardi Virtuoso reachable from your workspace rather than syncing records. The connection is read-only and grants Well nothing it could change in Yardi Virtuoso.
- granted
Read Yardi Virtuoso records
Resources the Yardi Virtuoso MCP server exposes, scoped by your OAuth approval.
- granted
Reach Yardi Virtuoso from your workspace
The grant makes Yardi Virtuoso reachable from conversation and your agents. It maps no structured entity, so Well resolves no records and can change nothing in Yardi Virtuoso.
- refused
Modify or delete Yardi Virtuoso records
Not granted; Yardi Virtuoso is read-only in Well. Write-back is opt-in per connector when a write surface exists.
- refused
Store Yardi Virtuoso passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
Frequently asked questions about Yardi Virtuoso and Well
How do I connect Yardi Virtuoso to Well, and how long does it take?
Choose Yardi Virtuoso in Well's Connections panel and authorise it over its MCP server. Well discovers the OAuth metadata from the MCP endpoint and registers a client via Dynamic Client Registration, so there are no keys to paste. The handshake completes in about a minute and puts Yardi Virtuoso within reach of your workspace and its agents.
What does Well sync from Yardi Virtuoso today?
No structured record, and the page is candid about that. Yardi Virtuoso exposes no supported target model for Well to turn into an invoice, transaction, or account, so there is no records table to configure and nothing is pulled into your workspace. The connection is about reach, not a data feed.
If nothing is synced, what does connecting Yardi Virtuoso give me?
It lets an agent working in your workspace reach Yardi Virtuoso in the same place it reaches the rest of your stack, instead of treating it as a separate destination. This is a reach-and-availability connection: honest about not pulling structured records that Yardi Virtuoso does not expose.
Will Yardi Virtuoso ever bring records into the workspace?
Only if and when Yardi Virtuoso exposes structured entities through its MCP server that map onto what Well captures. Until then Well will not invent a synced record to make the page look fuller; if that changes, the data-flow section would reflect the real entities.
What happens if I disconnect Yardi Virtuoso?
Disconnecting Yardi Virtuoso in Well revokes the OAuth token and ends the MCP reach immediately. Because nothing structured was being synced, there are no workspace records to retain or purge; it simply removes Yardi Virtuoso from the set of tools your agents can reach through Well.
Pairs well with Yardi Virtuoso
More in Real estate
Popular cross-category
Ready to connect Yardi Virtuoso?
Connect once. Every Yardi Virtuoso from Yardi Virtuoso becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.