Supabase Nextjs MCP Server

A Model Context Protocol server

Local serverstdioTypeScript

What is the Supabase Nextjs MCP server?

Supabase Nextjs MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. A Model Context Protocol server.

What you get

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

What the assistant can call

Once Supabase Nextjs is connected, these are the calls the assistant has available:

  • create_note — Create new text notes
  • Init — The Init tool exposed by this server
  • Resources — The Resources tool exposed by this server
  • Tools — The Tools tool exposed by this server
  • Prompts — The Prompts tool exposed by this server
  • Debugging — Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP

Setting it up

The server ships on npm as @smithery/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Configuration and credentials

You will need 2 environment variables: NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Supabase Nextjs's toolset — create_note, Init, Resources and 3 more — is a fair guide to whether it matches your workflow. It is maintained by tengfone; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the supabase nextjs mcp server does with a few real requests.

Available tools

ToolWhat it does
create_noteCreate new text notes
InitThe Init tool exposed by this server.
ResourcesThe Resources tool exposed by this server.
ToolsThe Tools tool exposed by this server.
PromptsThe Prompts tool exposed by this server.
DebuggingSince MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector), which is available as a package script:

How to install the Supabase Nextjs MCP server

{
  "mcpServers": {
    "supabase-nextjs": {
      "command": "npx",
      "args": ["-y", "@smithery/cli"],
      "env": {
        "NEXT_PUBLIC_SUPABASE_URL": "your-value",
        "NEXT_PUBLIC_SUPABASE_ANON_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
NEXT_PUBLIC_SUPABASE_URLEndpoint or connection string the server talks to.Yes
NEXT_PUBLIC_SUPABASE_ANON_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Supabase Nextjs to create note.
  • Use Supabase Nextjs to Init.
  • Use Supabase Nextjs to Resources.

Frequently asked questions

It connects Supabase Nextjs to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (create_note, Init, Resources, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Supabase Nextjs directly.