SQL Sentinel MCP Server

Official

by tkmawarire · C#

SQL Server monitoring and diagnostics for AI agents using Extended Events. No ODBC drivers required.

io.github.tkmawarire/sql-sentinel MCP Server

The io.github.tkmawarire/sql-sentinel (io.github.tkmawarire/sql-sentinel) MCP server provides SQL Server monitoring, diagnostics, and database operations for AI agents. It is built using Extended Events and native SQL Server connectivity via .NET 9 and Microsoft.Data.SqlClient. No ODBC drivers are required.

🛠️ Key Features

SQL Server monitoring and diagnostics using Extended Events
Database operations for AI agents
Native SQL Server connection via Microsoft.Data.SqlClient
Built with .NET 9
No ODBC drivers required

🚀 Use Cases

Monitoring SQL Server activity for AI agents
Running diagnostics on SQL Server using Extended Events
Performing SQL-related database operations within agent workflows

⚡ Developer Benefits

Production-ready MCP server
Uses native SQL Server connectivity (Microsoft.Data.SqlClient)
Deployable via NuGet or Docker (ghcr.io)

⚠️ Limitations

Coverage details beyond monitoring/diagnostics/database operations are not provided in the available source text.

Topics

extended-eventsmcp-serversql-server

README.md18 KBView on GitHub

SQL Sentinel MCP Server

NuGet

A production-ready MCP (Model Context Protocol) server for SQL Server monitoring, diagnostics, and database operations. Built with .NET 9 and Microsoft.Data.SqlClient for native SQL Server connectivity — no ODBC drivers required.

Features

Session Management — Create, start, stop, drop, and list Extended Events sessions
Smart Filtering — Filter by application, database, user, duration, host, and text patterns
Query Fingerprinting — Normalize and group similar queries differing only in literal values
Sequence Analysis — Trace execution order with timing gaps and cumulative duration
Deadlock Detection — Capture and analyze XML deadlock reports with victim/process details
Blocking Analysis — Monitor blocked process events with wait resource and SQL text
Wait Stats — Query sys.dm_os_wait_stats directly, categorized by type (CPU, I/O, Lock, Memory, etc.)
Health Check — Comprehensive server diagnostic: slow queries, deadlocks, blocking, wait stats, and insights
Real-Time Streaming — Stream captured events for a specified duration
Production-Safe — Auto-excludes noise (sp_reset_connection, SET statements, trace queries)
Database Operations — List tables, describe schemas, query data, insert, update, and drop tables
AI-Optimized — Structured JSON output with optional Markdown formatting

Requirements

SQL Server 2012+ with Extended Events enabled (default)

Required permissions:

sql

GRANT ALTER ANY EVENT SESSION TO [your_login];
GRANT VIEW SERVER STATE TO [your_login];

For blocked process detection:

sql

EXEC sp_configure 'show advanced options', 1;
RECONFIGURE;
EXEC sp_configure 'blocked process threshold', 5;
RECONFIGURE;

Installation

Option 1: Docker (Recommended)

No .NET SDK required. Works on any system with Docker installed.

bash

docker pull ghcr.io/tkmawarire/sql-sentinel-mcp:latest

Claude Desktop (`claude_desktop_config.json`)

json

{
  "mcpServers": {
    "sql-sentinel": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "--network", "host",
               "-e", "SQL_SENTINEL_CONNECTION_STRING=Server=localhost;Database=master;User Id=sa;Password=YourPassword;TrustServerCertificate=true",
               "ghcr.io/tkmawarire/sql-sentinel-mcp:latest"]
    }
  }
}

Claude Code

bash

claude mcp add sql-sentinel \
  -e SQL_SENTINEL_CONNECTION_STRING="Server=localhost;Database=master;User Id=sa;Password=YourPassword;TrustServerCertificate=true" \
  -- docker run -i --rm --network host \
  -e SQL_SENTINEL_CONNECTION_STRING \
  ghcr.io/tkmawarire/sql-sentinel-mcp:latest

