# mbentham/SqlAugur [Health: Active]

**Category:** 🗄️ Databases  
**Repository:** https://github.com/mbentham/SqlAugur  
**GitHub Stars:** 5  
**Views:** 5  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/mbentham-sqlaugur

## Description
⃣ 🏠 🪟 🐧 - SQL Server MCP server with AST-based query validation, read-only safety, schema exploration, ER diagram generation, and DBA toolkit integration (First Responder Kit, DarlingData, spWhoIsActive).

## Tools
Capabilities this server exposes over MCP:

- **list_servers** — Lists available SQL Server instances configured in `appsettings.json`.
- **list_databases** — Lists all databases on a named server with names, IDs, states, and creation dates.
- **read_data** — Executes a read-only SQL SELECT query. Only `SELECT` and `WITH` (CTE) queries are allowed. Results returned as JSON with a configurable row limit.
- **get_query_plan** — Returns the estimated or actual XML execution plan for a SELECT query.
- **get_schema_overview** — Concise Markdown schema overview: tables, columns, PKs, FKs, unique/check constraints, defaults. Supports `compact` mode, schema and table filtering.
- **describe_table** — Comprehensive table metadata in Markdown: columns, data types, nullability, defaults, identity, computed expressions, indexes, FKs, constraints.
- **list_programmable_objects** — Lists views, stored procedures, functions, and triggers. Filterable by type and schema.
- **get_object_definition** — Returns the source definition (CREATE statement) of a programmable object.
- **get_extended_properties** — Reads extended properties (descriptions, metadata) on tables, columns, and other objects.
- **get_object_dependencies** — Shows what an object references and what references it — upstream and downstream dependency graphs.
- **get_plantuml_diagram** — Generates a PlantUML ER diagram with tables, columns, PKs, and FK relationships. Saves to a `.puml` file. Supports `compact` mode, schema/table filtering, and a configurable table limit (max 200).
- **get_mermaid_diagram** — Generates a Mermaid ER diagram with tables, columns, PKs, and FK relationships. Saves to a `.mmd` file. Supports `compact` mode, schema/table filtering, and a configurable table limit (max 200).
- **sp_blitz** — Overall SQL Server health check — prioritized findings for performance, configuration, and security.
- **sp_blitz_first** — Real-time performance diagnostics — samples DMVs over an interval for waits, file latency, and perfmon counters.
- **sp_blitz_cache** — Plan cache analysis — top queries by CPU, reads, duration, executions, or memory grants.
- **sp_blitz_index** — Index analysis — missing, unused, and duplicate indexes with usage patterns.
- **sp_blitz_who** — Active query monitor — what's running, blocking info, tempdb usage, query plans.
- **sp_blitz_lock** — Deadlock analysis from the `system_health` extended event session.
- **sp_blitz_plan_compare** — Cross-server query plan comparison — captures a plan snapshot on one server and compares it to the cached plan on a second server without using linked servers. Requires the [demon_hunters branch](https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/tree/demon_hunters) until merged to mai…
- **sp_pressure_detector** — Diagnoses CPU and memory pressure — resource bottlenecks, high-CPU queries, memory grants, disk latency.
- **sp_quickie_store** — Query Store analysis — top resource-consuming queries, plan regressions, wait statistics.
- **sp_quickie_cache** — Plan cache analysis — high-impact queries ranked by impact score over the `dm_exec_*_stats` DMVs (the plan-cache companion to `sp_quickie_store`).
- **sp_health_parser** — Parses the `system_health` extended event session for historical waits, disk latency, CPU, memory, and locking.
- **sp_log_hunter** — Searches SQL Server error logs for errors, warnings, and custom messages.
- **sp_human_events_block_viewer** — Analyzes blocking events from `sp_HumanEvents` sessions — blocking chains, lock details, waits.
- **sp_index_cleanup** — Finds unused and duplicate indexes that are candidates for removal.
- **sp_query_repro_builder** — Generates reproduction scripts for Query Store queries with parameter values.
- **sp_whoisactive** — Monitors active sessions and queries — wait info, blocking details, tempdb usage, resource consumption.
- **list_toolsets** — Lists available toolsets with status (available, enabled, not configured) and tool counts.
- **get_toolset_tools** — Returns detailed tool and parameter info for a specific toolset before enabling it.
- **enable_toolset** — Enables a toolset, making its tools available. Only works if the admin has enabled the toolset via the corresponding `Enable*` config flag.

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "sqlaugur": {
    "command": "npx",
    "args": ["-y","mbentham-sqlaugur"]
  }
}
```

## Documentation

## What mbentham/SqlAugur MCP server does

The mbentham/SqlAugur MCP server connects an MCP client to one or more named SQL Server instances. Connections are defined in `appsettings.json`, and `list_servers` exposes the configured names for later tool calls. Database discovery includes database names, IDs, states, and creation dates.

Its query interface is intentionally read-only. `read_data` accepts only `SELECT` statements and common table expressions beginning with `WITH`, then returns JSON subject to a configurable row limit. The server also provides estimated or actual XML query plans for SELECT statements. Query validation uses Microsoft's T-SQL parser to inspect the full syntax tree rather than relying on keyword matching.

## How it works

The MCP client communicates with the server over standard input and output. SqlAugur validates incoming queries before sending permitted work to SQL Server. Diagnostic stored procedure calls have parameter restrictions intended to prevent write operations. Throughput and concurrency controls are included to limit repeated or simultaneous agent requests.

Core database tools support schema inspection and documentation. Agents can retrieve a compact or detailed schema view, describe a table's columns and constraints, inspect views, procedures, functions, and triggers, read object definitions and extended properties, and examine upstream or downstream dependencies. Diagram tools write PlantUML or Mermaid ER definitions to `.puml` or `.mmd` files and support schema, table, compactness, and table-count options.

## Setup and configuration

The documented installation options are the NuGet global tool, a Docker or Podman container, and a source build. The global tool requires the .NET 10 runtime and is installed with `dotnet tool install -g SqlAugur`; the executable used in MCP client configuration is `sqlaugur`. Source builds require the .NET 10 SDK.

For local installation, place `appsettings.json` under `~/.config/sqlaugur/` on Linux or macOS, or under `%APPDATA%\\sqlaugur` on Windows. Container deployments can mount the file at `/app/appsettings.json` or provide nested `SqlAugur__Servers__...__ConnectionString` environment variables. Each configured server needs a named connection string. SQL Server connectivity and authentication depend on those connection strings.

## Tools and capabilities

The initial toolset includes server and database listing, read-only data access, query plans, and schema overview. Additional tools can be discovered through `list_toolsets` and inspected with `get_toolset_tools` before being enabled.

Available diagnostic coverage includes overall health checks, DMV-based performance sampling, plan-cache and Query Store analysis, index review, active-session and blocking inspection, deadlock and system-health parsing, error-log searches, and query reproduction script generation. The listed integrations include SQL Server First Responder Kit, DarlingData, and `sp_WhoIsActive`; availability depends on the corresponding database-side setup.

## Limitations and notes

Only SELECT and CTE queries are accepted by `read_data`; this interface is not intended for INSERT, UPDATE, DELETE, DDL, or other mutations. PlantUML and Mermaid generation enforce a maximum of 200 tables. Diagnostic outputs may omit verbose columns and truncate long strings by default, with documented options such as `verbose` and `includeQueryPlans` available where supported.

The mbentham/SqlAugur MCP server requires a reachable SQL Server and correctly configured connection. Its cross-server plan comparison tool requires the `demon_hunters` branch of First Responder Kit until the referenced change is merged. The project is licensed under MIT.

_Full upstream README: https://allmcps.com/mcp/mbentham-sqlaugur/readme_