source-management

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Source Management

源管理

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Knows what sources are available, helps connect new ones, and manages how sources are queried.

若您看到不熟悉的占位符或需要查看已连接的工具，请参阅 CONNECTORS.md。

了解可用源情况，帮助连接新源，并管理源的查询方式。

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.

通过检查可用工具来确定已连接的MCP源。每个源对应一组MCP工具：

源	核心能力
~~chat	搜索消息，读取频道和对话线程
~~email	搜索消息，读取单个邮件
~~cloud storage	搜索文件，获取文档内容
~~project tracker	搜索任务，联想搜索
~~CRM	查询记录（客户账户、联系人、销售机会）
~~knowledge base	语义搜索，关键词搜索

若工具前缀可用，则表示该源已连接且可被搜索。

Guiding Users to Connect Sources

引导用户连接源

When a user searches but has few or no sources connected:

You currently have [N] source(s) connected: [list].

To expand your search, you can connect additional sources in your MCP settings:
- ~~chat — messages, threads, channels
- ~~email — emails, conversations, attachments
- ~~cloud storage — docs, sheets, slides
- ~~project tracker — tasks, projects, milestones
- ~~CRM — accounts, contacts, opportunities
- ~~knowledge base — wiki pages, knowledge base articles

The more sources you connect, the more complete your search results.

When a user asks about a specific tool that is not connected:

[Tool name] isn't currently connected. To add it:
1. Open your MCP settings
2. Add the [tool] MCP server configuration
3. Authenticate when prompted

Once connected, it will be automatically included in future searches.

当用户进行搜索但已连接的源很少或没有时：

您当前已连接 [N] 个源：[列表]。

如需扩大搜索范围，您可以在MCP设置中添加更多源：
- ~~chat — 消息、对话线程、频道
- ~~email — 邮件、对话、附件
- ~~cloud storage — 文档、表格、幻灯片
- ~~project tracker — 任务、项目、里程碑
- ~~CRM — 客户账户、联系人、销售机会
- ~~knowledge base — 维基页面、知识库文章

连接的源越多，您的搜索结果就越全面。

当用户询问某个未连接的特定工具时：

[工具名称] 目前未连接。如需添加，请按以下步骤操作：
1. 打开您的MCP设置
2. 添加 [工具] 的MCP服务器配置
3. 按提示完成身份验证

连接完成后，该工具会自动纳入后续搜索范围。

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..."):

1. ~~chat (conversations where decisions happen)
2. ~~email (decision confirmations, announcements)
3. ~~cloud storage (meeting notes, decision logs)
4. Wiki (if decisions are documented)
5. Task tracker (if decisions are captured in tasks)

Status queries ("What's the status of..."):

1. Task tracker (~~project tracker — authoritative status)
2. ~~chat (real-time discussion)
3. ~~cloud storage (status docs, reports)
4. ~~email (status update emails)
5. Wiki (project pages)

Document queries ("Where's the doc for..."):

1. ~~cloud storage (primary doc storage)
2. Wiki / ~~knowledge base (knowledge base)
3. ~~email (docs shared via email)
4. ~~chat (docs shared in channels)
5. Task tracker (docs linked to tasks)

People queries ("Who works on..." / "Who knows about..."):

1. ~~chat (message authors, channel members)
2. Task tracker (task assignees)
3. ~~cloud storage (doc authors, collaborators)
4. ~~CRM (account owners, contacts)
5. ~~email (email participants)

Factual/Policy queries ("What's our policy on..."):

1. Wiki / ~~knowledge base (official documentation)
2. ~~cloud storage (policy docs, handbooks)
3. ~~email (policy announcements)
4. ~~chat (policy discussions)

决策类查询（如“我们之前的决定是...”）：

1. ~~chat（决策通常在此类对话中产生）
2. ~~email（决策确认、公告）
3. ~~cloud storage（会议纪要、决策日志）
4. 维基（若决策已被记录）
5. 任务追踪器（若决策已被纳入任务）

