IDX Broker MCP by usefulapi

Most tools target a distinct resource+action pair, and the several listing-listing tools (featured, off-market, sold/pending, supplemental) are clearly separated by their descriptions. Minor confusion is possible between account-level idx_list_saved_links and lead-level idx_list_lead_searches/saved_properties, and between the MLS read tools which look similar but differ by resource.

Every tool follows a strict idx_verb_noun pattern (idx_get_*, idx_list_*, idx_create_lead, idx_update_lead, idx_add_lead_note), with the idx_ prefix applied uniformly. Resource nouns match the underlying REST paths, making the set highly predictable.

At 27 tools the set is heavy for a single server, sitting just above the comfortable range. The breadth is defensible because the server spans several domains (leads, MLS metadata, listings, account/agents/offices, widgets, saved links), but it is approaching the point where tools feel like thin endpoint wrappers.

Leads have a solid lifecycle (create, get, list, update, add/list notes) and the MLS/listing read surface is broad and well covered. Gaps exist on the write side for widgets, saved links, and offices/agents (read-only), and no lead delete, but these likely reflect API or domain limits rather than oversight.