Network access: The -i flag is required for stdio transport. Use --network host so the container can reach SQL Server on your host machine. For remote SQL Server, omit --network host and use the accessible hostname in your connection string.

Connection string: Set SQL_SENTINEL_CONNECTION_STRING via -e. All tools read the connection string from this environment variable.

Option 2: .NET Global Tool (NuGet)

Requires .NET 9 SDK or later.

bash

dotnet tool install -g SQLSentinel.Mcp

json

{
  "mcpServers": {
    "sql-sentinel": {
      "command": "sql-sentinel-mcp",
      "env": {
        "SQL_SENTINEL_CONNECTION_STRING": "Server=localhost;Database=master;User Id=sa;Password=YourPassword;TrustServerCertificate=true"
      }
    }
  }
}

Option 3: Build from Source

bash

git clone https://github.com/tkmawarire/sql-sentinel.git
cd sql-sentinel
dotnet build

Run directly:

bash

dotnet run --project SqlServer.Profiler.Mcp/

Or publish a self-contained single binary:

bash

# Windows
dotnet publish SqlServer.Profiler.Mcp/ -c Release -r win-x64 --self-contained

# Linux
dotnet publish SqlServer.Profiler.Mcp/ -c Release -r linux-x64 --self-contained

# macOS (Apple Silicon)
dotnet publish SqlServer.Profiler.Mcp/ -c Release -r osx-arm64 --self-contained

# macOS (Intel)
dotnet publish SqlServer.Profiler.Mcp/ -c Release -r osx-x64 --self-contained

Output will be in bin/Release/net9.0/{runtime}/publish/

Connection Strings

All tools read the connection string from the SQL_SENTINEL_CONNECTION_STRING environment variable. Set it once before starting the server:

bash

export SQL_SENTINEL_CONNECTION_STRING="Server=localhost;Database=master;User Id=sa;Password=YourPassword;TrustServerCertificate=false;Encrypt=true"

SQL Authentication:

code

Server=localhost;Database=master;User Id=sa;Password=YourPassword;TrustServerCertificate=false;Encrypt=true

Windows Authentication:

code

Server=localhost;Database=master;Integrated Security=true;TrustServerCertificate=false;Encrypt=true

Note: Only use TrustServerCertificate=true in development environments with self-signed certificates. For production, always use TrustServerCertificate=false with a valid SSL certificate.

Azure SQL:

code

Server=yourserver.database.windows.net;Database=yourdb;User Id=user;Password=password;Encrypt=true

MCP Tools Reference

Session Lifecycle

Tool	Description
`sqlsentinel_create_session`	Create an Extended Events session with filters (not started)
`sqlsentinel_start_session`	Start capturing events for an existing session
`sqlsentinel_stop_session`	Stop capturing; events are retained
`sqlsentinel_drop_session`	Drop session and discard all events
`sqlsentinel_list_sessions`	List all MCP-created sessions with state and buffer usage
`sqlsentinel_quick_capture`	Create and start a session in one step

Event Retrieval

Tool	Description
`sqlsentinel_get_events`	Retrieve captured events with filtering, sorting, and deduplication
`sqlsentinel_get_stats`	Aggregate statistics grouped by fingerprint, database, app, or login
`sqlsentinel_analyze_sequence`	Analyze query execution sequence with timing and gaps
`sqlsentinel_get_connection_info`	List databases, applications, logins, sessions, and blocking info
`sqlsentinel_stream_events`	Real-time event capture for a specified duration (1–300s)

Diagnostics

Tool	Description
`sqlsentinel_get_deadlocks`	Retrieve deadlock events with victim, processes, locks, and SQL text
`sqlsentinel_get_blocking`	Retrieve blocked process events with wait resources and SQL text
`sqlsentinel_get_wait_stats`	Query `sys.dm_os_wait_stats` categorized by type (no session required)
`sqlsentinel_health_check`	Comprehensive report: slow queries, deadlocks, blocking, wait stats, insights

Permissions

