IDX Broker MCP: Where We Are, V1 to V4 and Beyond

The IDX Broker MCP is an MCP server for IDX Broker accounts. This is a status report for developers and technical agents: how it got here, what works, what is still open, and where we want feedback.

Disclosure: IDX Webmasters is the IDX division of Virtual Results, which builds the IDX Broker MCP. IDX Broker is a trademark of its owner. This is an independent project, and nothing here implies that IDX Broker endorses or sponsors this MCP.

Access state: self-serve sign-up is open at https://vr-idx-app.virtualresults.workers.dev. You need your own IDX Broker account. The IDX Broker MCP is still early software, so expect rough edges and tell us about them.

Versions at a glance

V1 (core account): leads, saved searches, saved links, widgets, featured listings, account status.
V2 (lead depth): lead notes, saved properties, supplemental listings, system links, MLS counts and prices.
V3 (reach): bulk lead create and update, market reports, message history, listing search and detail, Social Pro.
V4 (site admin): custom CSS, sub-headers, wrapper cache, legacy widgets, API metadata.
Hardening (reliability): time budget with a "still working" result, search-criteria fixes, stress-testing pagination.
Docs (coverage): call catalog, client handbook, status report.

Version labels follow our own discovery reports, where each version was first exercised against the live API on a test account before it was built. Merge requests from our private repository include !130 (V4), !132 (V4 legacy widgets), !139 to !141 (stress testing, partner key and wording fixes), !145 (search criteria), !153 (time budget for slow calls), !157 (call catalog and client handbook) and !178 (status documentation). The numbers are plain references because the repository is private.

Where it stands

103 tools for IDX Broker, covering leads, notes, saved properties, saved searches, saved links, widgets, market reports, bulk operations, messages, account profile, your own listings, MLS lookups, and your public site's settings.
Deployed and connected, with its own connection URL. It has been connected since late September. When we first audited it on September 27 it exposed 18 tools.
Call catalog: on October 2 we ran every tool through a real connector. The result was 103 tools, 99 passed, 0 failed and 4 expected refusals.
Three-call confirmation for anything that changes or deletes existing data. The first call changes nothing and returns a confirmation token, because deleting in IDX Broker cannot be undone.

How it behaves

A few design choices, because developers ask:

One account per organization. You sign in with your Virtual Results login, and every call acts on the one IDX Broker key connected to your organization. There is no site argument to pass.
Your key does not go through the model. There is a private settings link for entering it, so it stays out of chat.
Read before write. The server's own instructions tell the assistant to check connection health first, look up valid search fields before building criteria, and plan a saved-search change before making it.
Merge, do not overwrite. Updates read the current record, merge your change, write, then read back to confirm.
Partners are excluded. The server manages one agent's account and never another partner's book of business.

What we are working through

Listing search is limited. General listing search works only on accounts under Virtual Results' IDX partnership, so it is not a feature every IDX Broker account gets.
Pagination quirks. Some IDX Broker endpoints ignore limit and offset, and some return empty responses where you would expect an empty list. We built a stress harness to find these and handle them.
Slow calls. Some vendor calls take long enough that clients time out, so the server now returns a "still working" result you can check back on.
Social Pro is the least proven area. It needs a paid add-on on the account, so treat posting as experimental.
Some shapes are unverified. A few endpoints returned empty data on our test account, so we have not confirmed what a populated response looks like.
Some things are deliberately not built. The dynamic wrapper URL is write-only, so we could not offer a tool that cannot confirm its own change.

What is next

Smoother onboarding, now that self-serve sign-up is open, so connecting takes fewer steps.
New-lead alerts. Neither API's documentation lists webhooks, so this means polling on a schedule.
Live listing search through Virtual Results' own IDX, for requests like "Scottsdale, 3 bed, 2 bath, under $900k".
Fewer tools per connection. Each product now has its own connection, so each stays under the 128-tool limit that OpenAI-based clients enforce. The iHomefinder MCP has its own as well. We want to make connecting simpler still.
CRM tools after that, starting with Follow Up Boss.

How to test it

Connect your own account. We never need your credentials by email, and we will not ask you to send them.

The connection URL is https://idxbroker.virtualresultsplatform.com/mcp (103 tools, plus 11 WordPress tools). Every product follows the same pattern, https://<product>.virtualresultsplatform.com/mcp, so future tools get their own address the same way.

Add it as a connector. In Claude, go to Settings, then Connectors, then Add custom connector, and paste the URL. In ChatGPT, add it as a developer-mode connector.
Sign in with a Virtual Results account. If you do not have one yet, sign up here.
Enter your own IDX Broker API key on the private settings page the tools link you to. Never type it into chat.
Ask "Is my IDX connection working?" first. It runs a full health check, including key validity and rate limit.
Try a few reads, then one change that asks you to confirm.

If you want help getting set up, or your account is managed by Virtual Results, ask us.

For example prompts, see the use-case library and the documentation.

Connections: one per product

We now run one connection per product, such as IDX Broker MCP and iHomefinder, and each one includes the WordPress tools (103 plus 11, so 114 in total). Each stays under the 128-tools-per-connection limit that ChatGPT enforces, and all of them use the same Virtual Results login. We are also testing Cloudflare "code mode" to combine everything into a single connection. That is an experiment, and we are not promising it.

Using our WordPress MCP too

Virtual Results also runs a WordPress MCP for site content. It lists your sites, searches and reads posts and pages, uploads media, and creates drafts. Publishing needs a review step and two confirmations, so an assistant cannot make something live by itself.

It never uses WordPress passwords. A person signs in with their Virtual Results login, and the MCP acts as their own WordPress user through a short-lived signed pass that a small Virtual Results plugin on the site checks. Today that works on sites we host, which we link to your account. For other WordPress sites, a free "Virtual Results AI Connect" plugin is planned (coming soon). It would give you a one-click Connect and Virtual Results sign-in, with no passwords or API keys to paste.

What you need depends on who is asking:

A person: a normal user account, which is their Virtual Results login. It is not a service account.
An automation or bot: a dedicated service account, linked to a limited WordPress user.
A site Virtual Results hosts: we set up the access for you.

The WordPress tools are included in your IDX Broker MCP connection, so an agent can pull listings and leads and draft a post on your own site from one connection. The IDX tools themselves do not edit WordPress. They give you links and embed codes, and the WordPress tools can place them in a draft.

What is most used, and what would make this easier

We do not have enough testers to publish usage numbers. Our expectation, which we want you to confirm or correct, is that the lead list, saved-search alerts and saved links get the most use.

What we think would help most:

One-click connect, so there is no connector URL to find.
Fewer tools per connection, so every client works.
Lead alerts instead of asking each morning.

Feedback wanted

Tell us what is missing, what is wrong and what you would use daily. Request a feature or ask for setup help. If you build against the IDX Broker API yourself, we would like to compare notes on its quirks.

Coming next for the platform

One Virtual Results account and dashboard across tools.
Billing built in. It is currently free during testing.
A share and referral program.

These are plans, not features you can use today.