WhoDB CLI

An interactive, production-ready command-line interface for WhoDB with a Claude Code-like experience.

Features

• Interactive TUI - Terminal UI built with Bubble Tea
• Multi-Database Support - PostgreSQL, MySQL/MariaDB, SQLite, MongoDB, Redis, ClickHouse, ElasticSearch
• Table Browser - Navigate schemas and tables with visual grid layout
• WHERE Builder - Build AND-based filters for table browsing
• SQL Editor - Multi-line editor with schema-aware autocomplete
• AI Chat - Optional AI-assisted querying with consent gate (requires configured provider)
• Responsive Data Viewer - Paginated results with horizontal column scrolling
• Column Selection - Choose which columns are visible in results
• Export Capabilities - Export to CSV and Excel formats
• Schema Diff - Compare schema metadata across environments in the CLI and TUI
• Cloud Discovery - Inspect configured cloud providers and discovered cloud-managed resources from the CLI
• Discovered Connect - Prefill connect/save flows directly from discovered cloud resources
• ERD Graph Output - Inspect backend graph metadata from the CLI or TUI
• Explain Plans - Run database-native EXPLAIN from the CLI or TUI
• Backend Query Suggestions - Shared onboarding suggestions in the CLI and TUI editor
• Bookmarks and Profiles - Shared saved queries and connection profiles across CLI and TUI
• Workspace Restore - Resume your last reconnectable TUI session on startup
• Query History - Persistent history with re-execution
• Shell Completion - Bash/Zsh/Fish install plus PowerShell script generation
• Programmatic Mode - JSON/NDJSON/CSV/plain output plus streamed query/export paths for scripting and automation
• Hosted Platform Commands - Browser login, workspace selection, manifest inspection, and hosted source management
• Agent Manifest - Machine-readable command, source, MCP, workflow, and safety metadata
• Database Doctor - Redacted connection and metadata diagnostics for support and AI agents
• Built-in Runbooks - Repeatable workflows for connection checks, schema audits, and schema diffs
• Assistant Integration Installer - Install bundled WhoDB skills, agents, MCP configs, and rule files into local assistant directories
• MCP Server - Model Context Protocol server for AI assistants (Claude, Cursor, etc.)

Installation

Native Install (Recommended)

macOS / Linux:

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

Windows (PowerShell):

irm https://raw.githubusercontent.com/clidey/whodb/main/cli/install/install.ps1 | iex

The native installer:

• Detects your OS and architecture
• Downloads the correct binary from GitHub releases
• Installs to ~/.local/bin (macOS/Linux) or %LOCALAPPDATA%\WhoDB\bin (Windows)
• Adds to PATH if needed

Linux note: if the WhoDB desktop snap is installed, it also provides a whodb command at /snap/bin/whodb. Which one runs depends on your PATH order.

Renamed from whodb-cli: the command used to be whodb-cli. The installer, Homebrew formula, npm package, and Docker image all still provide a deprecated whodb-cli alias that prints a warning and forwards to whodb. The alias will be removed in a future release — update any scripts or configs to use whodb.

To install a specific version:

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

# Windows
$env:WHODB_VERSION = "v0.62.0"; irm https://raw.githubusercontent.com/clidey/whodb/main/cli/install/install.ps1 | iex

Homebrew (macOS/Linux)

brew install whodb-cli

The formula is named whodb-cli (the whodb name is used by the desktop app cask), but it installs the whodb command.

npm

npm install -g @clidey/whodb

Or with npx (no install):

npx @clidey/whodb

From Source

Requires Go 1.21+:

git clone https://github.com/clidey/whodb.git
cd whodb/cli
go build -o whodb .

Or using the Makefile:

cd cli
make build
make install  # installs to /usr/local/bin

Using Docker

# Build the Docker image (from repo root)
docker build -t whodb-cli:latest -f cli/Dockerfile .

# Or pull pre-built
docker pull clidey/whodb-cli:latest

Verify Installation

whodb --version
whodb --help

Quick Start

For hosted WhoDB platform login and source management, see the hosted platform CLI guide.

1. Connect to a Database

If you omit required flags, the interactive connection form opens:

whodb connect

PostgreSQL

whodb connect \
  --type postgres \
  --host localhost \
  --port 5432 \
  --user postgres \
  --database mydb \
  --name my-postgres

PostgreSQL (non-interactive password)

printf "%s\n" "$PGPASSWORD" | whodb connect \
  --type postgres \
  --host localhost \
  --port 5432 \
  --user postgres \
  --database mydb \
  --name my-postgres \
  --password

PostgreSQL with SSL

whodb connect \
  --type postgres \
  --host localhost \
  --port 5432 \
  --user postgres \
  --database mydb \
  --ssl-mode verify-ca \
  --ssl-ca ./ca.pem

Discovered Cloud Resource

# Open the TUI form prefilled from discovery
whodb connect --discovered aws-prod-us-west-2/prod-db

