Get the FREE Ultimate OpenClaw Setup Guide →

mcp-directory

discover MCP Servers and Clients for Claude Integration

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio go-to-sea-mcp-directory node node_modules/.bin/next dev \
  --env SUPABASE_URL="" \
  --env SUPABASE_ANON_KEY="" \
  --env NEXT_PUBLIC_WEB_URL="http://localhost:3000"

How to use

This MCP server provides a frontend directory of MCP Servers and Clients for Claude integration. It exposes a web UI where you can discover, browse, and preview available MCP endpoints that can be consumed by Claude or other MCP-enabled clients. The app relies on a Supabase database for storing server/client metadata and uses Next.js to render the frontend. To use it, start the dev server to load the local dataset, then navigate to the provided web URL to explore the MCP directory, view server details, and initiate any supported interactions or demos documented in the UI. Ensure your environment variables are set so the app can connect to Supabase and generate the correct public URL for client-side use.

How to install

Prerequisites:

  • Node.js (LTS) and npm or pnpm installed
  • Git installed
  • Access to a database (Supabase) and ability to run SQL scripts

Installation steps:

  1. Clone the repository
git clone https://github.com/Go-To-Sea/mcp-directory.git
cd mcp-directory
  1. Install dependencies (uses pnpm in the repo)
pnpm install
  1. Prepare the database
  • Create a Supabase project or use an existing database
  • Run the SQL setup located at data/install.sql to initialize needed tables
  1. Configure environment variables
  • Create a .env file in the project root with at least:
SUPABASE_URL=""
SUPABASE_ANON_KEY=""
NEXT_PUBLIC_WEB_URL="http://localhost:3000"
  1. Run the development server
pnpm dev
  1. Preview the site Open http://localhost:3000 in your browser to view the MCP Directory UI.

Additional notes

  • The app stores configuration and metadata in Supabase; ensure SUPABASE_URL and SUPABASE_ANON_KEY are correctly set.
  • If the Next.js dev server does not start, verify that Node.js version is compatible with the project (LTS recommended).
  • The web URL in NEXT_PUBLIC_WEB_URL should reflect where you plan to access the frontend; updating it may be necessary if deploying behind a proxy or on a different host.
  • The SQL in data/install.sql may expect a fresh database; re-run as needed when reseeding.
  • This repository uses pnpm; if you prefer npm/yarn, install dependencies accordingly and adjust scripts if necessary.

Related MCP Servers

Sponsor this space

Reach thousands of developers