Tool	Description
`sqlsentinel_check_permissions`	Check current login permissions and blocked process threshold config
`sqlsentinel_grant_permissions`	Grant required permissions to a login (requires sysadmin)

Database Operations

Tool	Description
`sqlsentinel_list_tables`	List all user tables in the database (schema-qualified)
`sqlsentinel_describe_table`	Detailed table schema: columns, indexes, constraints, foreign keys
`sqlsentinel_create_table`	Create a new table via CREATE TABLE statement
`sqlsentinel_insert_data`	Insert data via INSERT statement
`sqlsentinel_read_data`	Execute SELECT queries and return results
`sqlsentinel_update_data`	Update data via UPDATE statement
`sqlsentinel_drop_table`	Drop a table via DROP TABLE statement

Usage Examples

Quick Debug Session

code

Agent: sqlsentinel_quick_capture(
    sessionName: "debug_api",
    applications: "MyWebApp",
    minDurationMs: 100
)

// User triggers the slow operation

Agent: sqlsentinel_get_events(
    sessionName: "debug_api",
    sortBy: "DurationDesc",
    limit: 20
)

Agent: sqlsentinel_drop_session(sessionName: "debug_api")

Find N+1 Queries

code

Agent: sqlsentinel_quick_capture(
    sessionName: "n_plus_one_check",
    databases: "OrdersDB"
)

// User loads a page

Agent: sqlsentinel_get_stats(
    sessionName: "n_plus_one_check",
    groupBy: "QueryFingerprint"
)

// Look for queries with high execution counts

Trace Specific Operation

code

Agent: sqlsentinel_analyze_sequence(
    sessionName: "my_session",
    correlationId: "order-12345",
    responseFormat: "Markdown"
)

Deadlock Detection

code

Agent: sqlsentinel_quick_capture(
    sessionName: "deadlock_monitor",
    eventTypes: "Deadlock"
)

// Wait for deadlocks to occur

Agent: sqlsentinel_get_deadlocks(
    sessionName: "deadlock_monitor",
    responseFormat: "Markdown"
)

Blocking Analysis

code

Agent: sqlsentinel_quick_capture(
    sessionName: "blocking_check",
    eventTypes: "BlockedProcess"
)

// Requires: sp_configure 'blocked process threshold', 5

Agent: sqlsentinel_get_blocking(
    sessionName: "blocking_check",
    responseFormat: "Markdown"
)

Server Health Check

code

Agent: sqlsentinel_health_check(
    sessionName: "my_session",
    slowQueryThresholdMs: 1000,
    responseFormat: "Markdown"
)

Database Operations

code

Agent: sqlsentinel_list_tables()

Agent: sqlsentinel_describe_table(
    name: "dbo.Products"
)

Agent: sqlsentinel_read_data(
    sql: "SELECT TOP 10 * FROM dbo.Products ORDER BY CreatedDate DESC"
)

Wait Stats (No Session Required)

code

Agent: sqlsentinel_get_wait_stats(
    topN: 20,
    responseFormat: "Markdown"
)

Query Fingerprinting

Queries are normalized to group similar ones:

sql

-- These become one fingerprint:
SELECT * FROM Users WHERE id = 123
SELECT * FROM Users WHERE id = 456

-- Fingerprint: abc123:SELECT * FROM Users WHERE id = ?
-- Execution count: 2

Noise Filtering

Default excluded patterns (when excludeNoise=true):

sp_reset_connection — Connection pool reset
SET TRANSACTION ISOLATION LEVEL — Session setup
SET NOCOUNT, SET ANSI_* — Client configuration
sp_trace_*, fn_trace_* — Trace system queries

Supported Event Types

SqlBatchCompleted, RpcCompleted, SqlStatementCompleted, SpStatementCompleted, Attention, ErrorReported, Deadlock, BlockedProcess, LoginEvent, SchemaChange, Recompile, AutoStats

Project Structure

code

