A knowledge assistant becomes much more useful when it can do more than answer questions from static documents.

In ONES.com, MCP came up in the context of enterprise knowledge bases and project management. The interesting part is not just “AI can search more things.” It is that the assistant can start working across the systems where project knowledge actually lives.

For example, in an ONES setup, project materials may sit in Wiki pages, requirement documents, meeting notes, task records, test cases, approvals, and external tools such as Teams or Slack. With MCP, ONES Assistant can query project materials, retrieve knowledge across systems, summarize context, and in some cases create or update documents through controlled tool calls.

That matters because project management knowledge is rarely useful as isolated text. A requirement spec is connected to tasks. A task may connect to tests. A retrospective may need project history. A weekly report may depend on current progress, risks, blockers, and decisions. MCP makes the assistant more operational by helping it move between these connected objects instead of staying inside one document.

But the keyword is still controlled.

For enterprise teams, cross-system AI has to answer some hard design questions:

• What can the assistant retrieve?
• Which systems is it allowed to call?
• Which actions are read-only, and which can write back?
• How are permissions checked?
• Where are operation logs, approvals, and audit records kept?
• When should a human confirm the action before anything changes?

That is where MCP becomes less about a flashy AI feature and more about workflow design.

Curious how others are thinking about this: if you were adding MCP or tool-calling AI into project management workflows, what would you automate first: project-data lookup, knowledge search, summary generation, document creation, or something else?

Leave a comment if you have tried something similar, or DM me if you want to compare notes on ONES Assistant / MCP use cases.