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

Collaboration tools spent the week wiring themselves into AI agents over MCP — as both client and server.

mcpai-agentsenterprise-governancemodel-agnosticdeveloper-platform
Y
By Yahya Tür
LinkedIn ↗
Generated 1h agoDrawn from 13 products

The week in collaboration

The dominant move this week was structural, not cosmetic: collaboration products stopped treating AI as a feature bolted onto the UI and started treating the Model Context Protocol as a two-way port. GitHub, Slack, Document360, and Whimsical all shipped work that makes their surfaces either callable by external agents, capable of calling external tools themselves, or both. The throughline is distribution and control — meeting users inside ChatGPT, Claude, and coding agents rather than pulling them into a tab, while giving administrators the levers to govern what those agents can do.

The second, quieter story is the platform plumbing underneath. GitHub paired its agent-provider work with a heavy dose of enterprise governance — marketplace restrictions, npm account hardening, break-glass credential controls — a reminder that the companies furthest along on agents are also the ones building the guardrails first. Meanwhile Rocket.Chat spent the week on architectural debt, migrating client traffic off Meteor's DDP toward REST, and Skedda kept turning physical touchpoints into self-serve terminals. Different problems, same instinct: control the surface, then open it.

Leaders

GitHub had the highest-signal week in the sector. Copilot now supports bring-your-own-key, letting teams run agent sessions against OpenAI, Azure, Anthropic, and other providers instead of GitHub's default model — turning the assistant into a model-agnostic host. In parallel it previewed Claude as an agent provider inside JetBrains IDEs and added organization-scoped agents, all while hardening enterprise governance (npm account protection, strict marketplace allowlists, credential revocation). Shipping the agent platform and its guardrails in the same window is the tell.

Slack moved on both ends of the MCP wire. The new Slackbot MCP Client lets Slackbot invoke external tools over MCP, extending the built-in assistant into an agent that reaches user-chosen tools; the developer changelog also expanded Slack's MCP server tools and added data-rich Block Kit primitives. Slack wants to be both an MCP host and an MCP server, which is the most complete version of the week's pattern.

Document360 pushed its knowledge base from AI-readable to AI-operable. Its MCP server now lets a connected assistant manage the full content lifecycle — assign reviewers, move articles through workflow stages, publish and unpublish — without anyone returning to the portal. For a docs platform, conceding that the human may never open the editor is a real directional bet.

Skedda kept widening from desk booking toward workplace operations. Tablet Room Actions turn a passive display into an interactive terminal: walk up to book a free room, check in, or end a meeting early, with no separate login. It is the clearest expression of Skedda's strategy of making every physical touchpoint — map, kiosk, tablet, Outlook — a booking surface that removes the need to open the web app.

Miro continued converting its canvas into an AI prototyping surface, this week adding Prototype Variations: prompt-to-multiple-directions generation inside the Prototypes add-on, letting teams generate and compare options before committing. Combined with its recent MCP bridge to coding agents, Miro is positioning the canvas as the place teams align on product direction upstream of code.

Wildcards

Rocket.Chat is the off-pattern move. While the rest of the sector chased agents, Rocket.Chat spent its 8.6.0-rc.0 cycle on architecture: migrating client callers for joinRoom, blockUser, saveSettings, spotlight and more onto REST, with the legacy Meteor DDP methods deprecated and slated for removal in 9.0.0. The same release added a unified presence engine and self-hostable LibreTranslate auto-translation. It is unglamorous spine work, but it is what lets an open-source, self-hosted product decouple from its origins and expose a cleaner integration surface later — the precondition for the agent story everyone else is already telling.

Themes that compounded

  • MCP became the default integration primitive: GitHub, Slack, Document360, Whimsical, and Miro all shipped MCP client or server work in the same window.
  • The leaders are shipping AI capability and AI governance together — GitHub's marketplace and credential controls landed alongside its agent-provider preview.
  • Model-agnosticism is spreading: GitHub's BYOK and Document360's multi-assistant MCP both decline to lock users to a single model vendor.
  • Physical-world surfaces are being absorbed too — Skedda's tablet terminal extends the same "every touchpoint is our surface" logic to office hardware.
  • Several knowledge and changelog feeds in this sector (Mattermost's blog, the dormant intranet vendors Claromentis, Powell, Happeo, Staffbase, pCloud) carried only marketing or thought-leadership content this week rather than substantive releases.

Watch this week

Watch whether the MCP push moves from announcement to permissioning. The most concrete near-term tension is visible in GitHub and Document360 already: once an external agent can publish a doc or run a Copilot session against an arbitrary model, the next releases have to answer who is allowed to, against which providers, and with what audit trail. Expect the agent-forward leaders to follow this week's capability ships with scope, role, and logging controls — and watch Slack specifically, which now sits on both ends of the MCP connection and will need to govern inbound agents acting in workspaces, not just outbound tool calls.