Legacy Sql Architect MCP Server

Connect Claude Desktop (or any MCP-compatible AI client) to your PostgreSQL, SQL Server, or Oracle database and let the AI inspect schemas, read

Local serverstdio

What is the Legacy Sql Architect MCP MCP server?

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. That is what the legacy sql architect mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

The tools it exposes

The server publishes 9 tools. What each one is for:

  • inspect_schema — Tables, columns, types, primary keys, foreign keys
  • data_sampler — Sample rows with automatic sensitive-column masking
  • get_procedure_source — Full source code of stored procedures and functions
  • query_plan_expert — Execution plan analysis, full table scan detection
  • dependency_graph — FK chains, trigger→procedure call chains, view dependencies
  • generate_mermaid_erd — Entity-Relationship Diagram in Mermaid format
  • generate_documentation — Complete Markdown documentation for the entire schema
  • find_impact — Everything that depends on a given table
  • generate_java_dao — Java Entity + Repository classes (plain JDBC) per table

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Legacy Sql Architect MCP.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Legacy Sql Architect MCP's toolset — inspect_schema, data_sampler, get_procedure_source and 6 more — is a fair guide to whether it matches your workflow. It is maintained by tabforgeai; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

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 to try

  • Use Legacy Sql Architect MCP to inspect schema.
  • Use Legacy Sql Architect MCP to data sampler.
  • Use Legacy Sql Architect MCP to get procedure source.

Frequently asked questions

It connects Legacy Sql Architect MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 9 tools (inspect_schema, data_sampler, get_procedure_source, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Legacy Sql Architect MCP directly.