Skip to content
MCP-Bridge
DatabasesRuntime: npmNo Auth RequiredCommunity VerifiedlightningActive

Whodb MCP Server

4,930 StarsQuality Score: 95/99

Section A: Quick Answer & Architectural Summary

The Whodb Model Context Protocol (MCP) server enables AI coding assistants—including Claude Desktop, Cursor, VS Code, and Zed—to interact directly with databases infrastructure. Developers use this server to automate multi-step tasks, query context, and trigger operations natively from chat prompts. It executes on the npm runtime engine and launches with "npx -y whodb". Runs as a local process with zero external API key requirements; local system permissions apply.

Core Functionality:Whodb bridges AI assistants to databases workflows over local JSON-RPC stdio.
Quick Install:Run "npx -y whodb" or insert the MCP client snippet into your editor config.
Authentication:Zero authentication required — runs immediately out of the box.
Operational Caveat:Runs as a local process with zero external API key requirements; local system permissions apply.
Section B: Editorial Evaluation

MCPBridge Editorial Verdict: Whodb

8 Standardized Dimensions
1. Best For

Developers integrating AI coding agents (Claude, Cursor, Cline) with Databases services

2. Experience LevelBeginner
3. Setup Difficulty

Low (1-2 mins)

4. Authentication

Zero Authentication (Local Stdio)

5. Maintenance Status

Active Maintenance

6. Compatibility

Claude Desktop, Cursor IDE, VS Code (Cline/Roo), Zed Editor

7. Security Profile

Local process execution without credential exposure

8. MCPBridge Verdict Summary

MCPBridge rates Whodb as a tier-one reference integration for developers requiring databases tool capabilities inside AI agent workflows.

Technical Architecture & System Integration

The Whodb Model Context Protocol (MCP) server provides a standardized bridge between modern Large Language Model (LLM) agents and external technical infrastructure. By leveraging open MCP protocol primitives, AI assistants like Claude Desktop, Cursor IDE, VS Code (via Cline/Roo Code), and Zed Editor can inspect, query, and execute capabilities provided by Whodb without custom integration code.

Where data access meets operational intelligence

This architectural pattern ensures complete sandbox isolation and security: credentials (such as environment keys) remain strictly inside the local client process environment, never leaking into model prompt contexts or external third-party servers.

2. Key Features & Technical Specifications Matrix

Specification Matrix

Server NameWhodb
Identifierwhodb
CategoryDatabases
Runtime Enginenpm
Transport Layerstdio (Standard I/O)
Auth MechanismNone Required
Install Launchernpx -y whodb
GitHub Stars4,930
Publisher Sourcecommunity
Last Health Check9/5/2026

Core Capability Matrix

  • Native MCP Tools: Exposes discrete tools callable by AI coding assistants during chat or agent execution loops.
  • JSON-RPC 2.0 Specs: Complies with standard protocol error handling and bidirectional message formats.
  • Multi-Client Compatibility: Pre-validated for Claude Desktop, Cursor IDE, VS Code (Cline), Zed Editor, and Docker containers.
  • Zero Setup Friction: Requires no API key credentials for instant execution.
  • Automated Tool Discovery: Client hosts dynamically discover parameters and parameter schemas on connection handshake.

3. Multi-Client Installation Matrix & Setup Guides

Copy and paste the exact configuration snippet for your preferred MCP client or editor environment.

Claude Desktop Setup

claude_desktop_config.json

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "whodb": {
      "command": "npx",
      "args": [
        "-y",
        "whodb"
      ],
      "env": {}
    }
  }
}
Deep link

Cursor IDE Setup

.cursor/mcp.json

Open Cursor Settings → Features → MCP Servers → Add New MCP Server, or add to project workspace config.

{
  "mcpServers": {
    "whodb": {
      "command": "npx",
      "args": [
        "-y",
        "whodb"
      ],
      "env": {}
    }
  }
}

Saves as .cursor/mcp.json in the download. Move it to your project root.

Deep link install →

VS Code (Cline / Roo Code)

cline_mcp_settings.json

