supabase-nextjs

This MCP server implements a simple notes system for Next.js backed by Supabase. It exposes resources representing text notes (accessible via note:// URIs) with a title, content and metadata, and a set of tools to manipulate notes. The server also includes a prompt named summarize_notes that can generate a structured summary of all stored notes, embedding the notes content as resources for use in your LLM workflows. To use the server, run it locally using Node.js and connect your MCP clients through standard IO channels. The server expects environment variables for Supabase credentials so it can store and retrieve notes in your Supabase database. You can create new notes using the create_note tool by providing a title and content, and you can fetch and list notes through the note:// URIs that the server exposes.

Prerequisites:

• Node.js and npm installed on your system
• Access to a Supabase project with a database you can connect to

Install and build:

# 1) Install dependencies
npm install

# 2) Build the TypeScript server
npm run build

Run in development (with auto-rebuild on changes):

npm run watch

To use with Claude Desktop, configure the MCP server path in Claude's config (as shown in the README). The server is started via Node and the built entry at build/index.js will be executed as the MCP server process.

Debugging:

npm run inspector

This opens the MCP Inspector URL for debugging tooling.

Environment variables are required for Init: NEXT_PUBLIC_SUPABASE_URL and NEXT_PUBLIC_SUPABASE_ANON_KEY. When deploying or sharing configurations, ensure these values are kept secure. The server exposes a notes system where each note has a title, content (plaintext), and metadata. Use the create_note tool to add notes, which will persist in your Supabase backend. For debugging, MCP communicates over stdio; the Inspector can help you monitor prompts, tool invocations, and responses. If you’re wiring this server to Claude Desktop, the example config in the Installation section shows how to reference the built server entry. If you run into connectivity or authentication issues, double-check that your Supabase URL and anon key are correct and that your Supabase database is accessible from your environment.