Skip to main content
Glama
enesjakozh
adiletD

Supabase MCP Server

by adiletD
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Supabase MCP 서버

이는 Supabase에 연결하고 feature_suggestions 테이블을 쿼리할 수 있는 MCP(Model Context Protocol) 서버입니다.

필수 조건

  • Node.js(v16 이상)

  • 엔피엠

  • 자격 증명이 있는 Supabase 프로젝트

Related MCP server: Supabase MCP Server

설정

  1. .env 파일에 다음 Supabase 자격 증명이 포함되어 있는지 확인하세요.

    지엑스피1

  2. 필요한 종속성을 설치하세요:

    npm install

서버 실행

다음을 사용하여 MCP 서버를 실행합니다.

npx tsx mcp-server.ts

또는 npm 스크립트를 사용하세요.

npm run dev

AI 도구에 연결

커서

  1. 커서를 열고 커서 설정 으로 이동합니다.

  2. 기능 탭에서 MCP 서버 섹션 아래에 있는 + 새 MCP 서버 추가를 탭합니다.

  3. 다음 세부 정보를 입력하세요.

    • 이름 : 수파베이스

    • 유형 : 명령

    • 명령 : 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