LoginSign Up
← Back to Collab
Weekly · Collab · Week of September 28, 2026

Knowledge and collaboration tools raced to wire their content layers into the AI agent surface, with MCP servers landing at SiYuan, Nuclino, and AFFiNE in the same week.

mcp-servers-in-knowledge-toolscollaborative-editing-catching-upai-economics-tieringpkm-as-agent-infrastructure
Y
Generated 11h agoDrawn from 6 products

The week in collaboration

The dominant pattern this week: collaboration tools are treating their content layers as agent infrastructure. SiYuan went furthest, upgrading its MCP server to OAuth 2.1 and connecting the Bazaar plugin marketplace to the agent layer. Nuclino shipped a native MCP server. AFFiNE tightened its AI Copilot MCP visibility controls. Three PKM/collaboration tools, three MCP releases, same week. The pattern has moved past early adopter.

The rest of the week shows collaborative editing catching up to where teams already expect it to be. Wiki.js 3 added live Excalidraw collaboration and SCIM provisioning in beta. Document360 shipped simultaneous multi-author editing — a feature the platform has needed for years. These aren't strategic surprises; they're table stakes arriving.

Leaders

SiYuan shipped two MCP releases in quick succession this week. Alpha.7 added OAuth 2.1 to the built-in MCP server — the auth protocol that production AI agent frameworks require before they'll integrate with a tool. Alpha.10 connected the Bazaar plugin marketplace to the MCP agent layer, giving AI agents the same plugin discovery and invocation access that human users have. Together these moves cross a meaningful threshold: SiYuan's MCP integration graduates from dev prototype to something frameworks will actually connect to.

Wiki.js 3 is visibly approaching production readiness. Beta.605 shipped Excalidraw with live multi-user collaboration — the first real-time diagramming capability in Wiki.js 3 — alongside SCIM provisioning for automated user management and a first-pass v2 migration tool. Beta.583 added blog pages and a native comments system, extending the product surface into CMS territory. Both releases together suggest Wiki.js 3 is closing its remaining feature gaps fast, and the v3 production release is no longer a distant milestone.

Document360 shipped simultaneous multi-author editing in v12.8.4. For a knowledge base platform that started as a solo-author tool, this is a structural shift in the collaboration model: multiple contributors can now work on the same article in real time. The redesigned navigation and unified project menu in v12.8.5 followed, addressing the multi-workspace friction that teams with more than one Document360 project had been managing around.

Wildcards

Double restructured its AI economics with a tiered model: a Standard tier 93% cheaper than Expert for routine tasks, with Expert (Claude Opus 5) reserved for complex work. Most AI-assisted tools have charged uniform rates; Double made the model tier a user-facing dial. For teams using Ask Double heavily for routine operations, the savings are real enough to change adoption behavior.

Themes that compounded

  • MCP servers shipped or updated at SiYuan, Nuclino, and AFFiNE this week — every PKM/knowledge tool with an active development team now appears to be treating agent access as a required integration, not an optional feature.
  • Real-time collaborative editing arrived at Document360 — functionality teams have expected for years in knowledge base platforms finally shipping at a product that has historically been single-author.
  • Wiki.js 3's beta cadence has clearly shifted into a production-prep mode: multiple meaningful features per beta cycle, SCIM, live collaboration, v2 migration tooling all landing within two releases.
  • AI model pricing pressure appeared explicitly in Double's tiered release — the 93% cost gap between Standard and Expert is large enough to restructure how collaboration AI features get deployed.

Watch this week

SiYuan's OAuth 2.1 MCP server is still in alpha; watch which AI agent frameworks announce integrations first, since that's a leading indicator of whether the PKM-as-agent-infrastructure thesis holds with framework developers. On the wiki side, watch Wiki.js 3's release cadence — the v2 migration tool shipping suggests the maintainers are actively working to pull existing deployments forward, which typically precedes a stable v3 announcement.