Skip to main content
Glama
lobsterdb

lobsterdb

Official
by lobster-kit

@lobsterkit/db-mcp

MCP server for LobsterDB — managed PostgreSQL for AI agents. Provision databases, run SQL, evolve schemas with tracked migrations. No API keys, no human signup, no configuration.

Quick Start

Add to your MCP config (.mcp.json, claude_desktop_config.json, .cursor/mcp.json, etc.):

{
  "mcpServers": {
    "lobsterdb": {
      "command": "npx",
      "args": ["-y", "@lobsterkit/db-mcp@0.1.0"]
    }
  }
}

On first use, an account is created automatically and your token is saved to ~/.lobsterdb/token.

Related MCP server: PostgreSQL MCP

Tools

Tool

Description

create_database

Provision a new Postgres database

list_databases

List all databases on the account

get_database

Get details and connection string for a database

delete_database

Permanently delete a database

query

Run parameterized SQL — SELECT, INSERT, UPDATE, DELETE. Supports multi-statement SQL (only the last statement's result is returned; intermediate results are discarded).

introspect_schema

Get table/column schema optimized for LLM context

migrate

Apply tracked, idempotent DDL migrations

list_migrations

Show schema change history

snapshot

Create a v2 DDL-aware point-in-time backup (Builder+)

get_account

View tier, limits, and usage

Environment Variables

Variable

Description

LOBSTERDB_API_KEY

API key (skips auto-signup and file persistence)

LOBSTERDB_API_URL

Custom API base URL (default: https://api.theclawdepot.com/db)

LobsterKit Ecosystem

This MCP server is part of the LobsterKit multi-product ecosystem. Accounts can be linked across LobsterVault, LobsterDB, and LobsterMail using a linkToken at signup, enabling a single Stripe customer and an automatic multi-product discount (see pricing).

License

MIT

Available Tools

10 tools
create_databaseCreate DatabaseB

Provision a new PostgreSQL database. Returns a connection string ready to use immediately.

Inputs: name (required).

delete_databaseDelete DatabaseB

Permanently delete a database and all its data.

Inputs: databaseId (required).

get_accountGet AccountB

Get your account tier, usage, and limits.

Inputs: no named parameters.

get_databaseGet DatabaseA

Get details for a specific database including its connection string.

Inputs: databaseId (required).

introspect_schemaIntrospect SchemaA

Get the database schema — tables and columns — in a format optimized for LLM context. Use this before writing queries against an existing database.

Inputs: databaseId (required).

list_databasesList DatabasesB

List all databases on your account.

Inputs: no named parameters.

list_migrationsList MigrationsB

List all schema migrations that have been applied to a database, in order.

Inputs: databaseId (required).

migrateRun Schema MigrationA

Apply a schema change (DDL) to a database. Migrations are tracked in _lobsterdb_migrations and are idempotent — safe to call multiple times with the same name.

Guidelines:

  • Use for all DDL: CREATE TABLE, ALTER TABLE ADD COLUMN, CREATE INDEX, etc.

  • Name migrations descriptively: "create_cards_table", "add_favorite_to_cards", "add_price_index"

  • ADDITIVE changes (add columns, create tables): apply without asking the user.

  • DESTRUCTIVE changes (DROP TABLE, DROP COLUMN, RENAME, changing column types): always confirm with the user before running.

  • Never use query for DDL — always use migrate so changes are tracked.

Inputs: sql (required), name (required), databaseId (required).

queryQuery DatabaseC

Execute a SQL query against a database. Use $1, $2, ... for parameters. Results are sanitized for safe LLM context.

Inputs: sql (required), databaseId (required), params.

snapshotCreate SnapshotB

Create a point-in-time snapshot of a database. Requires Builder tier or higher.

Inputs: databaseId (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: database lifecycle, SQL querying, schema introspection, migrations, snapshots, and account details. The query-vs-migrate boundary is explicitly clarified, and no two tools appear to do the same thing.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern (create_database, get_database, list_databases, introspect_schema, list_migrations). Minor deviations are snapshot (bare noun) and query/migrate (verbs without an explicit object).

    Tool Count5/5

    Ten tools is well-scoped for a database provisioning and management server. Each tool earns its place, covering account, database CRUD, querying, schema introspection, migrations, and snapshots without excessive redundancy.

    Completeness3/5

    Core database and query workflows are covered, but database CRUD lacks an update/rename operation and snapshots can only be created, not listed, restored, or deleted. Migrations can be applied and listed but not rolled back or dropped, leaving some notable lifecycle dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI-driven PostgreSQL database management with secure OAuth 2.1 authentication, enabling users to administer, monitor, and query databases with support for extensions like pgvector, PostGIS, and pg_cron.
      123 npm
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides tools for managing PostgreSQL databases through the Managed DB API, including project creation, table management, migrations, backups, and more.
      -