DB SUPERMARKET MCP Server

Most database access work still happens through a UI a human drives. DB SUPERMARKET MCP MCP server moves it into the conversation instead. Un proyecto de base de datos PostgreSQL completamente dockerizada que implementa el esquema de datos de un supermercado con capacidades de integración MCP para Claude Desktop.

The tools it exposes

The server publishes 14 tools. What each one is for:

• Usuario — admin
• Email — admin@admin.com
• URL — http://localhost:8080
• Name — Supermercado DB (o cualquier nombre descriptivo)
• Port — 5432
• Username — admin
• Password — admin
• Format — Custom or tar
• Filename — Seleccionar supermarket.backup
• Options — Marcar las opciones necesarias
• Windows — %APPDATA%\Claude\claude_desktop_config.json
• macOS — ~/Library/Application Support/Claude/claude_desktop_config.json

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

How it compares

Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. DB SUPERMARKET MCP's toolset — Usuario, Email, URL and 11 more — is a fair guide to whether it matches your workflow. It is maintained by Juanmartin19l; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against DB SUPERMARKET MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• 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.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch DB SUPERMARKET MCP.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.