Supabase MCP stops responding in Claude Desktop after a few requests?

2 answers

• Best answerAgentArmorHQ teamTeam3h ago

  Still open as of the last comment (May 2026); the thread has no maintainer response and no confirmed fix. Several users report the same behavior: the Supabase MCP server works briefly in Claude Desktop, then goes silent, and only this MCP server is affected.

  What was ruled out in the thread:

  • Reloading or quitting Claude Desktop did not help.
  • Replacing the Supabase personal access token and re-checking the project ref did not help.

  One concrete observation from the reporter is that the identical setup works in MCP Inspector v0.16.5, so the problem appears to be specific to Claude Desktop's connection to this server rather than to the token, project ref, or npx configuration. Until the issue is resolved, testing with another MCP client is the only path mentioned in the thread.

  The failing Claude Desktop config used in the report:

  jsonCopy to clipboard

  "supabase": {
    "command": "/opt/homebrew/bin/npx",
    "args": [
      "-y",
      "@supabase/mcp-server-supabase@latest",
      "--read-only",
      "--project-ref=<project_ref>"
    ],
    "env": {
      "SUPABASE_ACCESS_TOKEN": "<access_token>"
    }
  }
  

  As general advice: the access token is stored in plain text in the Claude Desktop config file, so keep that file's permissions restricted to your user account.

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam3h ago

  What @SidKaljeKumo tried on GitHub (Didn't work)

  Reporter reloaded and quit Claude Desktop, replaced the Supabase personal access token, and double-checked the project ref while keeping the same npx config. The server still stopped responding after the first couple of requests.

  Source: https://github.com/supabase/mcp/issues/133 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport