Berth

io.github.seayniclabsPublished by GitHub account seayniclabsv0.2.1Updated Oct 24, 2026

Database management — query, schema inspection, migrations for PostgreSQL, MySQL, SQLite.

VerifiedSTDIODesktop onlyDatabasesDeveloper Tools

Overview

AI-generated overview

A local MCP server that gives an AI assistant structured access to PostgreSQL, SQLite and MySQL databases for querying, schema inspection, migrations and backup

What you can do
Connect to a database and run SELECT queries, with an automatic row limit, or execute INSERT, UPDATE and DELETE statements subject to the active safety mode, with a confirmation token for destructive operations in admin mode. Inspect schemas: list tables, views and indexes, describe columns, show foreign key relationships, report database and table sizes, and view currently running queries on PostgreSQL. Analyze queries with EXPLAIN ANALYZE. Generate dialect-aware migration SQL by comparing a live database against target DDL or against a second live database. Create database backups and restore from them.
When to use it
Useful when an assistant needs to explore or query a relational database, understand its schema, diagnose slow queries, draft migrations between schemas, or take and restore backups, while keeping writes and destructive operations gated behind explicit modes.
Requirements
Runs as a local process over stdio, launched by an MCP client. Install the berth-mcp Python package from PyPI; MySQL support needs the optional mysql extra. Database connection strings (DSNs) are supplied through the db_connect tool. Backup and restore paths are confined to BERTH_BACKUP_DIR, which defaults to the current working directory. Backup and restore rely on the pg_dump/psql, sqlite3 and mysqldump/mysql command-line tools.
Before you install
The server starts read-only, but write and admin modes can be enabled and then allow INSERT, UPDATE, DELETE and CREATE, with admin mode permitting destructive operations once a 60-second confirmation token is echoed back. Restoring a backup overwrites database contents. Connection strings passed to db_connect contain database credentials; passwords are masked in output, but the DSN itself is still a secret. Backups are written to files under BERTH_BACKUP_DIR.

Installation

In SourceWeft

  1. Open Berth in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.