Schemacrawler Ai

io.github.schemacrawlerPublished by GitHub account schemacrawlervv18.0.1-1Updated Oct 30, 2026

Enables natural language schema queries — explore tables, keys, procedures, and get SQL help fast

VerifiedSTDIODesktop onlyDatabasesDeveloper Tools

Overview

AI-generated overview

SchemaCrawler AI lets an assistant explore a relational database's schema in natural language — tables, keys, procedures — and get SQL help.

What you can do
  • Explore database schema metadata: tables, keys, procedures and other objects, with detail controlled by the info level setting.
  • Ask for SQL help and natural-language schema questions against the connected database.
  • Identify the database server through an optional alias and description that appear in tool results and instructions.
  • Limit which tools are exposed by excluding them with a comma-separated list.
When to use it
Useful when you want an assistant to answer questions about an existing relational database's structure or help write SQL, without granting it a full query client. Suited to local, desktop-based exploration of a single configured database connection.
Requirements
Runs as a local process (container image, stdio transport by default; http is also selectable). Needs a database connection: either a JDBC URL or the server type, host, port and database name. Database user name and password are supplied through SCHCRWLR_DATABASE_USER and SCHCRWLR_DATABASE_PASSWORD, and may be optional depending on the connection type. A JDBC driver for the target database is implied.
Before you install
The server holds database credentials in SCHCRWLR_DATABASE_USER and SCHCRWLR_DATABASE_PASSWORD; supply them via environment configuration rather than sharing them in prompts. It connects to a live database, so point it at a least-privileged account and a non-production instance where possible. Metadata retrieved can be extensive at higher info levels, which may expose schema details to the assistant.

Installation

In SourceWeft

  1. Open Schemacrawler Ai 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 started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

6
  1. vv18.0.1-1LatestOct 30, 2026
  2. vv17.16.0-1Oct 14, 2026
  3. vv17.15.7-1Sep 30, 2026
  4. vv17.15.6-1Sep 25, 2026
  5. vv17.15.4-1Sep 21, 2026
  6. vv17.15.2-1Sep 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.