Skip to main content
Glama
Sign In
enesjakozh
Supabase NextJS MCP Server

Supabase NextJS MCP Server

by tengfone
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

supabase-nextjs-server MCP Server

A Model Context Protocol server

This is a TypeScript-based MCP server that implements a simple notes system for NextJS. It demonstrates core MCP concepts by providing:

  • Resources representing text notes with URIs and metadata

  • Tools for creating new notes

  • Prompts for generating summaries of notes

Features

Init

  • Require NEXT_PUBLIC_SUPABASE_URL and NEXT_PUBLIC_SUPABASE_ANON_KEY environment variables

Resources

  • List and access notes via note:// URIs

  • Each note has a title, content and metadata

  • Plain text mime type for simple content access

Tools

  • create_note - Create new text notes

    • Takes title and content as required parameters

    • Stores note in server state

Prompts

  • summarize_notes - Generate a summary of all stored notes

    • Includes all note contents as embedded resources

    • Returns structured prompt for LLM summarization

Related MCP server: MCP Server

Development

Install dependencies:

npm install

Build the server:

npm run build

For development with auto-rebuild:

npm run watch

Installation

To use with Claude Desktop, add the server config:

On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json On Windows: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "supabase-nextjs-server": {
      "command": "/path/to/supabase-nextjs-server/build/index.js"
    }
  }
}

Installing via Smithery

To install Supabase Notes for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @tengfone/supabase-nextjs-mcp-server --client claude

Debugging

Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a package script:

npm run inspector

The Inspector will provide a URL to access debugging tools in your browser.

Available Tools

4 tools
delete_recordC

Delete a record from Supabase

Inputs: table (required), filters (required).

insert_recordC

Insert a record into Supabase

Inputs: table (required), data (required).

query_dataC

Query data from Supabase

Inputs: table (required), select, filters.

update_recordC

Update a record in Supabase

Inputs: table (required), filters (required), data (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting a specific CRUD operation: delete, insert, query, and update. There is no overlap or ambiguity between these fundamental database operations, making tool selection straightforward for an agent.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (delete_record, insert_record, query_data, update_record) with perfect uniformity. The naming convention is predictable and readable throughout the set.

    Tool Count5/5

    With exactly 4 tools covering the core CRUD operations for a database server, this is well-scoped and appropriate. Each tool earns its place with no redundancy or missing essentials for basic data manipulation.

    Completeness5/5

    The tool set provides complete CRUD coverage for the Supabase database domain: create (insert), read (query), update, and delete. There are no obvious gaps for basic data operations, ensuring agents can handle full lifecycle workflows without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers

    Appeared in Searches