Paste directly into Cline MCP settings panel or workspace settings file.

{
  "mcpServers": {
    "whodb": {
      "command": "npx",
      "args": [
        "-y",
        "whodb"
      ],
      "env": {}
    }
  }
}

Zed Editor Context Server

settings.json

Insert into Zed's context_servers settings object.

{
  "context_servers": {
    "whodb": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "whodb"
        ],
        "env": {}
      }
    }
  }
}

Programmatic & Container Execution Snippets

Connect to Whodb programmatically via TypeScript, Python SDK, or Docker CLI.

import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StdioClientTransport } from "@modelcontextprotocol/sdk/client/stdio.js";

// Initialize Whodb MCP client transport via stdio
const transport = new StdioClientTransport({
  command: "npx",
  args: ["-y","whodb"],
  
});

const client = new Client(
  { name: "whodb-client", version: "1.0.0" },
  { capabilities: { tools: {}, resources: {}, prompts: {} } }
);

async function connectAndRun() {
  await client.connect(transport);
  const tools = await client.listTools();
  console.log("Connected to Whodb MCP Server successfully.");
  console.log("Available tools:", tools);
}

connectAndRun().catch(console.error);

4. Security Architecture & Credentials Reference

Configure authorization secrets and operational parameters safely inside your client environment object.

Section G: Security Architecture

Security Considerations & Sandbox Guidance: Whodb

Authorization credential isolation, least privilege boundaries, and container sandboxing options.

Credentials Handling

No external credentials required

Permission Scope

Read-Only Operations

Execution Boundary

Local stdio child process managed directly by client host

🔒

Isolation & Principle of Least Privilege

Run the server as a non-privileged child process. To achieve maximum isolation, execute inside a read-only Docker container.

Read-Only Sandbox Launch Example
docker run -i --rm --read-only --network=none mcp/whodb:latest

Actionable Operational Guidelines

  • Store authorization secrets in local environment files (.env.local) or client configuration; never commit secrets to Git repositories.
  • Limit API key permissions to the minimum scopes required for your specific workflow (least privilege principle).
  • Inspect tool schemas before invoking operations that perform destructive updates or permanent deletions.
  • The MCP stdio architecture keeps all credentials strictly on your machine; credentials are never transmitted into LLM prompt contexts.
Variable NameRequiredTypeDefaultPurpose & Description
LOG_LEVELNOConfiguration StringinfoSets output verbosity level for Whodb stdio log messages (debug, info, warn, error).

5. Tool Parameter Schemas & Usage Prompts

Detailed function call signatures and natural language prompt directives for Whodb.

Dynamic Capability Discovery

Runtime JSON-RPC 2.0 Tool Negotiation

The Whodb MCP server negotiates available tools dynamically at runtime via the standard Model Context Protocol tools/list handshake. Statically indexed schema tables are not hardcoded into this registry. When Claude Desktop or Cursor connects to the server process over stdio, the client automatically queries available functions and arguments upon initialization.

Programmatic Tool Discovery Example (TypeScript)
// Initialize stdio transport and discover runtime capabilities
const client = new Client({ name: "client", version: "1.0.0" }, { capabilities: {} });
await client.connect(transport);

// Dynamically discover all tools exposed by Whodb
const { tools } = await client.listTools();
console.log("Discovered Whodb tools:", tools);

Natural Language Usage Prompts

1. Information Retrieval & Status Inspection

Read-Only Query

"Use the Whodb MCP tools to check system status, list active resources, and summarize current configurations."

2. Executing Workflow Action

Action Execution

"Execute the primary workflow action on Whodb with parameters configured for your current task."

3. Multi-Step Automated Automation

Agent Automation

"Analyze output from Whodb, summarize any errors or warnings, and construct a follow-up request to remediate issues."

4. Schema & Parameter Inspection

Introspection

"Inspect available tools exposed by Whodb MCP server and generate a detailed report of supported capabilities."

Section C: Developer Workflows

Concrete Real-World Use Cases for Whodb

Practical multi-step agentic workflows and prompt directives demonstrating concrete developer outcomes.

