Agent-readable docs index: /llms.txt. Full docs in one file: /llms-full.txt. Download /docs.zip to grep all markdown files locally.

MCP updates

This page follows changes to the Model Context Protocol that affect how companies connect AI clients to their systems. We separate released protocol features from roadmap ideas and update the page as the boundary changes.
Last reviewed: August 22, 2026
General event triggers for PSA tickets, RMM alerts, backups, and security findings are not live in Stackyapper. No new customer event feed, webhook, or background polling is enabled by this work.

August 22, 2026 — Events are the next important boundary

The current MCP protocol revision is 2026-07-28. It adds a stateless protocol model, improved discovery, longer-running request patterns, and a subscription stream for defined MCP notifications.
The important distinction is scope: the released subscriptions/listen pattern can carry changes such as tool, prompt, and resource-list updates. It is not yet a general subscription API for business events such as a ticket change, an RMM alert, or a failed backup.
General-purpose Triggers and Events are active roadmap and working-group work. That direction is especially promising for MSPs, but it is not a released interoperability contract yet.

What is available in MCP today

  • Protocol revision 2026-07-28: a released protocol revision with a stateless serving model, explicit version negotiation, improved discovery, and authorization updates.
  • Subscriptions: clients can explicitly listen for supported MCP notifications. Both sides must support the notification being requested.
  • Tasks: a separately negotiated extension for work that continues beyond one request. Its standalone specification remains labeled Draft and its reference implementation remains Experimental. A client can check progress, provide requested input, or cancel when both sides support the extension.
  • MCP Apps: an official extension for interactive interfaces inside supporting AI clients. Client support varies.

What Stackyapper supports now

Stackyapper connects supported AI clients to approved tools in connected business systems. It helps the client find the relevant approved tool, then checks the workspace, signed-in user, connection, and tool permission again before the request runs. Risk and confirmation rules still apply to actions.
Stackyapper's newer stateless MCP path is being tested separately from the established production compatibility path. It is not enabled for customer traffic simply because a newer protocol revision or SDK package exists.

What we can prepare before general event support lands

Most of the difficult event work does not depend on the final MCP method names:
  • define stable event types for ticket, alert, backup, identity, connector, and long-running-work changes;
  • bind every event and subscription to the correct company or managed-customer workspace;
  • verify provider webhooks or use carefully limited polling where a provider supports it;
  • deduplicate repeated delivery, preserve ordering, keep replay bounded, and stop delivery promptly after access is revoked;
  • send only a small change notice, then fetch current details through an approved Stackyapper tool;
  • support signed webhooks, n8n, or a portal timeline before AI clients broadly support general MCP events;
  • add the final MCP adapter after the specification and real client behavior are known.
The first preparation step defines and validates this event vocabulary. It does not accept, store, stream, or display customer event data.

Why this matters for MSPs

Request-and-response MCP is useful when a person or agent already knows it needs to ask. Events can close the other half of the loop:
  • a critical RMM alert can start triage;
  • a failed backup can open recovery work;
  • a PSA priority change can cause the current ticket to be reassessed;
  • a completed remediation job can return control to the right person or agent;
  • an approval request can surface without constant polling.
An event should announce that something changed; it should not authorize an action. The recipient should fetch current data, and Stackyapper should check access and confirmation policy before anything else happens.

Is this “MCP v2”?

There is no officially named “MCP v2” protocol. The current protocol revision is 2026-07-28. Separately, the TypeScript SDK now has v2 packages.
Changing an SDK dependency does not automatically switch a server to the new wire behavior. Protocol support, version negotiation, client compatibility, and production rollout still need to be tested independently. It also does not make the general Triggers and Events work available.

Official references

Builder commentary we are watching

Rhys Sullivan's posts are useful signals about where MCP builders see value. They are commentary, not the protocol source of truth:
Powered byHolocron