# One-shot connect when you already know the missing credentials
whodb connect \
  --discovered aws-prod-us-west-2/prod-db \
  --user postgres \
  --database app

MySQL

whodb connect \
  --type mysql \
  --host localhost \
  --port 3306 \
  --user root \
  --database mydb \
  --name my-mysql

SQLite

whodb connect \
  --type sqlite \
  --user sqlite \
  --database /path/to/database.db \
  --name my-sqlite

MongoDB

whodb connect \
  --type mongodb \
  --host localhost \
  --port 27017 \
  --user admin \
  --database mydb \
  --name my-mongo

1b. Use Environment Profiles

Commands that accept --connection can also use environment profiles, for example WHODB_POSTGRES='[{"alias":"prod","host":"localhost","user":"user","password":"pass","database":"mydb","port":"5432"}]' or WHODB_MYSQL_1='{"alias":"dev","host":"localhost","user":"user","password":"pass","database":"devdb","port":"3306"}'. Each object supports alias (connection name), host, user, password, database, port, and optional config for advanced settings. port stays at the root level; the CLI also forwards it as the Port advanced key when building plugin credentials, so you do not need to include Port in config. Advanced config keys are plugin-specific; see core/src/plugins/*/db.go for the keys that are read.

# Array format (multiple profiles for a database type)
export WHODB_POSTGRES='[{"alias":"prod","host":"localhost","user":"user","password":"pass","database":"mydb","port":"5432"}]'

# Numbered format (one profile per variable)
export WHODB_MYSQL_1='{"alias":"dev","host":"localhost","user":"user","password":"pass","database":"devdb","port":"3306"}'

2. Start Interactive Mode

# Start the TUI (default behavior)
whodb

3. Execute a Quick Query

whodb query "SELECT * FROM users LIMIT 10" --connection my-postgres

Commands

Root Command (Interactive Mode)

Running whodb without arguments starts the interactive TUI.

whodb [flags]

Flags:

• --debug: Enable debug mode
• --no-color: Disable colored output

connect

Connect to a database and optionally save the connection. If required flags are missing, the interactive connection form opens.

whodb connect [flags]

Flags:

• --type: Database type (postgres, mysql, sqlite, mongodb, redis, clickhouse, elasticsearch, mariadb)
• --host: Database host (default: localhost)
• --port: Database port (default varies by type)
• --user: Username
• --database: Database name
• --schema: Preferred schema (optional)
• --name: Connection name (saves for later use)
• --password: Read password from stdin when not using a TTY (pipe a single line)
• --ssl-mode: SSL mode for the selected database type
• --ssl-ca: Path to a CA certificate PEM file
• --ssl-cert: Path to a client certificate PEM file
• --ssl-key: Path to a client private key PEM file
• --ssl-server-name: Override server name used for SSL hostname verification

On a TTY, you will be prompted for the password with input hidden.

query

Execute a SQL query directly. Use - to read SQL from stdin.

whodb query "SQL" [flags]

Flags:

• --connection, -c: Connection name to use (optional; if omitted, the first available connection is used)
• --format, -f: Output format: auto, table, plain, json, ndjson, csv
• --stream: Stream result rows incrementally (supported for plain, json, ndjson, and csv)
• --quiet, -q: Suppress informational messages

auto uses table output for terminals and plain output for pipes. ndjson writes one JSON object per result row.

suggestions

Show backend-generated query suggestions for a connection.

whodb suggestions --connection my-postgres
whodb suggestions --connection my-postgres --format json

Flags:

• --connection, -c: Connection name to use
• --schema, -s: Schema to use for suggestion generation
• --format, -f: Output format: table, plain, json, ndjson, csv
• --quiet, -q: Suppress informational messages

completion

Generate or install shell completion scripts.

# Show help
whodb completion

# Print completion script to stdout
whodb completion bash
whodb completion zsh
whodb completion fish
whodb completion powershell

# Install completion (auto-detects shell)
whodb completion install

# Install for specific shell
whodb completion install bash

# Uninstall completion
whodb completion uninstall

Install paths (bash/zsh rc files updated automatically):

• Bash: ~/.local/share/bash-completion/completions/whodb
• Zsh: ~/.zsh/completions/_whodb
• Fish: ~/.config/fish/completions/whodb.fish
• PowerShell: Manual install (see whodb completion powershell)

Programmatic Commands

These commands output structured data for scripting, automation, and AI integration.

• Query and list commands such as query, schemas, tables, columns, connections list, and history list/search keep their existing raw JSON array output.
• Action and analysis commands such as connections add/remove/test, history clear, audit, mock-data, diff, erd, bookmarks save/delete, and profiles save/delete return a JSON envelope with command, success, and data when you pass --format json.
• query --stream supports plain, json, ndjson, and csv. export --stream supports CSV only.

agent schema

Emit a machine-readable manifest of WhoDB's agent-facing surface. The manifest includes source types, connection fields, programmatic commands, MCP tools, platform MCP prompts/resources, safety modes, and built-in workflows.

whodb agent schema --format json

Flags:

• --format, -f: Output format: json

doctor

Run redacted connection, schema, and metadata diagnostics for one connection.

whodb doctor --connection my-postgres
whodb doctor --connection my-postgres --schema public --format json

Flags:

• --connection, -c: Connection name to inspect
• --schema, -s: Schema override for metadata checks
• --format, -f: Output format: table or json
• --quiet, -q: Suppress informational messages

runbooks

List, describe, and run built-in database workflows. Built-in runbooks are intentionally limited to WhoDB operations.

# List available workflows
whodb runbooks list

# Inspect a workflow
whodb runbooks describe schema-audit

# Show planned steps without executing
whodb runbooks run schema-audit --connection my-postgres --dry-run

# Run a schema audit
whodb runbooks run schema-audit --connection my-postgres --schema public --format json

# Compare two environments
whodb runbooks run schema-diff --from staging --to prod --format json

Built-in runbooks:

• connection-doctor: Runs the same diagnostics as doctor
• schema-audit: Loads storage units and runs data-quality checks
• schema-diff: Compares schema metadata between two connections

Flags:

• --format, -f: Output format: table or json
• --quiet, -q: Suppress informational messages
• run --connection, -c: Connection name for connection-doctor and schema-audit
• run --schema, -s: Schema override
• run --from: Source connection for schema-diff
• run --to: Target connection for schema-diff
• run --from-schema: Source schema override for schema-diff
• run --to-schema: Target schema override for schema-diff
• run --dry-run: Show planned steps without executing

skills

List bundled WhoDB assistant skills and install native assistant integrations.

# List bundled skills and agents
whodb skills list
whodb skills list --format json

# Install all skills into an explicit skills directory
whodb skills install --target-dir ~/.codex/skills

# Install one skill
whodb skills install query-builder --target-dir ~/.codex/skills

# Install skills and bundled agents for Claude Code
whodb skills install --target claude-code --include-agents

# Install native MCP configuration for an assistant
whodb skills install --target cursor
whodb skills install --target vscode
whodb skills install --target gemini-cli

# Preview files without modifying disk
whodb skills install --target cursor --dry-run

Supported targets:

Target	Files installed
codex	Skills under ~/.codex/skills
claude-code	Skills under ~/.claude/skills, plus Markdown agents under ~/.claude/agents with --include-agents
cursor	~/.cursor/mcp.json
vscode	VS Code user mcp.json
github-copilot	GitHub Copilot CLI ~/.copilot/mcp-config.json
gemini-cli	~/.gemini/extensions/whodb/gemini-extension.json and GEMINI.md
windsurf	~/.codeium/mcp_config.json
opencode	~/.config/opencode/opencode.json with mcp.whodb
cline	Cline MCP settings plus ~/Documents/Cline/Rules/whodb.md
zed	~/.config/zed/settings.json with context_servers.whodb
continue	~/.continue/config.yaml
aider	~/.aider.conf.yml plus ~/.aider/whodb-conventions.md

Existing JSON and JSONC configuration files are merged in place and rewritten as formatted JSON. Before an existing JSON or YAML assistant config is rewritten, the original file is saved beside it as <filename>.whodb.bak. Use --dry-run to preview created or updated files and any backup paths without writing changes.

Flags:

• --format, -f: Output format: table or json
• --quiet, -q: Suppress informational messages
• install --target: Assistant target to install. Supported values are listed above
• install --target-dir: Directory where skills should be installed
• install --agents-dir: Directory where agents should be installed
• install --include-agents: Install bundled Markdown agents as well as skills. With --target, this is supported for claude-code; use --agents-dir for any custom agent destination
• install --force: Overwrite existing installed files
• install --dry-run: Show files that would be written without modifying disk

explain

Run EXPLAIN using the current database plugin's native explain prefix.

whodb explain --connection my-postgres "SELECT * FROM users"
whodb explain --connection my-postgres --format json "SELECT * FROM users"

Flags:

• --connection, -c: Connection name to use
• --format, -f: Output format: auto, table, plain, json, ndjson, csv
• --quiet, -q: Suppress informational messages

schemas

List database schemas.

whodb schemas --connection my-postgres --format json

Flags:

• --connection, -c: Connection name (optional; if omitted, the first available connection is used)
• --format, -f: Output format: auto, table, plain, json, csv
• --quiet, -q: Suppress informational messages

tables

List tables in a schema.

whodb tables --connection my-postgres --schema public --format json

Flags:

• --connection, -c: Connection name (optional; if omitted, the first available connection is used)
• --schema, -s: Schema name (default varies by database)
• --format, -f: Output format: auto, table, plain, json, csv
• --quiet, -q: Suppress informational messages

columns

Describe table columns.

whodb columns --connection my-postgres --table users --format json

Flags:

• --connection, -c: Connection name (optional; if omitted, the first available connection is used)
• --table, -t: Table name (required)
• --schema, -s: Schema name
• --format, -f: Output format: auto, table, plain, json, csv
• --quiet, -q: Suppress informational messages

connections

Manage saved connections.

# List connections
whodb connections list --format json

# Test a connection
whodb connections test my-postgres --format json

# Add a connection
whodb connections add --name prod --type postgres --host db.example.com --port 5432 --user app --database mydb --format json

# Remove a connection
whodb connections remove prod --format json

Flags (applies to all subcommands):

• --format, -f: Output format: auto, table, plain, json, csv
• --quiet, -q: Suppress informational messages

cloud

Inspect configured cloud providers and discovered resources.

Cloud provider support follows the shared provider flags:

• WHODB_ENABLE_AWS_PROVIDER=true
• WHODB_ENABLE_AZURE_PROVIDER=true
• WHODB_ENABLE_GCP_PROVIDER=true

# List configured providers
whodb cloud providers list

# Test or refresh providers
whodb cloud providers test aws-prod-us-west-2
whodb cloud providers refresh --all

# List discovered resources
whodb cloud connections list
whodb cloud connections list --provider aws-prod-us-west-2

# Use a discovered resource in the normal connect/save flows
whodb connect --discovered aws-prod-us-west-2/prod-db
whodb connections add --from-discovered aws-prod-us-west-2/prod-db --user alice --database app

diff

Compare schema metadata between two connections.

By default, diff uses each connection's configured schema when one exists. For database-scoped connections such as MySQL and MariaDB, it uses the connection's configured database when no schema flag is provided.

# Compare two connections using their default schemas
whodb diff --from staging --to prod

# Compare the same schema on both sides
whodb diff --from staging --to prod --schema public

# Compare Postgres to MySQL using each connection's configured namespace
whodb diff --from dev-e2e_postgres-1 --to dev-e2e_mysql-1

# Emit machine-readable JSON
whodb diff --from staging --to prod --format json

Flags:

• --from: Source connection name (required)
• --to: Target connection name (required)
• --schema: Schema name to compare on both sides
• --from-schema: Source schema name
• --to-schema: Target schema name
• --format, -f: Output format: table or json
• --quiet, -q: Suppress informational messages

erd

Render the same backend graph metadata used by the TUI ER diagram view.

whodb erd --connection my-postgres
whodb erd --connection my-postgres --schema public --format json

Flags:

• --connection, -c: Connection name to use
• --schema, -s: Schema name
• --format, -f: Output format: text or json
• --quiet, -q: Suppress informational messages

export

Export table data or query results to file.

# Export to CSV
whodb export --connection my-postgres --table users --format csv --output users.csv

# Export to Excel
whodb export --connection my-postgres --table orders --format excel --output orders.xlsx

# Export query results
whodb export --connection my-postgres --query "SELECT * FROM users" --output users.csv

Flags:

• --connection, -c: Connection name (optional; if omitted, the first available connection is used)
• --table, -t: Table name (required unless using --query)
• --query, -Q: SQL query to export results from (use instead of --table)
• --schema, -s: Schema name
• --format, -f: Export format: csv or excel (auto-detected from filename if omitted)
• --output, -o: Output file path (required)
• --delimiter, -d: CSV delimiter (default: comma)
• --stream: Stream CSV exports incrementally to the output file
• --quiet, -q: Suppress informational messages

history

Access query history.

# List recent queries
whodb history list --limit 20 --format json

# Search history
whodb history search "SELECT.*users"

# Clear history
whodb history clear --format json

Flags:

• --limit, -l: Limit number of results (0 = no limit)
• --format, -f: Output format: auto, table, plain, json, csv
• --quiet, -q: Suppress informational messages

bookmarks

Manage the same saved query bookmarks used by the TUI editor.

whodb bookmarks list
whodb bookmarks save recent-users "SELECT * FROM users ORDER BY id DESC"
whodb bookmarks load recent-users
whodb bookmarks delete recent-users --format json

profiles

Manage the same saved connection profiles used by the TUI.

whodb profiles list
whodb profiles save production --connection prod --theme Dracula --page-size 100 --timeout 30
whodb profiles show production --format json
whodb profiles delete production --format json
whodb --profile production

MCP Server

WhoDB can run as an MCP (Model Context Protocol) server, enabling AI assistants like Claude, Cursor, and others to query your databases.

Start the MCP Server

# Default: stdio transport (for Claude Desktop, Claude Code, etc.)
whodb mcp serve

# HTTP transport (for cloud deployments, Docker, Kubernetes)
whodb mcp serve --transport=http --port=3000

This starts an MCP server that exposes these tools:

Tool	Description
whodb_connections	List available database connections
whodb_schemas	List schemas in a database (set include_tables for tables too)
whodb_tables	List tables in a schema (set include_columns for column details too)
whodb_columns	Describe table columns
whodb_query	Execute SQL queries (results include column_types)
whodb_confirm	Confirm pending write operations (only when confirm-writes is enabled)
whodb_pending	List pending write confirmations (only when confirm-writes is enabled)
whodb_explain	Run database-native EXPLAIN for a SQL query
whodb_diff	Compare schema metadata between two connections
whodb_erd	Inspect backend graph/ERD metadata
whodb_audit	Run data quality audits for a schema or table
whodb_suggestions	Get backend-generated starter queries

Start with --platform to run hosted WhoDB platform mode. In this mode, only hosted platform tools are exposed; local database tools are not registered. Local tool selection flags such as --tools and --disable-tools do not apply to platform mode.

Hosted setup:

# Sign in to app.whodb.com
whodb login

# Select the hosted workspace used by platform tools
whodb use --org <org> --project <project>

# Start stdio MCP for your MCP client
whodb mcp serve --platform

# Read-only hosted platform MCP
whodb mcp serve --platform --read-only

# Hosted writes without confirmation; use only for trusted automation
whodb mcp serve --platform --allow-write

Local or staging setup:

whodb login --host http://localhost:8080
whodb use --host http://localhost:8080 --org <org> --project <project>
whodb mcp serve --platform

Recommended MCP client behavior:

1. Read whodb://platform/tool-guide to understand the active platform MCP mode, available tool categories, field projection guidance, and write behavior.
2. Call whodb_platform_status before project-scoped reads or writes.
3. Use fields on hosted read tools whenever supported. Start narrow, for example ["id", "name", "type"], and request heavier fields only when needed.
4. For writes in default mode, explain confirmation_preview to the user and call whodb_platform_confirm only after the user approves that exact preview.
5. In --allow-write, hosted writes execute immediately, so ask the user before calling the mutating tool itself.

Most hosted read tools accept a fields array. Agents should request only the fields needed for the current answer, for example ["id", "name"], then call again with additional fields only when needed. Backend permissions still decide what the signed-in user can see or change.

Platform mode uses the same permission modes as local MCP. By default, hosted create, update, delete, and action tools return confirmation tokens and do not execute until approved with whodb_platform_confirm. --read-only and --safe-mode hide hosted write tools entirely. --allow-write executes hosted writes immediately without confirmation.

Tool	Description
whodb_platform_status	Show hosted login and selected workspace
whodb_platform_orgs	List hosted organizations visible to the signed-in user
whodb_platform_projects	List hosted projects for an organization
whodb_platform_sources	List hosted sources in the selected project
whodb_platform_source_types	List hosted source types available for creation
whodb_platform_source_fields	List connection fields for one hosted source type
whodb_platform_source_objects	Browse hosted source objects
whodb_platform_source_columns	Inspect hosted source object columns
whodb_platform_source_rows	Preview hosted source object rows
whodb_platform_source_constraints	Inspect editable source field constraints
whodb_platform_source_content	Read hosted source object content when supported
whodb_platform_source_config	Inspect redacted hosted source config
whodb_platform_source_test	Test saved or draft hosted source connections
whodb_platform_secrets	List secret metadata without secret values
whodb_platform_ai_providers	List hosted AI provider metadata without API keys
whodb_platform_ai_provider_models	List models for one hosted AI provider
whodb_platform_ontologies	List hosted ontology object types
whodb_platform_ontology	Inspect one hosted ontology object type
whodb_platform_ontology_fast_lookups	List saved fast lookups for one ontology
whodb_platform_ontology_fast_lookup_suggestions	List suggested fast lookups
whodb_platform_ontology_rows	Preview rows for one ontology
whodb_platform_ontology_follow_link	Follow one ontology link from a row
whodb_platform_datasets	List hosted datasets
whodb_platform_dataset	Inspect one hosted dataset
whodb_platform_dataset_rows	Preview hosted dataset rows
whodb_platform_lineage	Inspect lineage around one root node
whodb_platform_lineage_neighbors	Inspect immediate lineage neighbors
whodb_platform_project_lineage	Inspect project-level lineage
whodb_platform_transforms	List hosted transforms
whodb_platform_transform_runs	List recent runs for one transform
whodb_platform_functions	List hosted ontology functions
whodb_platform_function	Inspect one hosted ontology function
whodb_platform_files	List hosted project folders and files
whodb_platform_file_preview	Preview one hosted project file
whodb_platform_file_search	Search hosted project files
whodb_platform_tabular_files	List tabular hosted project files
whodb_platform_storage_usage	Show project storage usage in bytes
whodb_platform_source_create	Prepare hosted source creation for whodb_platform_confirm
whodb_platform_source_update	Prepare hosted source updates for whodb_platform_confirm
whodb_platform_source_delete	Prepare hosted source deletion for whodb_platform_confirm
whodb_platform_create	Prepare generic hosted resource creation
whodb_platform_update	Prepare generic hosted resource updates
whodb_platform_delete	Prepare generic hosted resource deletion
whodb_platform_action	Prepare generic hosted actions such as upload, move, run, deploy
whodb_platform_pending	List pending hosted platform confirmations
whodb_platform_confirm	Confirm pending hosted platform writes after user approval

Hosted create, update, delete, and action tools return confirmation tokens by default and do not execute until approved with whodb_platform_confirm. Use whodb_platform_pending to recover active confirmation tokens. Agents should explain the returned confirmation_preview to the user before confirming, especially for delete, deploy, move, and source/object changes.

Security model:

• The hosted platform remains the authorization boundary. The CLI sends the signed-in user's token and selected workspace; the backend still decides what that user may read or mutate.
• Workspace IDs are selectors, not proof of access. Pending confirmations store the host, organization, and project and re-check them before execution.
• Source config reads return redacted values, secret listing tools return metadata only, and confirmation previews include changed field names rather than credential values.

For source creation, agents should call whodb_platform_source_types and whodb_platform_source_fields first so they use backend-published source type ids and field names.

If no workspace is selected yet, agents should call whodb_platform_orgs and whodb_platform_projects, then ask the user to run whodb use --org <org> --project <project>. For single-workspace accounts, hosted login or status can select the only organization/project automatically and report what was selected.

Example hosted platform MCP config:

{
  "mcpServers": {
    "whodb-platform": {
      "command": "whodb",
      "args": ["mcp", "serve", "--platform"]
    }
  }
}

Example read-only hosted platform MCP config:

{
  "mcpServers": {
    "whodb-platform-readonly": {
      "command": "whodb",
      "args": ["mcp", "serve", "--platform", "--read-only"]
    }
  }
}

Example local or staging platform MCP config:

{
  "mcpServers": {
    "whodb-platform-local": {
      "command": "whodb",
      "args": ["mcp", "serve", "--platform"]
    }
  }
}

The server uses the single active hosted login selected by whodb login and whodb use. If you switch hosts, run login --host ... and use --host ... before starting the MCP server. The MCP server does not need a host flag because it reads the active hosted login from the CLI config.

Local MCP exposes these resources:

Resource	Description
whodb://connections	Available connection names
whodb://agent/schema	Machine-readable WhoDB agent capability manifest

Platform MCP exposes these resources instead:

Resource	Description
whodb://platform/schema	Machine-readable platform MCP contract, enabled tools, platform prompts, and platform resources
whodb://platform/workspace	Current hosted login and selected workspace metadata
whodb://platform/tool-guide	Platform tool categories, recommended usage, field projection guidance, and write behavior

The same metadata is available from whodb agent schema --format json. Its platform_mcp section describes the --platform flag, default host, login/workspace requirements, field projection support, platform-only tool prefix, platform prompts/resources, and write behavior for confirm, read-only, safe, and allow-write modes.

Write operations require confirmation by default. Use --allow-write to disable confirmations, or --read-only to block writes entirely.

Transport Modes

stdio (default) - For local CLI integration with Claude Desktop, Claude Code, etc.

whodb mcp serve

HTTP - For cloud deployments, Docker, Kubernetes, or shared access.

whodb mcp serve --transport=http --host=0.0.0.0 --port=8080

HTTP mode exposes:

• /mcp - MCP endpoint (streaming HTTP)
• /health - Health check endpoint

Security Modes

Mode	Flag	Description
Confirm-writes	(default)	Write operations require user approval
Safe mode	--safe-mode	Read-only + strict security (for demos/playgrounds)
Read-only	--read-only	Blocks all write operations
Allow-write	--allow-write	Full write access without confirmation

MCP Flags

Security:

• --safe-mode: Read-only + strict security (for demos/playgrounds)
• --read-only: Block all write operations
• --allow-write: Allow writes without confirmation (use with caution)
• --allow-drop: Allow DROP/TRUNCATE when running with --allow-write
• --security: Validation level (strict, standard, minimal)

Query Limits:

• --timeout: Query timeout (default 30s)
• --max-rows: Limit rows returned per query (0 = unlimited)
• --allow-multi-statement: Allow multiple SQL statements in one query

Transport:

• --transport: stdio (default) or http
• --host: Bind address (default: localhost)
• --port: Listen port (default: 3000)

Connection Scoping:

• --allowed-connections: Comma-separated list of connections to allow (restricts access)
• --default-connection: Default connection when not specified (does not restrict access)

Hosted Platform:

• --platform: Run hosted platform MCP mode only. Requires whodb login and whodb use --org <org> --project <project>.

# Restrict AI to specific connections only
whodb mcp serve --allowed-connections prod,staging

# Set default without restricting access
whodb mcp serve --default-connection prod

# Combine: restrict to prod/staging, default to staging
whodb mcp serve --allowed-connections prod,staging --default-connection staging

When --allowed-connections is set:

• whodb_connections only shows allowed connections
• Queries to other connections are rejected
• First allowed connection becomes the default (unless --default-connection is set)

Configure Connections

The MCP server uses the same connection sources as the CLI:

Option 1: Environment Profiles (recommended for production)

Use env profiles like WHODB_POSTGRES='[{"alias":"prod","host":"host","user":"user","password":"pass","database":"dbname","port":"5432"}]' or WHODB_MYSQL_1='{"alias":"staging","host":"host","user":"user","password":"pass","database":"dbname","port":"3306"}'. Each object supports alias (connection name), host, user, password, database, port, and optional config.

Use the JSON formats shown above. alias sets the connection name used in MCP tools.

# Array format
export WHODB_POSTGRES='[{"alias":"prod","host":"host","user":"user","password":"pass","database":"dbname","port":"5432"}]'

# Numbered format (one profile per variable)
export WHODB_MYSQL_1='{"alias":"staging","host":"host","user":"user","password":"pass","database":"dbname","port":"3306"}'

If alias is omitted, the CLI assigns a name like postgres-1. Saved connections take precedence if names collide.

Option 2: Saved Connections

Use whodb connect --name mydb ... to save connections that the MCP server can access.

If a tool call omits connection, the MCP server uses the only available connection or returns an error if multiple are available.

MCP Client Configuration (Example)

Example configuration (from whodb mcp serve --help):

{
  "mcpServers": {
      "whodb": {
        "command": "whodb",
        "args": ["mcp", "serve"],
        "env": {
          "WHODB_POSTGRES_1": "{\"alias\":\"prod\",\"host\":\"localhost\",\"user\":\"user\",\"password\":\"pass\",\"database\":\"db\"}"
        }
      }
    }
  }

Docker MCP Server

docker run -i --rm \
  -e WHODB_POSTGRES_1='{"alias":"prod","host":"host","user":"user","password":"pass","database":"db"}' \
  --network host \
  whodb-cli:latest mcp serve

Interactive Mode Views

1. Connection View

Select and manage database connections.

Key	Action
↑/k/Shift+Tab	Move up
↓/j/Tab	Move down
Enter	Connect to selected database
n	New connection
d	Delete connection
Esc	Back (form) / press twice to quit (list)
Ctrl+C	Force quit

Form mode: Tab/Shift+Tab or ↑/↓ to move fields, ←/→ to change database type, Enter to connect.

2. Browser View

Navigate schemas and tables in a visual grid layout.

Key	Action
↑/k ↓/j ←/h →/l	Navigate grid
/ or f	Filter tables
Ctrl+S	Select schema
Enter	View table data
Ctrl+E	Open SQL editor
Ctrl+H	View query history
Ctrl+A	Open AI chat
Ctrl+R	Refresh table list
Tab	Next view
Esc	Disconnect
Ctrl+C	Quit

3. Editor View

Write and execute SQL queries with schema-aware autocomplete.

Key	Action
Alt+Enter (Option+Enter Mac)	Execute query
Ctrl+Space (Ctrl+@)	Trigger autocomplete
↑/↓ or Ctrl+P/N	Navigate suggestions
Enter	Accept suggestion
Alt+L	Clear editor
Tab	Next view
Esc	Back to browser

Features:

• Schema-aware autocomplete (tables, columns, keywords, snippets)
• Multi-line editing
• Error display

4. Results View

View query results in a responsive, paginated table.

Key	Action
↑/k ↓/j	Navigate rows
←/h →/l	Scroll columns
n	Next page
p	Previous page
s	Cycle page size
Shift+S	Custom page size
e	Export data
w	Add WHERE condition
c	Select columns
Esc	Back

Features:

• Pagination (configurable, default 50 rows)
• Column selection
• Data export (CSV, Excel)

5. History View

Browse and re-execute past queries.

Key	Action
↑/k ↓/j	Navigate history
/	Filter history
Enter	Load query into editor
r	Re-run query
Shift+D	Clear history
y/n	Confirm clear
Tab	Next view
Esc	Back

6. AI Chat View

AI-assisted database chat (requires a configured provider and consent).

Key	Action
↑/↓	Cycle fields
←/→	Change selection
Ctrl+L	Load models
Ctrl+I	Focus message input
Ctrl+P/N	Select message
Enter	Confirm/send/view
Ctrl+R	Revoke consent
Esc	Back to browser

Consent gate: press a to accept or Esc to exit.

7. Export View

Export data to CSV or Excel format.

Key	Action
Tab/↑/↓	Move between fields
←/→	Change format/delimiter/toggle
Enter	Confirm export
Esc	Cancel

Configuration

Config File Location

WhoDB CLI stores data in the unified WhoDB config:

• macOS: ~/Library/Application Support/whodb/config.json
• Linux: $XDG_DATA_HOME/whodb/config.json (default: ~/.local/share/whodb/config.json)
• Windows: %APPDATA%\\whodb\\config.json

Development builds append -dev to the data directory name, and EE builds append -ee.

Query history is stored alongside the config as history.json.

Config Structure

{
  "cli": {
    "connections": [
      {
        "name": "local-postgres",
        "type": "Postgres",
        "host": "localhost",
        "port": 5432,
        "username": "postgres",
        "database": "mydb",
        "schema": "public"
      }
    ],
    "history": {
      "max_entries": 1000,
      "persist": true
    },
    "display": {
      "theme": "dark",
      "page_size": 50
    },
    "ai": {
      "consent_given": false
    },
    "query": {
      "timeout_seconds": 30
    }
  }
}

Passwords are stored in the OS keyring when available. If not available, they are written to config.json (new files are created with 0600 permissions).

Environment Variables

export WHODB_CLI_DEBUG=true
export WHODB_CLI_NO_COLOR=true
export NO_COLOR=1

Docker Usage

Run Interactively

docker run -it --rm whodb-cli:latest

Connect to Host Database

docker run -it --rm --network host whodb-cli:latest connect \
  --type postgres \
  --host localhost \
  --user postgres \
  --database mydb

Execute Query

docker run -it --rm --network host whodb-cli:latest query "SELECT version()"

Persist Configuration

docker run -it --rm \
  -v ~/.local/share/whodb:/root/.local/share/whodb \
  --network host \
  whodb-cli:latest

Environment Variables

• TERM=xterm-256color - Proper terminal colors (set by default)
• WHODB_CLI_DEBUG / WHODB_CLI_NO_COLOR / NO_COLOR - Control CLI output

Keyboard Reference Card

Global

Key	Action
Ctrl+C	Quit
Esc	Go back
?	Show help

Navigation (Vim-style)

Key	Action
↑ or k	Up
↓ or j	Down
← or h	Left
→ or l	Right
/	Filter/Search

Common Actions

Key	Action
Enter	Select/Execute
r	Refresh/Re-run
e	Edit/Export
n	New/Next
p	Previous
d	Delete

Troubleshooting

Connection Issues

"Cannot connect to database"

# Verify database is running
pg_isready -h localhost -p 5432  # PostgreSQL
mysql -h localhost -u root -p     # MySQL

"Plugin not found"

Supported database types: postgres, mysql, sqlite, mongodb, redis, clickhouse, elasticsearch, mariadb

Display Issues

"Garbled text / incorrect colors"

# Set terminal type
export TERM=xterm-256color

Recommended terminals: iTerm2, Alacritty, Windows Terminal, Kitty

Configuration Issues

"Config not found"

mkdir -p ~/.local/share/whodb
whodb connect --type postgres --host localhost --name test

Adjust the path for your OS (see Configuration).

"Permissions error"

chmod 700 ~/.local/share/whodb
chmod 600 ~/.local/share/whodb/config.json ~/.local/share/whodb/history.json

Debug Mode

whodb --debug

Architecture

cli/
├── cmd/                # CLI commands (Cobra)
│   ├── root.go         # Main entry, starts TUI
│   ├── connect.go      # Database connection
│   ├── query.go        # Direct query execution
│   ├── schemas.go      # List schemas
│   ├── tables.go       # List tables
│   ├── columns.go      # Describe columns
│   ├── connections.go  # Connection management
│   ├── agent.go        # Agent capability manifest
│   ├── doctor.go       # Connection diagnostics
│   ├── runbooks.go     # Built-in workflows
│   ├── skills.go       # Skill and assistant integration installer
│   ├── export.go       # Data export
│   ├── history.go      # Query history
│   ├── mcp.go          # MCP server command
│   └── completion.go   # Shell completion
├── internal/
│   ├── tui/            # Terminal UI (Bubble Tea)
│   │   ├── model.go
│   │   ├── connection_view.go
│   │   ├── browser_view.go
│   │   ├── editor_view.go
│   │   ├── results_view.go
│   │   ├── history_view.go
│   │   ├── chat_view.go
│   │   ├── export_view.go
│   │   ├── where_view.go
│   │   ├── columns_view.go
│   │   ├── schema_view.go
│   │   └── messages.go
│   ├── agentmanifest/  # Agent capability manifest builder
│   ├── config/         # Unified config.json + keyring storage
│   ├── database/       # Database manager
│   ├── doctor/         # Connection diagnostics
│   ├── runbooks/       # Built-in workflow execution
│   ├── skillinstaller/ # Bundled skill and assistant integration installation
│   └── history/        # Query history
├── pkg/
│   ├── mcp/            # MCP server implementation
│   │   ├── server.go   # Server setup
│   │   ├── tools.go    # Tool handlers
│   │   └── credentials.go # Connection resolution
│   ├── output/         # Programmatic output formatting
│   ├── styles/         # UI styling (Lipgloss)
│   ├── version/        # Build/version info
│   └── crash/          # Panic handler and crash report
├── skills/             # Claude Code skills
│   ├── whodb/          # Main database skill
│   ├── query-builder/  # Natural language → SQL
│   └── schema-designer/ # Schema design assistance
├── agents/             # Claude Code agents
│   ├── database-analyst.md
│   ├── query-optimizer.md
│   └── report-generator.md
└── plugin.json         # Plugin manifest

Development

# Run in development mode
go run .

# Run tests
go test ./...

# Build with race detector
go build -race -o whodb .

# Lint
golangci-lint run ./...

License

Apache License 2.0 - See LICENSE file for details.