Sandbox
@clidey/whodb

Database workspace with CLI and MCP server

WhoDB lets you browse tables, edit rows, run SQL, inspect relationships, and move data in and out. It works as a browser app, desktop app, and terminal CLI, and its MCP server lets AI tools talk to your databases.

5,022 stars238 forksGoUpdated 7d ago
Who it's for

Builders who want one place to inspect databases, edit records, and use an agent-friendly database tool.

What it delivers

You can explore and update databases without switching between a heavy client, the browser, and your terminal.

What it does

Browse and edit data

Spreadsheet-style tables with sorting, filtering, pagination, and inline editing.

Visual schema graph

An interactive graph shows tables and relationships so you can understand the schema at a glance.

Query scratchpad

A multi-cell SQL workspace with autocomplete, history, and results shown beside each query.

Import, export, and mock data

Tools for moving data in and out and generating sample rows for development and testing.

Plain-English AI chat

Connect local or hosted providers like Ollama, OpenAI, Anthropic, LM Studio, or other OpenAI-compatible services.

CLI and MCP server

Terminal access through `whodb` and agent access through `whodb mcp serve`.

How to get it

  1. 1Run WhoDB with Docker
    docker run --rm -it -p 8080:8080 clidey/whodb
  2. 2The one-line Docker command is ideal for trying WhoDB. To keep encrypted login sessions…
    openssl rand -hex 32
  3. 3Then mount /data and reuse that key whenever you start the container
    docker run -it -p 8080:8080 \
      -v whodb-data:/data \
      -e WHODB_ENCRYPTION_KEY=your_saved_64_character_hex_key \
      clidey/whodb
  4. 4The CLI includes an interactive terminal UI and an MCP server for AI tools
    # macOS and Linux
    curl -fsSL https://raw.githubusercontent.com/clidey/whodb/main/cli/install/install.sh | bash
    
    # or install with npm
    npm install -g @clidey/whodb
  5. 5Run
    whodb             # open the terminal UI
    whodb mcp serve   # start the MCP server

README

WhoDB

MCP Toplist

A lightweight, self-hosted workspace for your databases

Release workflow Release version Release date Total downloads Docker size

Commits per month Last commit Contributors Closed issues Closed PRs

License GitHub stars Go TypeScript

Available on

Docker Windows macOS Snap CLI

Quick start · Documentation · Live demo · Community

WhoDB showing a database table

WhoDB gives you one place to explore your databases, edit data, run queries, and understand how a schema fits together. It runs in the browser, is easy to self-host, and is available as a desktop app or terminal CLI too.

Use it when you want to inspect a local database, help a teammate explore unfamiliar data, or work without installing a heavyweight database client. AI features are optional: connect Ollama, OpenAI, Anthropic, LM Studio, or another OpenAI-compatible provider if you want to ask questions in plain English.

Quick start

Run WhoDB with Docker:

docker run --rm -it -p 8080:8080 clidey/whodb

Then open http://localhost:8080 and enter your database connection details.

Want to look around first? Try the live demo or watch the video walkthrough.

What you can do

  • Browse and edit data in a spreadsheet-style grid with sorting, filtering, pagination, and inline editing.
  • Understand a schema visually with an interactive graph of tables and relationships.
  • Work through queries in a scratchpad with multiple cells, autocomplete, history, and results kept alongside each query.
  • Move data in and out with imports, exports, and mock-data generation for development and testing.
  • Ask questions in plain English using a local or hosted AI provider that you choose.
  • Work from your terminal through the WhoDB CLI and its MCP server.
Browsing rows in the WhoDB data grid Exploring database relationships in the WhoDB schema graph
Browse, filter, and edit dataFollow relationships through the schema graph

Supported databases

WhoDB Community supports:

  • PostgreSQL, CockroachDB, YugabyteDB, and QuestDB
  • MySQL, MariaDB, and TiDB
  • SQLite and DuckDB
  • MongoDB and FerretDB
  • Redis, Valkey, and Dragonfly
  • Elasticsearch and OpenSearch
  • ClickHouse and Memcached

Support varies by database because not every system has the same concepts or capabilities. The connection screen shows the options available for each source.

Installation options

Docker with persistent sessions

The one-line Docker command is ideal for trying WhoDB. To keep encrypted login sessions when the container is replaced, first generate a key and save it somewhere secure:

openssl rand -hex 32

Then mount /data and reuse that key whenever you start the container:

docker run -it -p 8080:8080 \
  -v whodb-data:/data \
  -e WHODB_ENCRYPTION_KEY=your_saved_64_character_hex_key \
  clidey/whodb

Keep that key somewhere safe. Changing it invalidates existing sessions. If WhoDB is served through an HTTPS reverse proxy, also set WHODB_SECURE=true so browsers only send the session cookie over HTTPS.

See the documentation for Docker Compose, connection profiles, SSL, AI providers, and other configuration options.

Desktop

CLI and MCP server

The CLI includes an interactive terminal UI and an MCP server for AI tools:

