Skip to main content
Glama
enesjakozh
adiletD

Supabase MCP Server

by adiletD
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Supabase MCP サーバー

これは、Supabase に接続し、feature_suggestions テーブルをクエリできる Model Context Protocol (MCP) サーバーです。

前提条件

  • 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. カーソルを開き、カーソル設定に移動します。

  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