Support MCP connections for Community Search as an alternative to Federated Search.

Problem / Current state

We're trying to make Community the one-stop shop for our customers — the single place they go instead of bouncing between the tech docs platform, the support platform and community itself. Today the only path to that is federated search because the tech docs and support platforms we use aren't native Gainsight integrations. So making their content searchable means our engineering team builds and maintains a custom API connection for each source. Every non-native source is another custom build and another thing to maintain — a hard bottleneck on the one-stop-shop vision.

Why now

MCP is quickly becoming the standard way platforms expose their content and capabilities, and the platforms we use already offer it. That creates a real tension: investing engineering time into federated-search API builds means investing in an integration approach the industry is already moving past. Given how fast AI-driven search is evolving, Community should be leaning into the MCP approach now rather than accumulating custom federated-search infrastructure it will want to replace.

Proposed solution

Let Community Search connect to external content sources via MCP, so a non-native platform can be connected the way a native app would be — instead of through a custom-built federated-search API integration. Because the platforms we already use for tech docs and support expose MCP servers, Community Search consuming those servers directly removes the custom engineering step entirely. The search AI could then retrieve and rank across every connected source and return everything relevant to a query — a community post, a course, a tech doc, a KB article — in one result set.

Value

• Makes the one-stop-shop vision achievable without a custom engineering project per source.
• Removes both the upfront custom-API build and the ongoing maintenance burden of federated-search connections.
• Turns adding a source into a connection rather than a roadmap item gated on engineering bandwidth.
• Positions Community Search on the trajectory the AI and platform ecosystem is already on, rather than on infrastructure that's aging out.
• Gives the search AI a richer retrieval layer across all sources, driving more first-search resolutions and less customer effort.