# macOS and Linux
curl -fsSL https://raw.githubusercontent.com/clidey/whodb/main/cli/install/install.sh | bash

# or install with npm
npm install -g @clidey/whodb
whodb             # open the terminal UI
whodb mcp serve   # start the MCP server

See the CLI guide for connection examples and the full command reference.

AI providers

You can add a hosted AI provider directly from WhoDB—no backend configuration or restart is required. Open Chat, choose Add Provider from the provider menu, then select OpenAI, Anthropic, or Gemini and enter your API key. WhoDB will fetch the available models from that provider.

Ollama and LM Studio are available as local options in WhoDB Community. By default, the backend looks for Ollama at localhost:11434 and LM Studio at localhost:1234/v1, with local addresses adjusted automatically for Docker and WSL. Use WHODB_OLLAMA_HOST, WHODB_OLLAMA_PORT, or WHODB_LMSTUDIO_BASE_URL only when those defaults are not suitable for your setup.

Optional backend provider configuration

Environment variables let deployment administrators declare providers when the server starts. This is useful for preconfiguring OpenAI or Anthropic, changing provider endpoints, or adding an OpenAI-compatible service for everyone using that deployment:

  • WHODB_OPENAI_* for OpenAI
  • WHODB_ANTHROPIC_* for Anthropic
  • WHODB_OLLAMA_* for Ollama connection settings
  • WHODB_LMSTUDIO_* for LM Studio connection settings
  • WHODB_AI_GENERIC_<ID>_* for OpenAI-compatible providers

See the installation guide for the complete environment variable list and the AI provider guide for setup examples.

WhoDB Community and WhoDB Platform

This repository contains WhoDB Community, the Apache-2.0-licensed database workspace described above. It is free to self-host and is the best place to start if you want to explore and work with databases.

WhoDB Platform is the commercial, self-hosted edition for organizations that need shared projects, more data sources, SSO, fine-grained access controls, audit logs, pipelines, reporting, and internal apps. You can read the WhoDB overview or compare plans on the pricing page.

Development

WhoDB has a Go backend and a React/TypeScript frontend. For local development, run them in separate terminals.

Requirements:

  • Go
  • Node.js and pnpm

Start the backend:

cd core
go run ./cmd/whodb

Start the frontend:

cd frontend
pnpm install
pnpm start

The frontend opens at http://localhost:3000 and talks to the backend on port 8080. See the CE build and run guide for generation and build commands.

Contributing

Bug reports, feature ideas, documentation improvements, and code contributions are all welcome.

More screenshots

See WhoDB in action

Query scratchpad

Writing queries in the WhoDB scratchpad

Add and edit records

Adding a row in WhoDB

Build filters visually

Building WHERE conditions in WhoDB

Export data

Exporting data from WhoDB

Support

WhoDB is licensed under the Apache License 2.0.

If WhoDB saves you time, consider giving the project a star.

Files in the repo

Repository payload44 top-level entries
  • .agents
  • .claude
  • .codegraph
  • .codex
  • .github
  • .impeccable
  • .vscode
  • badges
  • cli
  • core
  • desktop-ce
  • desktop-common
  • dev
  • docs
  • frontend
  • sdk
  • .claudeignore
  • .gitattributes
  • .gitignore
  • .gitleaks.toml
  • .gitmodules
  • .trivyignore
  • AGENTS.md
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
  • CONTRIBUTING.md
  • DESIGN.md
  • ee
  • generate-docs-screenshots.sh
  • generate-microsoft-store-logos.sh
  • glama.json
  • go.work
  • go.work.desktop-ce
  • go.work.desktop-ce.sum
  • go.work.sum
  • LICENSE
  • logo.png
  • medusa.yml
  • NOTICE
  • PRODUCT.md
  • README.md
  • SECURITY.md
  • snapcraft.yaml
  • tidy-go-mods.sh

Discussion (0)

Ask about usage, or say what you built with it

Sign in to join the discussion.

No comments yet. Be the first to say what this is good for.

More tools

JuliusBrussee/
caveman

🪨 why use many token when few token do trick — Claude Code skill that cuts 65% of tokens by talking like caveman

105k
1 add
MemPalace/
mempalace

The best-benchmarked open-source AI memory system. And it's free.

59k
stablyai/
orca

Orca is the ADE for working with a fleet of parallel agents. Run any coding agent with your own subscription. Available on desktop, mobile and remote runtime.

66k

A cross-platform desktop All-in-One assistant for Claude Code, Codex, OpenCode, OpenClaw, Grok Build & Hermes Agent. Only official website: ccswitch.io

132k

Never stop coding. Free MIT AI gateway: one endpoint, 352 providers (150+ free), 1200+ models Kimi, Claude, GPT, Gemini, GLM, DeepSeek, MiniMax. Works with Claude Code, Codex, Cursor, OpenCode, Cline & Copilot. Quota-aware auto-fallback, RTK+Caveman compression saves 15-95% tokens, MCP/A2A, Desktop/PWA. Built by 550+ contributors

64k
headroomlabs-ai/
headroom

Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.

71k