Labsco
tabforgeai logo

Legacy SQL Architect MCP

β˜… 1

from tabforgeai

MCP server that gives AI agents deep understanding of contemporary or legacy relational databases.

πŸ”₯πŸ”₯πŸ”₯πŸ”₯βœ“ VerifiedFreeAdvanced setup

Legacy SQL Architect MCP

MCP server that gives AI agents deep understanding of legacy databases.

Connect Claude Desktop (or any MCP-compatible AI client) to your PostgreSQL, SQL Server, or Oracle database and let the AI inspect schemas, read stored procedures, analyze query performance, trace dependencies, generate documentation, and produce working Java code β€” all in a single conversation, without you copying a single line of SQL.


Why Legacy SQL Architect MCP?

Works with legacy databases, not just modern ones. Full stored procedure source retrieval, trigger dependency mapping, and impact analysis designed for databases that have been running for years or decades β€” including large PL/SQL packages that other tools fail on.

Read-only by design. Connects in strict read-only mode. Physically cannot modify your database β€” no INSERT, no UPDATE, no DELETE. Safe to point at production.

No framework lock-in. No Docker. Pure Java + JDBC. No Spring, no ORM, no infrastructure to maintain. Runs as a lightweight native installer on Windows, macOS, and Linux.

Combines structure + logic + real data in one conversation. The AI inspects the schema, reads the stored procedure that processes orders, then samples real orders to understand why something is broken β€” without you copy-pasting anything between tools.

The AI understands relationships, not just tables. dependency_graph and find_impact trace how tables, triggers, procedures, views, and foreign keys connect β€” so the AI tells you what breaks before you change anything.

Generates working Java code, not pseudocode. generate_java_dao produces ready-to-compile Entity + Repository classes (plain JDBC, Java 17+) directly from your live schema.


Supported Databases

DatabaseTested version
PostgreSQL11+
SQL Server2016+ (Express, Standard, Enterprise)
Oracle12c+

Available Tools

ToolWhat it does
inspect_schemaTables, columns, types, primary keys, foreign keys
data_samplerSample rows with automatic sensitive-column masking
get_procedure_sourceFull source code of stored procedures and functions
query_plan_expertExecution plan analysis, full table scan detection
dependency_graphFK chains, trigger→procedure call chains, view dependencies
generate_mermaid_erdEntity-Relationship Diagram in Mermaid format
generate_documentationComplete Markdown documentation for the entire schema
find_impactEverything that depends on a given table
generate_java_daoJava Entity + Repository classes (plain JDBC) per table

Example Prompts

Inspect the schema, generate a Mermaid ERD, sample the orders table,
read all stored procedures, and produce complete Markdown documentation.
Analyze this query with query_plan_expert:
SELECT * FROM orders WHERE status = 'PENDING' AND created_at > '2024-01-01'
Is it using indexes? What would you recommend?
Generate Java DAO classes for all tables using package com.acme.repository,
then write each file into src/main/java/com/acme/repository/.
Build the dependency graph. When a row is inserted into orders,
what triggers fire and what procedures do they call?

Documentation

  • Setup Guide β€” installation, config.json reference, Claude Desktop setup, troubleshooting
  • User Guide β€” all tools with prompt examples, multi-tool workflows, tips

Building from Source

Requires Java 21 and Maven 3.8+.

# Run tests + build JAR
mvn clean package

# Windows installer (run on Windows, requires Java 21 with jpackage)
JAVA_HOME="c:/Java_21" mvn clean package -P windows-exe -Dmaven.test.skip=true

# Linux DEB (run inside Ubuntu/Debian container or system)
mvn clean package -P linux-deb -Dmaven.test.skip=true

# Linux RPM (run inside RHEL/Fedora container or system)
mvn clean package -P linux-rpm -Dmaven.test.skip=true

Integration tests use embedded PostgreSQL β€” no Docker, no external database required.


Distribution

Legacy SQL Architect MCP is distributed as native installers β€” not as a Maven library. There is no dependency to add to your pom.xml. Download the installer for your platform from GitHub Releases and follow the Setup Guide.