Manages connected MCP sources for enterprise search. Detects available sources, guides users to connect new ones, handles source priority ordering, and manages rate limiting awareness.

Source Management If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Knows what sources are available, helps connect new ones, and manages how sources are queried. Checking Available Sources Determine which MCP sources are connected by checking available tools. Each source corresponds to a set of MCP tools: Source Key capabilities ~~chat Search messages, read channels and threads ~~email Search messages, read individual emails ~~cloud storage Search files, fetch document contents ~~project tracker Search tasks, typeahead search ~~CRM Query records (accounts, contacts, opportunities) ~~knowledge base Semantic search, keyword search If a tool prefix is available, the source is connected and searchable. Guiding Users to Connect Sources When a user searches but has few or no sources connected: When a user asks about a specific tool that is not connected: Source Priority Ordering Different query types benefit from searching certain sources first. Use these priorities to weight results, not to skip sources: By Query Type Decision queries ("What did we decide..."): Status queries ("What's the status of..."): Document queries ("Where's the doc for..."): People queries ("Who works on..." / "Who knows about..."): Factual/Policy queries ("What's our policy on..."): Default Priority (General Queries) When query type is unclear: Rate Limiting Awareness MCP sources may have rate limits. Handle them gracefully: Detection Rate limit responses typically appear as: HTTP 429 responses Error messages mentioning "rate limit", "too many requests", or "quota exceeded" Throttled or delayed responses Handling When a source is rate limited: 1. Do not retry immediately — respect the limit 2. Continue with other sources — do not block the entire search 3. Inform the user : 4. For digests — if rate limited mid scan, note which time range was covered before the limit hit Prevention Avoid unnecessary API calls — check if the source is likely to have relevant results before querying Use targeted queries over broad scans when possible For digests, batch requests where the API supports it Cache awareness: if a search was just run, avoid re running the same query immediately Source Health Track source availability during a session: When reporting search results, include which sources were searched so the user knows the scope of the answer. Adding Custom Sources The enterprise search plugin works with any MCP connected source. As new MCP servers become available, they can be added to the .mcp.json configuration. The search and digest commands will automatically detect and include new sources based on available tools. To add a new source: 1. Add the MCP server configuration to .mcp.json 2. Authenticate if required 3. The source will be included in subsequent searches automatically

source-management