Dust

Dust is an enterprise AI assistant platform built to connect company knowledge and internal tools into custom AI agents that teams can actually rely on day to day. Rather than shipping a generic chatbot, Dust lets organizations build assistants scoped to specific workflows — customer support, engineering onboarding, sales enablement, internal documentation search — by grounding them in the company's own data sources. For teams evaluating enterprise AI assistant platforms, Dust's appeal is its focus on connecting knowledge and tools in one place so agents give answers that reflect how the business actually operates, not just what a foundation model knows out of the box.

The challenge most companies hit after adopting a platform like Dust is fragmentation: knowledge lives in Dust, but revenue data sits in ad platforms, customer data sits in a CRM, and operational metrics sit in yet another dashboard. BusinessMCP.com solves this by giving you one hosted MCP server that unifies Dust-connected knowledge alongside your other tools, databases, and ad platforms, plus a business-intelligence dashboard to see it all together. Connect Dust once through your BusinessMCP.com account, and its context becomes available to any AI agent — Claude, GPT, Gemini, or a custom model — through a single model-agnostic endpoint at /api/mcp, authenticated with a Bearer mcph_* key. This means your team doesn't need to rebuild integrations for every new model or agent framework; the MCP layer stays stable while the AI layer evolves.

This pattern is especially useful for organizations running Dust as their enterprise knowledge and assistant layer while also wanting AI agents to reason across marketing spend, product usage, or support tickets in the same conversation. Instead of switching between a Dust-powered assistant and separate BI tools, teams get a unified view: an agent can pull relevant internal documentation via Dust and cross-reference it with live business metrics from other connected sources, all through the same hosted MCP session. Because BusinessMCP.com is cookieless and GDPR-friendly by design, this works well for regulated industries and enterprise teams with strict data-handling requirements who still want flexible, model-agnostic access to their Dust-connected knowledge base.

Teams typically reach for this setup when they've already invested in Dust for internal knowledge and custom agent building but need a consistent way to expose that context to multiple AI clients — whether that's a growth-suite app, a coding assistant, or a support tool — without duplicating integration work for each one. If your organization is comparing enterprise AI assistant platforms or looking to centralize how Dust's knowledge and tool connections reach different AI agents, hosting it behind a unified MCP endpoint with built-in business intelligence turns a single-purpose assistant platform into a shared, queryable layer for the whole business.