InspectionWorkflow 01

Database Schema Exploration & Table Introspection

Allow AI assistants to query tables, inspect primary and foreign key constraints, and understand database relationships before generating migration scripts.

Execution Steps:
  1. Agent connects to database via MCP stdio client
  2. Executes schema introspection tool to retrieve DDL definitions
  3. Synthesizes accurate SQL queries validated against live schema
"Inspect the database schema using Whodb and summarize foreign key relationships in the users table."
PerformanceWorkflow 02

Automated Query Optimization & Diagnostic Execution

Run read-only analytical queries, explain query execution plans, and identify slow index scans directly from editor chat.

Execution Steps:
  1. Agent formulates query with execution plan flags
  2. Calls database tool to retrieve query cost and index utilization
  3. Recommends targeted composite indexes to eliminate table scans
"Run an EXPLAIN on recent queries through Whodb and suggest index improvements."
MigrationWorkflow 03

Safe Data Migration Script Verification

Verify prospective migration scripts against a local staging database instance before applying changes to production.

Execution Steps:
  1. Agent validates migration SQL syntax and rollback compatibility
  2. Executes dry-run schema alteration
  3. Confirms table state and records post-migration validation checks
"Use Whodb to verify whether the pending migration alters table constraints safely."
Section D: Project Suitability

Good Fit vs. Poor Fit Criteria for Whodb

Architectural guidelines to determine when to adopt this integration and when to explore alternatives.

✓

When to Choose / Good Fit

  • Developers using Claude Desktop, Cursor, or VS Code who need direct natural language interaction with Databases tools.
  • Local development workflows requiring zero-wrapper stdio communication with local credential isolation.
  • Teams building agentic coding workflows that automate repetitive Whodb queries and state checks.
  • Environments where JSON-RPC 2.0 protocol standardization simplifies tooling integration.
✕

When to Avoid / Poor Fit

  • Production multi-tenant servers requiring centralized role-based access control (RBAC) without local process sandboxing.
  • Streaming high-frequency data pipelines where stdio request-response tool calls introduce unwanted latency.
  • Completely unmonitored autonomous agents with unrestricted write access to sensitive production data.
Section E: Trust Architecture

Verification & Evidence Audit: Whodb

Tier: Automated Metadata CheckReview Protocol →

Repository metadata, installation commands, and schema conformity verified via automated build checks.

Last Verified:
Verification Source: scraped

Independent Evidence Checks

JSON-RPC 2.0 Protocol Conformityverified

Standardized stdio transport and bidirectional message formatting verified.

Package Registry & Launcherverified

Verified launch command format: npx (npm).

Repository & Maintenance Checkverified

4,930 GitHub stars; maintenance status: active.

Runtime Sandbox Executionchecked

Automated static check only; not independently executed in production sandbox.

Section F: Health & Maintenance

Project Health & Maintenance Audit: Whodb

lightningActive
Quality Score Index
95
★ Tier-One Quality Grade

Activity & Cadence

Commit VelocityRecent commit recorded on 7/20/2026
Release CadencePublished via source repository tags
Project LicenseOpen Source (MIT / Apache)

Transparent Quality Score Breakdown

✓Community publisher validation (+22 pts)
✓High compatibility runtime ecosystem (+20 pts)
✓Zero-authentication instant configuration (+20 pts)
✓JSON-RPC 2.0 protocol spec conformity (+15 pts)
✓Documented installation command & repository tracking (+10 pts)
Score Validation Criteria
✓Community publisher validation (+22 pts)
✓High compatibility runtime environment (+20 pts)
✓Zero-authentication instant configuration (+20 pts)
✓JSON-RPC 2.0 protocol spec conformity (+15 pts)
✓Dynamic runtime tool discovery protocol (+10 pts)

Own or Maintain Whodb?

Claim this listing to update descriptions, custom installation commands, and feature documentation.

Claim Listing →
Section H: Peer Comparison

Alternatives & Comparison Table (Databases)

Comparative trade-offs between Whodb and similar ecosystem tools in the Databases category.

