Summary
Narrow on purpose.
One table, one read, one optional limit — which makes it a good shape to copy when you want an assistant to see a specific dataset and nothing around it. It uses the anon key, so what it can actually read is whatever your row-level security allows that key.
What it is
A small MCP server that connects to Supabase and queries a single table of feature suggestions. It exists so product feedback can be read inside the conversation where you are deciding what to build.
What you get
- The feature suggestions table queried directly — `query_feature_suggestions`
- A `limit` on how many records come back, defaulting to 100
- One table and one operation, so the credentials in play reach nothing else
- Setup documented for both Cursor and Claude Desktop, using the same `npx tsx` command
Requirements
A Supabase project with a `feature_suggestions` table, and its credentials in `.env` as `SUPABASE_URL` and `SUPABASE_ANON_KEY`. Node v16 or higher with `npm install`, then run it as `npx tsx mcp-server.ts` — the client entry points at that file by absolute path.