Skip to main content
Glama
lobster-kit

lobsterdb

Official
by lobster-kit

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LOBSTERDB_API_KEYNoAPI key (skips auto-signup and file persistence)
LOBSTERDB_API_URLNoCustom API base URLhttps://api.theclawdepot.com/db

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
create_databaseB

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

list_databasesB

List all databases on your account.

get_databaseA

Get details for a specific database including its connection string.

delete_databaseB

Permanently delete a database and all its data.

queryC

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

introspect_schemaA

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

snapshotB

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

get_accountB

Get your account tier, usage, and limits.

migrateA

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.

list_migrationsB

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

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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 issues