OptionBest ForMain Difference vs. WhodbSetup / RuntimeExplore
PrestDevelopers needing Databases capabilities with go runtimeUses go runtime instead of npmgo / communityView →
TabularisDevelopers needing Databases capabilities with npm runtimeMaintains quality score of 95/99 with 3,759 starsnpm / communityView →
DbhubDevelopers needing Databases capabilities with npm runtimeMaintains quality score of 95/99 with 3,185 starsnpm / communityView →

9. Error Resolution & Troubleshooting Guide

Diagnose and resolve common JSON-RPC protocol error codes and stdio execution failures.

-32600 (Invalid Request)

Root Cause: Malformed JSON-RPC payload sent to server

Resolution Action: Verify MCP client payload adheres to JSON-RPC 2.0 specification.

-32601 (Method Not Found)

Root Cause: Requested tool or resource method does not exist

Resolution Action: Call list_tools() to inspect supported tool names on this server.

-32602 (Invalid Params)

Root Cause: Missing or invalid tool arguments

Resolution Action: Check argument schema parameter data types against tool specification.

-32603 (Internal Error)

Root Cause: Unhandled execution exception inside server process

Resolution Action: Inspect process stderr logs or verify runtime environment credentials.

RUNTIME_LAUNCH_ERROR

Root Cause: Runtime executable not found or missing environment dependencies

Resolution Action: Verify that npm is installed and on your system PATH, or execute "npx -y whodb" in terminal to inspect startup logs.

Section I: Authority & References

Official Verified Sources for Whodb

Authoritative upstream repositories, specifications, package registries, and configuration endpoints.

📦

Upstream Source Repository

Official GitHub repository containing source code, releases, and issue tracker.

https://github.com/clidey/whodb
🏷️

npm: whodb

Official package registry entry for versioned distribution.

https://www.npmjs.com/package/whodb
📐

Model Context Protocol Specification

Official Anthropic MCP protocol specifications and SDK documentation.

https://modelcontextprotocol.io
🛡️

Maintainer Claim & Verification

GitHub claim issue template for package authors to verify ownership.

https://github.com/stormlive-ai/mcp-bridge-docs/issues/new?title=Claim+Listing%3A+Whodb+%28mcp-server%3A+whodb%29&labels=claim-listing&body=%23%23+Claim+Listing+Request%0A%0AI+would+like+to+claim+this+listing%3A%0A%0A-+**Type%3A**+mcp-server%0A-+**ID%3A**+whodb%0A-+**Name%3A**+Whodb%0A%0A%23%23%23+Your+Information%0A%0A**GitHub+Handle%3A**+%3C%21--+your+GitHub+username+--%3E%0A%0A**Email%3A**+%3C%21--+optional%2C+for+verification+--%3E%0A%0A**Relationship+to+this+API%3A**%0A-+%5B+%5D+I+am+the+API+provider+%2F+maintainer%0A-+%5B+%5D+I+am+an+authorized+representative%0A-+%5B+%5D+Other%3A%0A%0A%23%23%23+Verification+Method%0A-+%5B+%5D+I+will+add+a+CNAME%2FTXT+record+to+verify+domain+ownership%0A-+%5B+%5D+I+can+confirm+from+an+email+address+at+the+provider+domain%0A-+%5B+%5D+I+maintain+the+GitHub+repository%0A%0A%23%23%23+Updates+I%27d+Like+to+Make+%28optional%29%0A%3C%21--+What+would+you+like+to+update%3F+Description%2C+links%2C+category%2C+etc.+--%3E%0A%0A---%0A*Submitted+via+MCP-Bridge+claim+form*
Section J: Technical FAQ

Frequently Asked Technical Questions: Whodb

Targeted developer questions regarding installation, client configuration, credentials, and error resolution.

Whodb is a native Model Context Protocol (MCP) server that exposes databases capabilities directly to AI assistants like Claude Desktop, Cursor, and VS Code. It executes locally via stdio transport, enabling AI models to inspect resources and execute tools within defined boundaries.

← Back to Ecosystem Directory
← Back to Databases Directory