Sanity outage: Sanity MCP Server Unavailability

Affected components

• MCP Server

1. resolvedMay 1, 2026, 13:19 UTC

   This incident has been resolved.

2. monitoringMay 1, 2026, 13:11 UTC

   A fix has been implemented and we are monitoring the results.

3. identifiedMay 1, 2026, 13:08 UTC

   We are continuing to work on a fix for this issue.

4. identifiedMay 1, 2026, 12:49 UTC

   We are continuing to work on a fix for this issue.

5. identifiedMay 1, 2026, 12:48 UTC

   We’ve identified the issue affecting the MCP server (mcp.sanity.io) and are actively working on a fix. We’ll share another update as soon as we have more information.

6. identifiedMay 1, 2026, 12:46 UTC

   We are implementing a fix that should resolve the issue.

7. investigatingMay 1, 2026, 12:00 UTC

   Our MCP server (mcp.sanity.io) is currently inoperative, returning 500 errors and impacting access via tools like Claude and Cursor. We are working to restore functionality.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Sanity's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Snyk: Snyk recurring tests showing slow performanceMinor · Apr 21, 2026, 18:58 UTC
• Akamai: Intermittent Edge Delivery Delays in Chennai, IN (MAA) RegionMinor · Apr 28, 2026, 16:42 UTC
• Linode: Service Issue - Connectivity Issues - Chennai (IN-MAA)Minor · Apr 28, 2026, 17:17 UTC
• Akamai: Reporting Issues affecting URL Traffic and URL Responses reportsMinor · Apr 29, 2026, 05:19 UTC
• Intercom: Investigating: Compromised version of intercom-client npm package and intercom-phpMinor · Apr 30, 2026, 16:58 UTC

How often does Sanity have incidents?

Sanity reported 10 incidents in the last 90 days, 3 of them major or critical. A typical incident lasted 52 min. See Sanity's uptime and incident history