SqlAugur

What it is

A .NET MCP server for named SQL Server connections. Only SELECT and CTE queries pass: each one is parsed into an abstract syntax tree with Microsoft's TSql180Parser, so keywords hidden in comments, string literals or encoding tricks are rejected at the syntax level rather than by pattern matching.

What you get

• Six core tools always loaded: list_servers, list_databases, read_data, get_query_plan, get_schema_overview and describe_table
• Schema exploration with list_programmable_objects, get_object_definition, get_extended_properties and get_object_dependencies — the last one reports both what an object references and what references it
• get_plantuml_diagram and get_mermaid_diagram write ER diagrams with cardinality to a file, with schema and table filtering and a limit of 200 tables
• First Responder Kit diagnostics behind a config flag: sp_blitz, sp_blitz_first, sp_blitz_cache, sp_blitz_index, sp_blitz_who, sp_blitz_lock, sp_blitz_plan_compare
• DarlingData diagnostics behind another: sp_pressure_detector, sp_quickie_store, sp_quickie_cache, sp_health_parser, sp_log_hunter, sp_human_events_block_viewer, sp_index_cleanup, sp_query_repro_builder, plus sp_whoisactive on its own flag
• 31 tools in total; list_toolsets, get_toolset_tools and enable_toolset load the non-core ones on demand instead of at startup

Requirements

The NuGet package SqlAugur, version 1.4.0, installed as a global .NET tool over stdio and launched as sqlaugur; it needs the .NET 10.0 runtime. A container at ghcr.io/mbentham/sqlaugur:latest is the alternative. Connections go in appsettings.json under ~/.config/sqlaugur or %APPDATA%\sqlaugur, or as environment variables using __ as the section separator. Windows Authentication or Azure Managed Identity is preferred over a password in the file.

Setup effort

One command plus a key — dotnet tool install -g SqlAugur, then supply credentials

Tools you get

31 tools named in the project's documentation. A default install shows 12: the DBA toolsets and discovery tools stay off until enabled in config, and each toolkit needs its stored procedures on the SQL Server. Only SELECT and CTE queries run.

Requires

sqlaugur on PATH

Where it runs

The documented client runs the server on your machine.