sql-profiler-mcp/
├── .github/
│   └── workflows/
│       ├── docker.yml                     # Build & push multi-arch Docker images
│       └── publish-mcp-registry.yml       # Publish NuGet + MCP registry
├── .mcp/
│   └── server.json                        # MCP manifest (NuGet + OCI packages)
├── SqlServer.Profiler.Mcp/                # Main MCP server (stdio transport)
│   ├── SqlServer.Profiler.Mcp.csproj
│   ├── Program.cs                         # Entry point, DI setup, MCP config
│   ├── Models/
│   │   ├── ProfilerModels.cs              # Records, enums, data models
│   │   └── DbOperationResult.cs           # Result model for CRUD operations
│   ├── Services/
│   │   ├── ProfilerService.cs             # Core Extended Events logic
│   │   ├── QueryFingerprintService.cs     # SQL normalization & fingerprinting
│   │   ├── WaitStatsService.cs            # DMV-based wait stats analysis
│   │   ├── SessionConfigStore.cs          # In-memory session config storage
│   │   └── EventStreamingService.cs       # Real-time event streaming
│   ├── Utilities/
│   │   └── SqlInputValidator.cs           # SQL input validation & escaping
│   └── Tools/
│       ├── SessionManagementTools.cs      # Session lifecycle tools (6)
│       ├── EventRetrievalTools.cs         # Event retrieval tools (5)
│       ├── DiagnosticTools.cs             # Diagnostic tools (4)
│       ├── PermissionTools.cs             # Permission tools (2)
│       └── DatabaseTools.cs               # Database CRUD tools (7)
├── SqlServer.Profiler.Mcp.Api/            # Debug REST API (Swagger on port 5100)
│   ├── SqlServer.Profiler.Mcp.Api.csproj
│   ├── Program.cs
│   ├── Controllers/
│   │   └── ProfilerController.cs
│   ├── Models/
│   │   └── RequestModels.cs
│   └── appsettings.json
├── SqlServer.Profiler.Mcp.Cli/            # Debug CLI (REPL + script mode)
│   ├── SqlServer.Profiler.Mcp.Cli.csproj
│   └── Program.cs
├── SqlServer.Profiler.Mcp.Tests/          # xUnit tests for core MCP library (228 tests)
│   └── ...
├── SqlServer.Profiler.Mcp.Api.Tests/      # xUnit tests for API project (29 tests)
│   └── ...
├── Dockerfile                             # Multi-stage build (bookworm-slim)
├── .dockerignore
├── SqlServer.Profiler.Mcp.slnx           # Solution file
├── CLAUDE.md
├── CONTRIBUTING.md
└── README.md

Development

Prerequisites

.NET 9 SDK
SQL Server 2012+ instance (local, Docker, or remote)
Docker (optional, for container builds)

Clone & Build

bash

git clone https://github.com/tkmawarire/sql-sentinel.git
cd sql-sentinel
dotnet restore
dotnet build

Running the MCP Server Locally

bash

dotnet run --project SqlServer.Profiler.Mcp/

The server communicates over stdio using the MCP protocol. Connect it to an MCP client (Claude Desktop, Claude Code, etc.) for interactive use.

Using the Debug API

The API project provides a REST wrapper around all MCP tools with Swagger UI for manual testing.

bash

dotnet run --project SqlServer.Profiler.Mcp.Api/

Swagger UI: http://localhost:5100/
Configure the connection string via environment variable SQL_SENTINEL_CONNECTION_STRING

Using the Debug CLI

The CLI project provides an interactive REPL and script mode for testing tools directly.

bash

# Interactive REPL mode
dotnet run --project SqlServer.Profiler.Mcp.Cli/

# List all available tools
dotnet run --project SqlServer.Profiler.Mcp.Cli/ list

# Get help for a specific tool
dotnet run --project SqlServer.Profiler.Mcp.Cli/ help sqlsentinel_quick_capture

# Execute a single tool
dotnet run --project SqlServer.Profiler.Mcp.Cli/ call sqlsentinel_list_sessions

