Skip to main content

Developer policy

SlideDrift API versioning and deprecation policy.

This page is the public lifecycle contract for SlideDrift's OAuth-protected JSON API, MCP interface, and machine-readable discovery resources. It explains what can change safely, how breaking changes are announced, and how clients learn when an older HTTP resource is being retired.

Active migration

Use the canonical MCP endpoint.

The canonical Streamable HTTP endpoint is nowhttps://slidedrift.com/mcp. The previous/api/mcpendpoint remains available temporarily for migration.

Deprecated
24 August 2026
Scheduled sunset
30 November 2026
Replacement
https://slidedrift.com/mcp

Versioning

SlideDrift negotiates the MCP protocol version during initialize and honors MCP-Protocol-Version on subsequent HTTP requests. Additive tools and optional fields may be introduced within the current implementation version. Breaking tool, authentication, or transport changes require a new implementation version and a documented migration path.

Notice period

SlideDrift gives at least 90 days of public notice before removing a supported agent operation or required field. During that period, affected HTTP operations are documented as deprecated and return Deprecation and Sunset headers where the transport can represent them. Security, legal, or active-abuse issues may require a shorter emergency window.

Runtime signals

A deprecated HTTP resource returns the standards-based Deprecation header. When a removal date is scheduled, it also returns Sunset. A Link header with rel="deprecation" points to this policy, and rel="successor-version" identifies the supported replacement when one exists.

Migration guidance

SlideDrift publishes the replacement URL and migration deadline before removing a supported surface. Clients should update stored server URLs, reconnect OAuth when the protected resource identifier changes, and confirm the current endpoint in server.json before the sunset date.