MCP server with Supabase integration
Feature Request Collection MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP server with Supabase integration.
This is a Model Context Protocol (MCP) server that connects to Supabase and allows you to query the feature_suggestions table.
Installation goes through your MCP client rather than a global install: point it at tsx on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Once Feature Request Collection MCP is connected, these are the calls the assistant has available:
Cursor — 1. Open Cursor and navigate to Cursor Settings. 2. Under the Features tab, tap + Add new MCP server under the MCP Servers section. 3query_feature_suggestions — Query the feature_suggestions table in your Supabase databaseYou will need 2 environment variables: SUPABASE_URL, SUPABASE_ANON_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Feature Request Collection MCP's toolset — Cursor, query_feature_suggestions — is a fair guide to whether it matches your workflow. It is maintained by adiletD; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Feature Request Collection MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Cursor | 1. Open Cursor and navigate to **Cursor Settings**. 2. Under the **Features** tab, tap **+ Add new MCP server** under the **MCP Servers** section. 3. Enter the following details: - **Name**: Supabase - **Type**: command |
| query_feature_suggestions | Query the feature_suggestions table in your Supabase database. |
{
"mcpServers": {
"supabase": {
"command": "npx",
"args": ["tsx", "/path/to/mcp-server.ts"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| SUPABASE_URL | Endpoint or connection string the server talks to. | Yes |
| SUPABASE_ANON_KEY | Credential the server authenticates with. | Yes |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.