Skip to main content
Glama
adiletD

Supabase MCP Server

by adiletD

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

  1. Make sure your .env file contains the following Supabase credentials:

    SUPABASE_URL=your_supabase_url
    SUPABASE_ANON_KEY=your_supabase_anon_key
  2. Install the required dependencies:

    npm install

Running the Server

Run the MCP server using:

npx tsx mcp-server.ts

Or use the npm script:

npm run dev

Connecting to AI Tools

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

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

  4. You should see a green active status after the server is successfully connected.

Claude Desktop

  1. Open Claude desktop and navigate to Settings.

  2. Under the Developer tab, tap Edit Config to open the configuration file.

  3. Add the following configuration:

    {
      "mcpServers": {
        "supabase": {
          "command": "npx",
          "args": ["tsx", "/path/to/mcp-server.ts"]
        }
      }
    }
  4. 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 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.

TDQS

D1.7/5.0
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
ResponsivenessSyncing

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

Related MCP Servers

  • 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

Latest Blog Posts

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