Skip to main content
Glama
enesjakozh
adiletD

Supabase MCP Server

by adiletD
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Supabase MCP 服务器

这是一个连接到 Supabase 的模型上下文协议 (MCP) 服务器，它允许您查询 feature_suggestions 表。

先决条件

  • Node.js（v16 或更高版本）

  • npm

  • 具有凭证的 Supabase 项目

Related MCP server: Supabase MCP Server

设置

  1. 确保您的.env文件包含以下 Supabase 凭据：

    SUPABASE_URL=your_supabase_url
SUPABASE_ANON_KEY=your_supabase_anon_key

  2. 安装所需的依赖项：

    npm install

运行服务器

使用以下方式运行 MCP 服务器：

npx tsx mcp-server.ts

或者使用 npm 脚本：

npm run dev

连接到AI工具

光标

  1. 打开 Cursor 并导航至Cursor Settings 。

  2. 在**“功能”选项卡下，点击“MCP 服务器”**部分下的“ + 添加新的 MCP 服务器” 。

  3. 输入以下详细信息：

    • 名称: Supabase

    • 类型：命令

    • 命令： npx tsx /path/to/mcp-server.ts

  4. 服务器成功连接后，您应该会看到绿色的活动状态。

克劳德桌面

  1. 打开 Claude 桌面并导航到**“设置”** 。

  2. 在开发人员选项卡下，点击编辑配置以打开配置文件。

  3. 添加以下配置：

    {
  "mcpServers": {
    "supabase": {
      "command": "npx",
      "args": ["tsx", "/path/to/mcp-server.ts"]
    }
  }
}

  4. 保存配置文件并重新启动Claude桌面。

可用工具

查询功能建议

查询 Supabase 数据库中的 feature_suggestions 表。

参数：

  • limit （数字，可选）：返回的最大记录数（默认值：100）

AI工具中的使用示例：

Can you show me feature suggestions from the database?

或者设置一个限制：

Can you show me the top 10 feature suggestions?

故障排除

  • 如果您遇到连接问题，请确保您的 Supabase 凭据正确。

  • 检查控制台输出是否有任何错误消息。

  • 确保您的 Supabase 数据库中存在 feature_suggestions 表。

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
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

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

Resources

Related MCP Connectors

Related MCP Servers

  • Supabase MCP Server

    Cappahccino
    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

  • Self-Hosted Supabase MCP

    abushadab
    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
    -

Appeared in Searches