Skip to main content
Glama
adiletD

Supabase MCP Server

by adiletD

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

  1. Asegúrese de que su archivo .env contenga las siguientes credenciales de Supabase:

    SUPABASE_URL=your_supabase_url
    SUPABASE_ANON_KEY=your_supabase_anon_key
  2. Instale las dependencias necesarias:

    npm install

Ejecución del servidor

Ejecute el servidor MCP usando:

npx tsx mcp-server.ts

O utilice el script npm:

npm run dev

Conexión a herramientas de IA

Cursor

  1. Abra el Cursor y navegue hasta Configuración del Cursor .

  2. En la pestaña Características , toque + Agregar nuevo servidor MCP en la sección Servidores MCP .

  3. Introduzca los siguientes datos:

    • Nombre : Supabase

    • Tipo : comando

    • Comando : npx tsx /path/to/mcp-server.ts

  4. Debería ver un estado activo verde después de que el servidor se haya conectado exitosamente.

Escritorio de Claude

  1. Abra el escritorio de Claude y navegue hasta Configuración .

  2. En la pestaña Desarrollador , toque Editar configuración para abrir el archivo de configuración.

  3. Agregue la siguiente configuración:

    {
      "mcpServers": {
        "supabase": {
          "command": "npx",
          "args": ["tsx", "/path/to/mcp-server.ts"]
        }
      }
    }
  4. 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 tool
query_feature_suggestionsD
ParametersJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of records to return

TDQS

D1/5.0
Behavior1/5

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.

Conciseness1/5

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.

Completeness1/5

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.

Parameters1/5

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.

Purpose1/5

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.

Usage Guidelines1/5

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. 1 tool update
    • First observedquery_feature_suggestions

TDQS

D1.7/5.0

Scored across 1 tool

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness1/5

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

ActivityInactive
ResponsivenessNo issues

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    D
    maintenance
    A Model Context Protocol server that enables Claude and other LLMs to perform database operations and invoke Edge Functions within Supabase through natural language.
    798 npm
    4
    MIT
  • F
    license
    A
    quality
    D
    maintenance
    A 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.
    21
    1
    -