状态类查询（如“...的状态是什么？”）：

1. 任务追踪器（~~project tracker — 权威状态来源）
2. ~~chat（实时讨论内容）
3. ~~cloud storage（状态文档、报告）
4. ~~email（状态更新邮件）
5. 维基（项目页面）

文档类查询（如“...的文档在哪里？”）：

1. ~~cloud storage（主要文档存储位置）
2. 维基 / ~~knowledge base（知识库）
3. ~~email（通过邮件分享的文档）
4. ~~chat（在频道中分享的文档）
5. 任务追踪器（关联到任务的文档）

人员类查询（如“谁负责...？”/“谁了解...？”）：

1. ~~chat（消息作者、频道成员）
2. 任务追踪器（任务负责人）
3. ~~cloud storage（文档作者、协作者）
4. ~~CRM（客户账户负责人、联系人）
5. ~~email（邮件参与者）

事实/政策类查询（如“我们的...政策是什么？”）：

1. 维基 / ~~knowledge base（官方文档）
2. ~~cloud storage（政策文档、手册）
3. ~~email（政策公告）
4. ~~chat（政策相关讨论）

Default Priority (General Queries)

默认优先级（通用查询）

When query type is unclear:

1. ~~chat (highest volume, most real-time)
2. ~~email (formal communications)
3. ~~cloud storage (documents and files)
4. Wiki / ~~knowledge base (structured knowledge)
5. Task tracker (work items)
6. CRM (customer data)

当无法明确查询类型时：

1. ~~chat（数据量最大、最实时）
2. ~~email（正式沟通内容）
3. ~~cloud storage（文档和文件）
4. 维基 / ~~knowledge base（结构化知识）
5. 任务追踪器（工作项）
6. CRM（客户数据）

Rate Limiting Awareness

限流感知

MCP sources may have rate limits. Handle them gracefully:

MCP源可能存在限流限制，需妥善处理：

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

限流响应通常表现为：

HTTP 429 响应
包含“rate limit”“too many requests”或“quota exceeded”的错误信息
响应被节流或延迟

Handling

处理

When a source is rate limited:

Do not retry immediately — respect the limit
Continue with other sources — do not block the entire search
Inform the user:

Note: [Source] is temporarily rate limited. Results below are from
[other sources]. You can retry in a few minutes to include [source].

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

避免不必要的API调用 — 在查询前先判断该源是否可能包含相关结果
尽可能使用针对性查询而非广泛扫描
对于摘要生成，在API支持的情况下批量请求
缓存感知：若刚执行过某搜索，避免立即重复执行相同查询

Source Health

源健康状态

Track source availability during a session:

Source Status:
  ~~chat:        ✓ Available
  ~~email:        ✓ Available
  ~~cloud storage:  ✓ Available
  ~~project tracker:        ✗ Not connected
  ~~CRM:   ✗ Not connected
  ~~knowledge base:      ⚠ Rate limited (retry in 2 min)

When reporting search results, include which sources were searched so the user knows the scope of the answer.

在会话期间追踪源的可用性：

源状态：
  ~~chat:        ✓ 可用
  ~~email:        ✓ 可用
  ~~cloud storage:  ✓ 可用
  ~~project tracker:        ✗ 未连接
  ~~CRM:   ✗ 未连接
  ~~knowledge base:      ⚠ 已限流（2分钟后可重试）

在返回搜索结果时，需注明已搜索的源，让用户了解答案的覆盖范围。

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:

Add the MCP server configuration to
```
.mcp.json
```
Authenticate if required
The source will be included in subsequent searches automatically

企业搜索插件可与任何MCP连接的源配合使用。当有新的MCP服务器可用时，可将其添加到

.mcp.json

配置中。搜索和摘要命令会自动基于可用工具检测并纳入新源。

添加新源的步骤：

将MCP服务器配置添加到
```
.mcp.json
```
中
若需要，完成身份验证
后续搜索会自动纳入该源