Supabase
Supabase’s official server lets AI create tables, query data and review project settings in your Supabase database.
Description from the maker (original English)
Managed Postgres MCP: projects, SQL, docs search, and storage buckets via OAuth.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://mcp.wowsql.com/mcpRun this in your terminal
claude mcp add --transport http wowsql https://mcp.wowsql.com/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"wowsql": {
"url": "https://mcp.wowsql.com/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"wowsql": {
"type": "http",
"url": "https://mcp.wowsql.com/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://mcp.wowsql.com/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain wowsql.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 32 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Supabase, MongoDB MCP Server, Elasticsearch MCP Server
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Supabase’s official server lets AI create tables, query data and review project settings in your Supabase database.
MongoDB Model Context Protocol Server
MCP server for interacting with Elasticsearch
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
wowsql-style HTTP MCP with OAuth 2.0 authorization code + PKCE on the WoWSQL API.
| Package | Description |
|---|---|
packages/mcp-server-wowsql | @wowsql/mcp-server-wowsql — HTTP MCP server, createToolSchemas() for AI SDK |
From the repo root:
cd mcp
npm install npm run build npm start
The MCP process is an OAuth protected resource (not the authorization server):
Authorization: Bearer unless MCP_ALLOW_UNAUTHENTICATED=true (dev only).WWW-Authenticate: Bearer ... resource_metadata=" " so MCP clients (Cursor, etc.) can start OAuth.GET {WOWSQL_API_BASE}/api/v1/auth/me with the same Bearer token (must match the JWT issued by WoWSQL OAuth or login).GET {WOWSQL_API_BASE}/.well-known/oauth-authorization-serverGET /.well-known/oauth-protected-resource/mcpCursor / Electron: OAuth metadata is rewritten so authorization_endpoint, token_endpoint, and registration_endpoint point at this MCP host (e.g. http://localhost:8787/...). The MCP process proxies those requests to WOWSQL_API_BASE, so the IDE does not need a working direct fetch to localhost:8000 for OAuth (which often shows up as fetch failed). You still need FastAPI running on WOWSQL_API_BASE so the proxy can reach it.
If `MCP_PUBLIC_URL` is unset, PRM and 401 resource_metadata are derived from each request’s `Host` (and X-Forwarded-Proto), so http://localhost:8787/mcp and http://127.0.0.1:8787/mcp each get matching metadata. Set `MCP_PUBLIC_URL` when the MCP is behind a reverse proxy or you need a single fixed origin in production.
| Variable | Default | Purpose |
|---|---|---|
WOWSQL_API_BASE | https://api.wowsql.com | WoWSQL FastAPI base URL (no trailing slash). |
WOWSQL_OAUTH_ISSUER_URL | same as WOWSQL_API_BASE | issuer advertised in PRM (authorization_servers). |
MCP_PUBLIC_URL | unset | If set, fixed public origin (no /mcp path) for OAuth PRM + WWW-Authenticate; overrides Host-based derivation. |
MCP_ALLOW_UNAUTHENTICATED | unset | If true, skips Bearer check (insecure; local testing only). |
PORT / MCP_PORT | 8787 | MCP HTTP port. |
MCP_HOST | 0.0.0.0 | Bind address. |
Option A — `.env` / `.env.local` (recommended) Copy packages/mcp-server-wowsql/.env.example to .env or .env.local in that folder. The CLI loads `.env`, then `.env.local` (overrides), then the process cwd .env. Use .env.local for machine-specific values (e.g. http://localhost:8000) without committing them.
cd mcp/packages/mcp-server-wowsql
cp .env.example .env
npm run build # from mcp root: npm run build -w @wowsql/mcp-server-wowsql npm start
Option B — shell (no file)
PowerShell:
cd mcp
$env:WOWSQL_API_BASE="http://localhost:8005" $env:PORT="8787" npm start
bash / zsh:
cd mcp
export WOWSQL_API_BASE=http://localhost:8005 export PORT=8787 npm start
POST http://localhost:8787/mcp — JSON-RPC body; append query params for scoping. MCP clients (Cursor, etc.) use this.GET http://localhost:8787/mcp returns 401 with a short “not authorized” page (no public metadata). The protocol is POST JSON-RPC with Authorization: Bearer.GET http://localhost:8787/healthExample scoped URL for clients:
http://localhost:8787/mcp?project_ref= &read_only=true&features=database,docs
GET https://api.wowsql.com/.well-known/oauth-authorization-serverGET /api/v1/auth/oauth/mcp/authorizePOST /api/v1/auth/oauth/mcp/approvePOST /api/v1/auth/oauth/mcp/token (grant_type=authorization_code or refresh_token)Dashboard consent UI: /mcp/oauth on the app (see dashboard/app/mcp/oauth/page.tsx).
mcp.wowsql.comWOWSQL_API_BASE / WOWSQL_OAUTH_ISSUER_URL to `https://api.wowsql.com` (not 127.0.0.1:8000/8001). Blue/green flips change the backend host port; the public hostname always follows the active slot via NPM.MCP_PUBLIC_URL=https://mcp.wowsql.com.mcp.wowsql.com to the service; health check: GET /health.redirect_uri values include your MCP client callbacks (see oauth_clients seed + env).EC2 blue/green: ./deploy/ec2-blue-green.sh mcp sets those env vars automatically.
cd mcp/packages/mcp-server-wowsql
npm version patch npm publish --access public
Requires an npm org scope @wowsql (or change name in package.json).