# I can't seem to get MCP working with my Supabase

**URL:** <https://forum.cursor.com/t/i-cant-seem-to-get-mcp-working-with-my-supabase/53542>\
**Category:** Help\
**Created:** [February 23, 2025, 6:39pm UTC](https://forum.cursor.com/t/i-cant-seem-to-get-mcp-working-with-my-supabase/53542 "2025-02-23T18:39:11Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Luma](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/luma/32/20272_2.png) [@Luma](https://forum.cursor.com/u/Luma)\
**Post date:** [February 23, 2025, 6:39pm UTC](https://forum.cursor.com/t/i-cant-seem-to-get-mcp-working-with-my-supabase/53542/1 "2025-02-23T18:39:11Z")

</div>

I’m trying to get it to work with my hosted supabase server.  
I followed the guide 1-to-1. But It’s stuck at no tools available.  
As an alternative I tried docker too but that also didn’t work.  
Do I need a specific version of Node for this to work?  
Running the MCP server did work fine with other tools other than supabase

---

<div class="post-metadata">

**Author:** ![anonix98](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/anonix98/32/13764_2.png) [@anonix98](https://forum.cursor.com/u/anonix98)\
**Post date:** [February 27, 2025, 7:56pm UTC](https://forum.cursor.com/t/i-cant-seem-to-get-mcp-working-with-my-supabase/53542/2 "2025-02-27T19:56:29Z")

</div>

i have the same problem on my mac

---

<div class="post-metadata">

**Author:** ![anonix98](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/anonix98/32/13764_2.png) [@anonix98](https://forum.cursor.com/u/anonix98)\
**Post date:** [February 28, 2025, 12:10pm UTC](https://forum.cursor.com/t/i-cant-seem-to-get-mcp-working-with-my-supabase/53542/3 "2025-02-28T12:10:56Z")

</div>

could some one solve this problem?  
or is the supabasesserver connection actually working on someones cursor?

---

<div class="post-metadata">

**Author:** ![Luma](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/luma/32/20272_2.png) [@Luma](https://forum.cursor.com/u/Luma)\
**Post date:** [February 28, 2025, 12:23pm UTC](https://forum.cursor.com/t/i-cant-seem-to-get-mcp-working-with-my-supabase/53542/4 "2025-02-28T12:23:00Z")

</div>

The only thing that solved it for me was running it outside as a terminal  
by using the command like this.

`cmd /c npx -y @modelcontextprotocol/server-postgres <connection-string>`

---

<div class="post-metadata">

**Author:** ![anonix98](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/anonix98/32/13764_2.png) [@anonix98](https://forum.cursor.com/u/anonix98)\
**Post date:** [March 2, 2025, 12:44am UTC](https://forum.cursor.com/t/i-cant-seem-to-get-mcp-working-with-my-supabase/53542/5 "2025-03-02T00:44:44Z")

</div>

can the composer or chat access the MCP that runns in the terminal?

---

<div class="post-metadata">

**Author:** ![Luma](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/luma/32/20272_2.png) [@Luma](https://forum.cursor.com/u/Luma)\
**Post date:** [March 3, 2025, 10:48am UTC](https://forum.cursor.com/t/i-cant-seem-to-get-mcp-working-with-my-supabase/53542/6 "2025-03-03T10:48:19Z")

</div>

yes. just follow the steps in the supabase guide except you add cmd /c in front of the command instead of just npx and it will work. It’s read-only but that’s miles better than nothing. Alternatively there is which is even better but I haven’t managed to get it to work [GitHub - alexander-zuev/supabase-mcp-server: Supabase MCP Server enabling Cursor & Windsurf to use any method from Management API and query your database](https://github.com/alexander-zuev/supabase-mcp-server?tab=readme-ov-file#getting-started)

---

<div class="post-metadata">

**Author:** ![Nando](https://avatars.discourse-cdn.com/v4/letter/n/77aa72/32.png) [@Nando](https://forum.cursor.com/u/Nando)\
**Post date:** [October 29, 2025, 2:30pm UTC](https://forum.cursor.com/t/i-cant-seem-to-get-mcp-working-with-my-supabase/53542/7 "2025-10-29T14:30:58Z")

</div>

It’s probably a cache-related issue.

Run this on the terminal:

npx clear-npx-cache 2\>&1
