query_feature_suggestionsLABSCO 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
limiton how many records come back, defaulting to 100 - One table and one operation, so the credentials in play reach nothing else
- A Claude Desktop configuration that runs
npx tsxagainst mcp-server.ts in your clone
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.
Setup effort
Build from source — git clone https://github.com/adiletD/feature-request-collection-mcp.git
USE CASES
01
Reviewing feedback while planning
Pull recent suggestions into the conversation where the roadmap is being written.
02
Summarising what users keep asking for
Read a batch of rows and have the assistant group them by theme.
03
Checking a request already exists
Query the table before adding something that duplicates an open suggestion.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Requires
- Node.js
- SUPABASE_ANON_KEY in your environment
- SUPABASE_URL in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/adiletD/feature-request-collection-mcp.git
cd feature-request-collection-mcpCreate a .env file with your Supabase credentials: SUPABASE_URL=<YOUR_SUPABASE_URL> and SUPABASE_ANON_KEY=<YOUR_SUPABASE_ANON_KEY>.
TERMINAL
npm installMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"supabase": {
"command": "npx",
"args": [
"tsx",
"<YOUR_PATH_TO_FEATURE_REQUEST_COLLECTION_MCP>/mcp-server.ts"
]
}
}
}The server reads .env from the folder it is started in, and a client usually starts it somewhere else. If it cannot find your Supabase credentials, set command to the repository's run-mcp.sh (with no args) — that script changes into the project folder before running npx tsx mcp-server.ts.
The configuration on this page does not set SUPABASE_ANON_KEY and SUPABASE_URL; the project's instructions put them in a .env file. Check which folder the server reads that file from before you rely on it.