Set the SQL_SENTINEL_CONNECTION_STRING environment variable before running.

Docker Build

bash

docker build -t sql-sentinel-mcp:test .
docker run -i --rm --network host sql-sentinel-mcp:test

Architecture

Key Patterns

Dependency injection via Microsoft.Extensions.Hosting
stdio transport — stdout is reserved for MCP protocol; all logging goes to stderr
Tool auto-discovery — MCP tools are discovered from the assembly via WithToolsFromAssembly()
XE session prefix — All created sessions are prefixed with mcp_sentinel_
Two event shapes — Standard events (query, login, recompile) with typed fields, and XML-payload events (deadlock, blocking) parsed from Extended Events XML

Adding a New MCP Tool

Create a public static method in the appropriate file under Tools/ (or create a new file)
Decorate with [McpServerTool(Name = "sqlsentinel_your_tool")] and [Description("...")]
Add parameters with [Description("...")] attributes — they become the tool's input schema
Inject services via method parameters (e.g., IProfilerService, IWaitStatsService)
Return a string (JSON or Markdown) — the framework handles MCP response wrapping

csharp

[McpServerTool(Name = "sqlsentinel_example")]
[Description("Description shown to AI agents")]
public static async Task<string> Example(
    IProfilerService profilerService,
    [Description("Optional filter")] string? filter = null)
{
    var connectionString = ConnectionStringResolver.Resolve();
    // Implementation
    return JsonSerializer.Serialize(result);
}

Troubleshooting

"Permission denied" creating session

sql

GRANT ALTER ANY EVENT SESSION TO [your_login];
GRANT VIEW SERVER STATE TO [your_login];

Check connection string credentials
For Windows auth, ensure process runs under correct user
For Azure SQL, ensure firewall allows your IP

No events captured

Verify session is RUNNING (sqlsentinel_list_sessions)
Check filters aren't too restrictive
Verify target database/app is generating queries
Check minDurationMs isn't filtering everything

No deadlock events

Ensure session was created with eventTypes: "Deadlock"
Deadlocks must actually occur while the session is running

No blocking events

Ensure blocked process threshold is configured: sp_configure 'blocked process threshold', 5
Ensure session was created with eventTypes: "BlockedProcess"
Blocking must exceed the configured threshold (seconds)

Timeout reading events

Large ring buffers with many events can be slow to parse. Use:

Time filters to narrow the window
Increase command timeout in code if needed

Security Notes

The SQL_SENTINEL_CONNECTION_STRING environment variable contains credentials — secure appropriately
Don't leave sessions running indefinitely on production
Query text may contain sensitive data
Grant minimum required permissions

Contributing

See CONTRIBUTING.md for guidelines on submitting issues and pull requests.

License

MIT

Install

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "sql-sentinel": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/tkmawarire/sql-sentinel-mcp"
      ]
    }
  }
}

io.github.tkmawarire/sql-sentinel MCP Server

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

SQL Sentinel MCP Server

Features

Requirements

Installation

Option 1: Docker (Recommended)

Claude Desktop (claude_desktop_config.json)

Claude Code

Option 2: .NET Global Tool (NuGet)

Option 3: Build from Source

Connection Strings

MCP Tools Reference

Session Lifecycle

Event Retrieval

Diagnostics

Permissions

Database Operations

Usage Examples

Quick Debug Session

Find N+1 Queries

Trace Specific Operation

Deadlock Detection

Blocking Analysis

Server Health Check

Database Operations

Wait Stats (No Session Required)

Query Fingerprinting

Noise Filtering

Supported Event Types

Project Structure

Development

Prerequisites

Clone & Build

Running the MCP Server Locally

Using the Debug API

Using the Debug CLI

Docker Build

Architecture

Key Patterns

Adding a New MCP Tool

Troubleshooting

"Permission denied" creating session

"Login failed"

No events captured

No deadlock events

No blocking events

Timeout reading events

Security Notes

Contributing

License

Install

Related servers

Claude Desktop (`claude_desktop_config.json`)