Supabase
Supabase’s official server lets AI create tables, query data and review project settings in your Supabase database.
Description from the maker (original English)
SQL Server monitoring and diagnostics for AI agents using Extended Events. No ODBC drivers required.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"sql-sentinel": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/tkmawarire/sql-sentinel-mcp"
]
}
}
}Run this in your terminal
claude mcp add sql-sentinel -- docker run -i --rm ghcr.io/tkmawarire/sql-sentinel-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"sql-sentinel": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/tkmawarire/sql-sentinel-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"sql-sentinel": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/tkmawarire/sql-sentinel-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account tkmawarire, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (2.3.1) reached the registry 8 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need .NET, Docker on your computer.
In the same category: Supabase, MongoDB MCP Server, Elasticsearch MCP Server
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Supabase’s official server lets AI create tables, query data and review project settings in your Supabase database.
MongoDB Model Context Protocol Server
MCP server for interacting with Elasticsearch
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
sys.dm_os_wait_stats directly, categorized by type (CPU, I/O, Lock, Memory, etc.)sp_reset_connection, SET statements, trace queries) GRANT ALTER ANY EVENT SESSION TO [your_login];
GRANT VIEW SERVER STATE TO [your_login];
- For blocked process detection:
EXEC sp_configure 'show advanced options', 1;
RECONFIGURE; EXEC sp_configure 'blocked process threshold', 5; RECONFIGURE;
No .NET SDK required. Works on any system with Docker installed.
docker pull ghcr.io/tkmawarire/sql-sentinel-mcp:latest
claude_desktop_config.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 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
-iflag is required for stdio transport. Use--network hostso the container can reach SQL Server on your host machine. For remote SQL Server, omit--network hostand use the accessible hostname in your connection string.
Connection string: Set
SQL_SENTINEL_CONNECTION_STRINGvia-e. All tools read the connection string from this environment variable.
Requires .NET 9 SDK or later.
dotnet tool install -g SQLSentinel.Mcp
{
"mcpServers": { "sql-sentinel": { "command": "sql-sentinel-mcp", "env": { "SQL_SENTINEL_CONNECTION_STRING": "Server=localhost;Database=master;User Id=sa;Password=YourPassword;TrustServerCertificate=true" } } } }
git clone https://github.com/tkmawarire/sql-sentinel.git
cd sql-sentinel dotnet build
Run directly:
dotnet run --project SqlServer.Profiler.Mcp/
Or publish a self-contained single binary:
# Windows
dotnet publish SqlServer.Profiler.Mcp/ -c Release -r win-x64 --self-contained
dotnet publish SqlServer.Profiler.Mcp/ -c Release -r linux-x64 --self-contained
dotnet publish SqlServer.Profiler.Mcp/ -c Release -r osx-arm64 --self-contained
dotnet publish SqlServer.Profiler.Mcp/ -c Release -r osx-x64 --self-contained
Output will be in bin/Release/net9.0/{runtime}/publish/
All tools read the connection string from the SQL_SENTINEL_CONNECTION_STRING environment variable. Set it once before starting the server:
export SQL_SENTINEL_CONNECTION_STRING="Server=localhost;Database=master;User Id=sa;Password=YourPassword;TrustServerCertificate=false;Encrypt=true"
SQL Authentication:
Server=localhost;Database=master;User Id=sa;Password=YourPassword;TrustServerCertificate=false;Encrypt=true
Windows Authentication:
Server=localhost;Database=master;Integrated Security=true;TrustServerCertificate=false;Encrypt=true
Note: Only use
TrustServerCertificate=truein development environments with self-signed certificates.
For production, always use
TrustServerCertificate=falsewith a valid SSL certificate.
Azure SQL:
Server=yourserver.database.windows.net;Database=yourdb;User Id=user;Password=password;Encrypt=true
| 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 |
| 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) |
| 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 |
| 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) |
| 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 |
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")
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
Agent: sqlsentinel_analyze_sequence(
sessionName: "my_session", correlationId: "order-12345", responseFormat: "Markdown" )
Agent: sqlsentinel_quick_capture(
sessionName: "deadlock_monitor", eventTypes: "Deadlock" )
// Wait for deadlocks to occur
Agent: sqlsentinel_get_deadlocks( sessionName: "deadlock_monitor", responseFormat: "Markdown" )
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" )
Agent: sqlsentinel_health_check(
sessionName: "my_session", slowQueryThresholdMs: 1000, responseFormat: "Markdown" )
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" )
Agent: sqlsentinel_get_wait_stats(
topN: 20, responseFormat: "Markdown" )
Queries are normalized to group similar ones:
-- 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
Default excluded patterns (when excludeNoise=true):
sp_reset_connection — Connection pool resetSET TRANSACTION ISOLATION LEVEL — Session setupSET NOCOUNT, SET ANSI_* — Client configurationsp_trace_*, fn_trace_* — Trace system queriesSqlBatchCompleted, RpcCompleted, SqlStatementCompleted, SpStatementCompleted, Attention, ErrorReported, Deadlock, BlockedProcess, LoginEvent, SchemaChange, Recompile, AutoStats
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
Only the beginning is shown; read the rest in the repo