Supabase MCP Server
Servidor MCP de Supabase
Este es un servidor de Protocolo de contexto de modelo (MCP) que se conecta a Supabase y le permite consultar la tabla feature_suggestions.
Prerrequisitos
Node.js (v16 o superior)
npm
Proyecto Supabase con credenciales
Related MCP server: Supabase MCP Server
Configuración
Asegúrese de que su archivo
.envcontenga las siguientes credenciales de Supabase:SUPABASE_URL=your_supabase_url SUPABASE_ANON_KEY=your_supabase_anon_keyInstale las dependencias necesarias:
npm install
Ejecución del servidor
Ejecute el servidor MCP usando:
npx tsx mcp-server.tsO utilice el script npm:
npm run devConexión a herramientas de IA
Cursor
Abra el Cursor y navegue hasta Configuración del Cursor .
En la pestaña Características , toque + Agregar nuevo servidor MCP en la sección Servidores MCP .
Introduzca los siguientes datos:
Nombre : Supabase
Tipo : comando
Comando :
npx tsx /path/to/mcp-server.ts
Debería ver un estado activo verde después de que el servidor se haya conectado exitosamente.
Escritorio de Claude
Abra el escritorio de Claude y navegue hasta Configuración .
En la pestaña Desarrollador , toque Editar configuración para abrir el archivo de configuración.
Agregue la siguiente configuración:
{ "mcpServers": { "supabase": { "command": "npx", "args": ["tsx", "/path/to/mcp-server.ts"] } } }Guarde el archivo de configuración y reinicie el escritorio Claude.
Herramientas disponibles
sugerencias de funciones de consulta
Consulta la tabla feature_suggestions en tu base de datos Supabase.
Parámetros:
limit(número, opcional): número máximo de registros a devolver (predeterminado: 100)
Ejemplo de uso en herramienta de IA:
Can you show me feature suggestions from the database?O con un límite:
Can you show me the top 10 feature suggestions?Solución de problemas
Si encuentra problemas de conexión, asegúrese de que sus credenciales de Supabase sean correctas.
Verifique la salida de la consola para ver si hay mensajes de error.
Asegúrese de que la tabla feature_suggestions exista en su base de datos Supabase.
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.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- First observed
query_feature_suggestions
TDQS
Scored across 1 tool
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
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 gradedqualityDmaintenanceA Model Context Protocol server that enables Claude and other LLMs to perform database operations and invoke Edge Functions within Supabase through natural language.798 npm4MIT
- 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-