zed -supabase

This MCP server extension integrates Supabase MCP with Zed, enabling you to expose and manage project-scoped data through Zed's Agent Panel. Once configured, the extension authenticates with Supabase using your access token and exposes a context server named mcp-server-supabase that Zed can query and interact with. You can control access scope via the read_only flag and optionally limit operations to a specific Supabase project using the project_ref setting. Use the Agent Panel to explore, query, and manipulate MCP-backed data as defined by Supabase MCP, which includes collaboration-friendly data access and real-time capabilities depending on your Supabase configuration.

Prerequisites:

• Node.js and npm installed on your system
• Zed editor installed and running
• A Supabase access token with appropriate MCP permissions

1. Install the MCP server extension for Zed via the command line or Zed Extensions marketplace (the extension integrates as an MCP context server).

2. If using the command line, install the MCP server package via npx (as configured here):

   • Ensure you have an active internet connection.
   • Run from a suitable directory: npx -y mcp-server-supabase

3. In Zed, add the MCP context server configuration by editing your settings to include:

   { "context_servers": { "mcp-server-supabase": { "settings": { "supabase_access_token": "<YOUR_SUPABASE_ACCESS_TOKEN>", "read_only": false } } } }

4. If you want to restrict access to a specific Supabase project, extend the settings with:

   { "context_servers": { "mcp-server-supabase": { "settings": { "supabase_access_token": "<YOUR_SUPABASE_ACCESS_TOKEN>", "supabase_project_ref": "<PROJECT_REF>", "read_only": true } } } }

5. Save the configuration and restart Zed if necessary. Open the Agent Panel and select the mcp-server-supabase context to begin using Supabase MCP's capabilities within Zed.

Tips and guidance:

• Keep your Supabase access token secure and rotate it periodically according to your organization's security policies.
• The supabase_project_ref option scopes MCP access to a single project; omit it to allow broader access depending on your token scopes.
• The read_only flag prevents write operations; set it to true for collaboration scenarios where edits should be restricted.
• If you encounter authentication errors, verify token validity, token scope, and that the tokens are entered correctly in the Zed settings.
• Ensure network connectivity to Supabase endpoints; firewall rules or VPNs might affect MCP communication.
• When upgrading, re-check the extension configuration in Zed to ensure the token and project reference (if used) remain valid.
• This setup is powered by Supabase MCP; consult the Supabase MCP documentation for project-scoped capabilities and data models relevant to your workspace.