From dfe26d802c69771202fff8dc7fa13c20b2ddfc56 Mon Sep 17 00:00:00 2001
From: Taryn King <49492414+tk1ng@users.noreply.github.com>
Date: Mon, 4 Aug 2025 10:24:26 -0500
Subject: [PATCH] Update Postgres MCP server reference link (#36604)

The resource has been moved to an archived repo named `servers-archived`
---
 apps/docs/content/guides/getting-started/mcp.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/apps/docs/content/guides/getting-started/mcp.mdx b/apps/docs/content/guides/getting-started/mcp.mdx
index 181d012da19..c1a4e0ba38c 100644
--- a/apps/docs/content/guides/getting-started/mcp.mdx
+++ b/apps/docs/content/guides/getting-started/mcp.mdx
@@ -241,7 +241,7 @@ We recommend the following best practices to mitigate security risks when using
 
 ## MCP for local Supabase instances
 
-The Supabase MCP server connects directly to the cloud platform to access your database. If you are running a local instance of Supabase, you can instead use the [Postgres MCP server](https://github.com/modelcontextprotocol/servers/tree/main/src/postgres) to connect to your local database. This MCP server runs all queries as read-only transactions.
+The Supabase MCP server connects directly to the cloud platform to access your database. If you are running a local instance of Supabase, you can instead use the [Postgres MCP server](https://github.com/modelcontextprotocol/servers-archived/tree/main/src/postgres) to connect to your local database. This MCP server runs all queries as read-only transactions.
 
 ### Step 1: Find your database connection string