LoginSign Up
← Back to Collab
Weekly · Collab · Week of July 6, 2026

Collaboration tools open up to agents over MCP — and rush to govern them

mcpagent-governanceexternal-agentsai-operable-docsmodel-choice
Y
By Yahya Tür
LinkedIn ↗
Generated 1h agoDrawn from 10 products

The week in collaboration

One thread runs through nearly every real release this week, and it isn't a feature — it's a protocol. MCP has become the default way collaboration tools open themselves to external AI agents, and the sector has split cleanly into products acting on that shift and products blogging around it. Slack shipped agent context and a Slackbot MCP client; Notion's 3.6 lets external agents like Claude take assigned tasks off a shared board; Document360, Avoma, Outline, and Claap all made their content or meeting data readable — and in several cases writable — by outside assistants over MCP. The move is consistent: stop being a destination UI, start being an addressable data source and action surface that agents drive.

The second pattern is governance catching up to that surface. GitHub, the sector's highest-throughput feed, spent the week almost entirely on Copilot administration — agent session streaming for observability, per-cost-center credit pools, model deprecations, and a hard shutdown date for standalone GitHub Models. Notion shipped admin credit limits and auto-pausing for runaway agents; Shortcut added coarse-grained API token scopes ahead of an agent-oriented v4. Once agents can act inside these tools, the next release is always about who can run them, on which model, and for how much spend. That is where the leaders are converging.

Leaders

GitHub led on volume and direction with six sparks, all Copilot: agent session streaming entered public preview, Kimi K2.7 Code became the first open-weight model in the picker, and Claude Sonnet 5 reached GA — while GitHub Models was given a July 30 shutdown. The changelog now reads as an enterprise AI control plane, not an IDE feed.

Slack posted two sparks that together form an agent platform: agent context hands an app whatever channel, thread, or canvas the user is looking at, and the new Slackbot MCP client lets the built-in assistant call external tools. Context in, tools out — the two halves of a runtime for third-party agents, backed by richer Block Kit primitives to render the output.

Notion shipped 3.6 with External Agents, letting teams @-mention Claude and Cursor and assign them tasks from a shared board, on top of May's 3.5 Developer Platform and its hosted Workers runtime. The paired admin release — per-agent credit limits, spend dashboards, auto-pausing — shows Notion betting that orchestration and governance, not the model, is where it adds value.

Claap folded contact-email capture and MCP-readable smart tables into one per-deal timeline, with enrichment writing back into HubSpot. Two sparks moved it from meeting recorder to a deal-conversation layer that sits above the CRM and exposes that context to any MCP client.

Document360 extended its MCP server from search-and-read to the full content lifecycle — assign reviewers, move articles through workflow, publish — and added auto-generated llms.txt for agent discoverability. Two sparks that push the knowledge base from AI-readable to AI-operable.

Wildcards

Teable ran a near-daily open-source cadence, with one spark adding a generic HTTP connector and a chat-driven Airtable import via an /airtable skill, feeding its Agent Computer and App Builder. It is building an AI application platform on a no-code database rather than following the MCP-interop script.

Mattermost is the counter-current: no sparks and a feed dominated by zero-trust thought leadership, but the real signal underneath is v11.8 — classification banners, data-spillage reporting, mobile ephemeral mode — aimed at defence and sovereign deployments where the sector's open-to-external-agents push is exactly the wrong direction.

Themes that compounded

  • MCP became the sector's default agent interface, exposing knowledge bases, meeting data, and CRM context as readable and increasingly writable surfaces.
  • Agent governance — credit caps, spend dashboards, scoped tokens, auto-pausing, session streaming — landed as the necessary companion to agent capability.
  • Model choice widened, with GitHub adding its first open-weight option and Notion expanding its roster while consolidating away from standalone model catalogs.
  • Wikis and knowledge bases (Outline, Document360, SiYuan) leaned into being AI-operable rather than human-only, via MCP write access and extensibility.
  • A large share of the sector's "changelog" feeds are marketing blogs with no product signal, inflating velocity without shipping anything.

Watch this week

The open question is whether governance keeps pace with reach. Every leader this week paired a new agent surface with a new control — GitHub's session streaming, Notion's auto-pausing, Shortcut's scoped tokens — and the products that only opened the surface without the guardrails are the ones to watch for friction next. Expect the MCP write-access thread (Outline, Document360, Claap) to force the permissions conversation, and watch whether Slack connects its two halves — agent context feeding MCP tool calls — into a single loop. Mattermost's defence-first stance is the reminder that not every buyer wants their collaboration data made agent-addressable.