This is the second note in our Showcase IDX MCP series. The first covered our approach. This one is the inventory: what Showcase exposes, how sure we are about each part, and the tools an assistant could offer on top.
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.
Read this first: Showcase has no public developer API. Everything under "internal" below comes from route names visible in the dashboard's public JavaScript. We have not called them, we do not know their methods or response shapes, and using them may not be permitted. Treat that section as a map of what exists, not a contract.
Documented and supported
All of it is outbound, meaning data leaves Showcase and nothing goes in.
- Zapier "New Lead" trigger. Fires when a lead is created from the site or in the dashboard. Showcase's help text describes about 15-minute updates, so it is not real time.
- Zapier "New Message" trigger. Covers the contact form, CMA form, Ask a Question, Schedule a Tour and Friends and Family comments.
- Zapier actions. None. Showcase states that inbound to Showcase IDX is not supported.
- Slack incoming webhook. Premium plan, set up by an admin, posts leads and messages as they happen. The payload is presumably Slack-shaped, but we have not verified it.
- CRM integrations. Follow Up Boss, LionDesk and Prospect Converter, Premium plan, plus a middleware option for others.
Our parser for these hooks matches field names loosely, such as name, email, phone, message, listing and source, and falls back to scanning Slack-style text for an email address and a phone number. Those names are assumptions, not documentation. We are not publishing a field list for the webhook payloads, because Showcase has not documented one and we will not invent it. Once we have seen real payloads from a test account, we will document what we observed and mark it as observed, not promised.
Internal, from the dashboard's public code (unverified)
The dashboard is a single-page app. Its public JavaScript shows an internal, cookie-session API covering leads, messages, saved searches, hot sheets and settings.
What we do not know is more important than what we know: methods, parameters, response shapes, rate limits, stability, and whether partner automation is allowed. We are not planning anything against the reseller dashboard.
Dashboard-only features
According to Showcase's help center, these are done in the dashboard and have no documented API:
- Viewing, editing, assigning and deleting leads, and setting status and persona.
- The saved-search library and hot sheets, which can be shown on a WordPress site by shortcode.
- Lead routing, email templates, users, integrations and billing.
- Bulk lead import, which is done by emailing a CSV to Showcase support.
Side effects to know about
- Creating a lead in the dashboard emails that lead a template with an "access your account" button.
- Subscribing a lead to a saved search triggers emails to that lead.
- Showcase has no SMS feature.
- Showcase documents no rate limits.
These matter for an assistant, because a harmless-sounding "add this lead" would contact a real person.
Tool ideas
Here is what an agent could offer, split by which leg of our plan it depends on.
From the webhooks (supported, read-only):
- A lead and message inbox.
- A new-lead alert, bearing in mind the Zapier delay.
- A follow-up queue and a drafted reply per lead.
From the user's own login (unofficial, if permitted):
- Lead lookup and hot leads.
- A list of saved searches and hot sheets.
- Notes and tags on leads, only where we can verify the call and its side effects.
From our WordPress tools (11, in the same connection):
- Draft a post or a landing page from what the assistant found, for you to review.
Nothing in the second list is built until we have verified it against a test account.
What would make this simpler
A documented partner API with a key model, a sandbox, rate limits and documented webhook payloads would replace the whole unofficial leg. We plan to ask Showcase. If you are a Showcase customer with a contact there, we would be glad of an introduction.
Feedback wanted
Which of these tools would you actually use? What did we get wrong about Showcase? Join the early-access list, see the Showcase page, or browse 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