We are building an MCP server for Showcase IDX accounts. It is in development, and this is the first of three notes written while we build it. This one covers why, how, and where we draw the line.
Disclosure: IDX Webmasters is the IDX division of Virtual Results, which builds this MCP. Showcase IDX is a trademark of its owner. This is an independent project, and nothing here implies that Showcase IDX endorses or sponsors this MCP.
Access state: in development. Nothing connects to a Showcase account today. The planned address is https://showcase.virtualresultsplatform.com/mcp, and it is planned, not live. Details are on the Showcase IDX MCP page.
Why Showcase
We already run an MCP for IDX Broker and one for iHomefinder. We expect agents who use Showcase IDX want the same thing: ask an assistant who the new leads are and who needs a follow-up, then draft the reply. That is the job we are aiming at.
The constraint
Showcase has no public developer API. We looked for one using public sources only, with no logins. The developer-platform page returns a "not found" page, and none of the 111 support-center articles we read documents a REST API, third-party API keys or webhooks.
What Showcase does document is outbound automation:
- A Zapier app with a "New Lead" and a "New Message" trigger.
- A Slack incoming-webhook integration, on the Premium plan.
- Premium integrations with a few CRMs.
Showcase's own support article says its Slack integration "can be used in place of a direct API with us", which points the same way. Showcase's own Zapier help article says that inbound to Showcase IDX is not supported. So there is no documented way to write to an account from outside.
There is also a partner program for deeper integrations. The terms of any API under it are not public. We plan to ask Showcase about it rather than assume.
Our plan: two legs
Leg one: Showcase's documented lead webhooks. New leads and messages arrive through the outbound integrations Showcase documents. This leg is read-only and supported. The agent configures it in their own Showcase account, pointing it at an address we give them.
Leg two: your own Showcase login. Lookup, hot leads, saved searches and hot sheets live only in the Showcase dashboard. To reach them we would use the agent's own login to their own account. We label this leg unofficial, because it relies on the dashboard's internal API, which is not documented or sanctioned by Showcase. We have not read Showcase's terms of service, and we have not verified that this is permitted. We will say so on every page that describes it.
What we will not do
- Claim an official integration. There is none, and we will not imply one.
- Ask for credentials in chat or by email. A login belongs on a settings page, never in a conversation with an assistant.
- Rely on the unverified parts silently. If a tool depends on the dashboard's internal API, its description will say so.
- Write to an account without saying what happens. Creating a lead in Showcase emails that lead, so any write we add will state that before it runs.
- Promise what Showcase has not published. If Showcase adds a partner API, we will move to it and tell you.
What else comes in the connection
Each of our MCP connections includes our 11 WordPress tools, so the same assistant that finds your leads can draft a post on your own site. You sign in once with a Virtual Results account, and billing is built in. It is currently free during testing.
Feedback wanted
If you use Showcase IDX, tell us which of these matters most: lead alerts, lead lookup, follow-up drafts, or saved searches and hot sheets. If you have talked to Showcase about their API, we would like to compare notes. Join the early-access list or read the Showcase page. More notes are in the journal.
Keep the conversation going.
Ask a question, share a workflow, or add your perspective. Comments are public and hosted on GitHub; a GitHub account is required to post.
Comment on GitHub