Supabase MCP Server
Allows querying of the feature_suggestions table in a Supabase database, with optional limits on the number of records returned.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Supabase MCP Servershow me the latest 5 feature suggestions"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Supabase MCP Server
This is a Model Context Protocol (MCP) server that connects to Supabase and allows you to query the feature_suggestions table.
Prerequisites
Node.js (v16 or higher)
npm
Supabase project with credentials
Related MCP server: Supabase MCP Server
Setup
Make sure your
.envfile contains the following Supabase credentials:SUPABASE_URL=your_supabase_url SUPABASE_ANON_KEY=your_supabase_anon_keyInstall the required dependencies:
npm install
Running the Server
Run the MCP server using:
npx tsx mcp-server.tsOr use the npm script:
npm run devConnecting to AI Tools
Cursor
Open Cursor and navigate to Cursor Settings.
Under the Features tab, tap + Add new MCP server under the MCP Servers section.
Enter the following details:
Name: Supabase
Type: command
Command:
npx tsx /path/to/mcp-server.ts
You should see a green active status after the server is successfully connected.
Claude Desktop
Open Claude desktop and navigate to Settings.
Under the Developer tab, tap Edit Config to open the configuration file.
Add the following configuration:
{ "mcpServers": { "supabase": { "command": "npx", "args": ["tsx", "/path/to/mcp-server.ts"] } } }Save the configuration file and restart Claude desktop.
Available Tools
query_feature_suggestions
Query the feature_suggestions table in your Supabase database.
Parameters:
limit(number, optional): Maximum number of records to return (default: 100)
Example usage in AI tool:
Can you show me feature suggestions from the database?Or with a limit:
Can you show me the top 10 feature suggestions?Troubleshooting
If you encounter connection issues, make sure your Supabase credentials are correct.
Check the console output for any error messages.
Ensure that the feature_suggestions table exists in your Supabase database.
Available Tools
1 toolquery_feature_suggestionsD
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of records to return |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
TDQS
With only one tool, there is no possibility of confusion or overlap between tools, as there are no other tools to compare it against. The single tool's purpose is inherently distinct by default.
Since there is only one tool, naming consistency is trivially perfect—there are no other tool names to compare it to, so no inconsistencies can exist. The tool name 'query_feature_suggestions' follows a clear verb_noun pattern.
A single tool is too few for a server named 'Supabase MCP Server', which implies a database or backend service with broader functionality. This minimal toolset suggests severe under-scoping for the apparent domain, limiting agent capabilities.
The tool surface is severely incomplete for a Supabase-related server, lacking basic CRUD operations (e.g., insert, update, delete, select) or other essential database functions. With only one vague tool, agents will face significant gaps and dead ends.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
A Model Context Protocol server for Wix AI tools
Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.
- SupabaseOAuthcom.supabase
MCP server for interacting with the Supabase platform
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants to explore and interact with Cursor IDE's SQLite databases, providing access to project data, chat history, and composer information.25
- AlicenseNot gradedqualityFmaintenanceA Model Context Protocol server that enables Claude and other LLMs to perform database operations and invoke Edge Functions within Supabase through natural language.2,2234MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI tools to interact with Supabase databases, providing tools for reading, creating, updating, and deleting records in Supabase tables.MIT
- FlicenseAqualityDmaintenanceA Model Context Protocol server that enables interaction with self-hosted Supabase instances, allowing developers to query database schemas, manage migrations, inspect statistics, and interact with Supabase features directly from MCP-compatible development environments.211
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/adiletD/feature-request-collection-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server