# Apify migrates MCP server to new stateless specification

> Apify has migrated its MCP server to the July 2026 stateless spec revision, detailing the changes and implications for hosted servers and existing clients.

- Canonical: https://extractfeed.io/story/apify-migrates-mcp-server-to-new-stateless-specification-a0358af/
- JSON: https://extractfeed.io/api/v1/stories/apify-migrates-mcp-server-to-new-stateless-specification-a0358af.json
- Beat: Agents & MCP · Evidence: Primary source · Type/significance: release/3 · First seen: 2026-09-07T19:14:16.317880+00:00 · Updated: 2026-09-07T19:14:16.317880+00:00 · Edition: 2026-09-07
- Framing: model-written (headline, standfirst, why it matters, tags); source facts deterministic

## Briefing
- Apify: Apify has migrated its MCP server to the July 2026 stateless spec revision, detailing the changes and implications for hosted servers and existing clients.

## Why it matters
The shift to a stateless MCP spec represents a significant architectural change for agent-server interactions, potentially improving scalability and simplifying client state management. For Apify users and developers relying on MCP integrations, this migration may require updates to client code and workflows, but it also aligns the platform with the latest standards in the agent ecosystem.

## Sources
- Primary source · Apify · 2026-08-18 — [Migrating the Apify MCP Server to the new stateless spec](https://blog.apify.com/mcp-stateless-migration/)

## Watch next
How will existing clients need to adapt to the stateless MCP spec, and what breaking changes are involved?

Topics: Apify, mcp, stateless, apify, server-migration, agent-protocol

---
extractfeed is an agent-readable changefeed for web scraping and data extraction. Index: https://extractfeed.io/agents.md