# IDX Broker MCP Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## IDX Broker MCP

Access IDX Broker leads, agents, listings and MLS data for real estate professionals

- Record: https://musedirectory.ai/connector/idx-broker-mcp
- Category: Developer Tools
- Developer: usefulapi (https://usefulapi.io/idx-broker/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 326ms, checked 2026-10-29T21:11:20Z
- Endpoint: https://idx-broker.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-29T21:11:20Z)
- Source: Found in the official MCP Registry (io.usefulapi/idx-broker) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Fidx-broker

Connects to IDX Broker to read and manage leads, agents, offices, listings across multiple MLS feeds, and create or update lead notes. Designed for real estate brokers and agents using IDX Broker's CRM and website platform.

Example request: "Show me all new leads from the past week and add a follow-up note to the most recent one"

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use IDX Broker MCP to help me. It is a free service with an MCP server at https://idx-broker.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- idx_get_account_info: The IDX Broker client account this access key belongs to: company and contact details and account settings (access keys and passwords are never returned). The reply also shows how many of the key's hourly API accesses are used. GET /clients/accountinfo.
- idx_get_account_type: The IDX Broker plan of the account (Lite or Platinum). It sets the hourly API limit: 300 accesses per key on Lite, 500 on Platinum. GET /clients/accounttype.
- idx_list_agents: Agents on a multi-user IDX Broker account (id, name, office, contact details, category, language, login dates). Filter by one field or by a time window. GET /clients/agents.
- idx_list_offices: Offices on a multi-user IDX Broker account. Filter by one field or by a time window. GET /clients/offices.
- idx_list_leads: List the account's leads (website registrants) with contact details, status, agent owner, and last viewed listings and searches. A reply holds up to 500 leads; pass offset to page on and look for pagination information in the reply. Filter by a time window on signup, edit, login 
- idx_get_lead: One lead by id with its details, last 5 viewed listings and searches, and the total number of listings viewed. GET /leads/lead/{leadID}.
- idx_list_lead_notes: Notes on a lead, or one note when note_id is given. GET /leads/note/{leadID}[/{noteID}].
- idx_list_lead_searches: Saved property searches of a lead (or one search when search_id is given), with the results URL of each. GET /leads/search/{leadID}[/{searchID}].
- idx_list_lead_saved_properties: Properties a lead saved (or one when property_id is given). GET /leads/property/{leadID}[/{propertyID}].
- idx_get_lead_traffic: Website traffic history of one lead: date, page, referrer and IP of each visit (at most 5,000 rows per request; use interval/offset/limit to narrow it). GET /leads/leadtraffic/{leadID}.
- idx_list_featured_listings: The account's featured (active) listings with address, price, status, photos and agent. Only the account's own listings are returned, never general MLS data. GET /clients/featured.
- idx_list_sold_pending_listings: The account's sold and pending listings, that is those removed from the MLS feed. GET /clients/soldpending.
- idx_list_off_market_listings: The account's off-market listings. GET /clients/offmarket.
- idx_list_supplemental_listings: The account's supplemental (non-MLS) listings with a basic set of fields. GET /clients/supplemental.
- idx_list_saved_links: Saved links (pre-built property search pages) of the account with id, name and URL. GET /clients/savedlinks.
- idx_get_saved_link_count: The total number of properties a saved link currently matches. GET /clients/savedlinks/{savedLinkID}/count.
- idx_list_widgets: The JavaScript widgets on the account with id, name, URL and options. GET /clients/widgets.
- idx_get_widget: One JavaScript widget with its settings. GET /clients/widgets/{id}.
- idx_list_system_links: The system pages of the account's site (search, featured, contact...) with name, id and URL, which can be linked to directly. GET /clients/systemlinks.
- idx_list_approved_mls: The MLSs approved for display on the account, with their IDX ids (such as a001) and names. Use the id in the other MLS tools. GET /mls/approvedmls.
- idx_get_mls_age: When an MLS feed was last downloaded and processed and when its images were last gathered (UTC). GET /mls/age/{idxID}.
- idx_list_mls_property_types: Property types of an MLS with the IDX type id, the MLS name, the parent type and subtypes. GET /mls/propertytypes/{idxID}.
- idx_list_mls_search_fields: The fields of an MLS that can be searched under MLS rules: field name, display name and the property types they belong to. GET /mls/searchfields/{idxID}.
- idx_list_mls_locations: Cities, counties or postal codes present in an MLS's data, with ids and a count of occurrences. Filter fields: cities = cityID, cityName, stateAbrv, mlsPtID; counties = countyID, countyName, stateAbrv, mlsPtID; postalcodes = id, stateAbrv, mlsPtID. GET /mls/{cities|counties|posta
- idx_create_lead: WRITE: creates a new lead in the IDX Broker account (and may trigger the account's own lead notifications). Needs a correctly formatted email with a valid MX record; IDX rejects bad addresses with a server error. Extra fields go in `fields` by their IDX name, as seen on a lead re
- idx_add_lead_note: WRITE: adds a note to a lead (visible to the account's agents). Returns the new note id. PUT /leads/note/{leadID}.
- idx_update_lead: WRITE: changes fields of an existing lead; the given values replace the stored ones. Only pass what must change. Field names are the IDX lead field names as seen on a lead returned by idx_get_lead (for example firstName, lastName, email, phone, status). POST /leads/lead/{leadID}.

Screening checks:
- MCP handshake: pass (Answered in 326ms)
- Domain against threat feeds (Cloudflare security DNS): pass (idx-broker.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (27 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)