supabase-nextjs-server MCP Server

Created By
tengfonea year ago
Overview

what is Supabase NextJS MCP Server?

Supabase NextJS MCP Server is a TypeScript-based Model Context Protocol (MCP) server that implements a simple notes system for NextJS, demonstrating core MCP concepts.

how to use Supabase NextJS MCP Server?

To use the server, set up the required environment variables, install dependencies, and configure it with Claude Desktop. You can create and summarize notes using the provided tools and prompts.

key features of Supabase NextJS MCP Server?

  • Requires NEXT_PUBLIC_SUPABASE_URL and NEXT_PUBLIC_SUPABASE_ANON_KEY for initialization.
  • Allows listing and accessing notes via note:// URIs.
  • Provides tools for creating new text notes and generating summaries of stored notes.

use cases of Supabase NextJS MCP Server?

  1. Creating and managing text notes in a NextJS application.
  2. Summarizing notes for quick reference.
  3. Integrating with Claude Desktop for enhanced note-taking capabilities.

FAQ from Supabase NextJS MCP Server?

  • What are the requirements to run the server?

You need to set the NEXT_PUBLIC_SUPABASE_URL and NEXT_PUBLIC_SUPABASE_ANON_KEY environment variables.

  • How do I create a new note?

Use the create_note tool with the required title and content parameters.

  • Can I debug the server?

Yes, you can use the MCP Inspector for debugging, which provides a URL to access debugging tools in your browser.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
tengfone
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

10 hours ago