Sql Server Analyst Mcp

io.github.coregentdevspacePublished by GitHub account coregentdevspacev0.1.1Updated Oct 27, 2026

Read-only SQL Server Analyst MCP — safe schema, stored procedure, and performance analysis.

VerifiedSTDIODesktop onlyDatabasesData & Analytics

Overview

AI-generated overview

A local, read-only MCP server that lets an assistant inspect SQL Server schemas, stored procedures and query performance.

What you can do
  • Explore database schemas and objects such as tables and stored procedures
  • Inspect stored procedure definitions and structure
  • Run read-only analysis queries with configurable row limits and timeouts
  • Review performance-related information about the connected SQL Server instance
  • Scope access to specific databases and schemas through allowlists
When to use it
Useful when you want an assistant to help understand or document an existing SQL Server database, review stored procedures, or investigate query performance without granting write access. It suits analysts and developers working against a single SQL Server or Azure SQL instance from their own machine.
Requirements
Runs locally over stdio as an npm package, so Node.js is needed. Requires a reachable SQL Server instance and SQL authentication credentials: MSSQL_SERVER, MSSQL_USER and the secret MSSQL_PASSWORD, plus optional settings for port, default database, encryption, certificate trust, row limits, timeout and log level. Set MSSQL_ENCRYPT to true for Azure SQL.
Before you install
The server holds SQL credentials (MSSQL_PASSWORD) and connects directly to your database, so use a least-privilege read-only login. Leaving ALLOWED_DATABASES or ALLOWED_SCHEMAS empty removes the allowlist restriction. Setting MSSQL_TRUST_SERVER_CERT to true weakens connection security and is meant only for local development. Row caps and timeouts limit, but do not eliminate, the cost of heavy queries.

Installation

In SourceWeft

  1. Open Sql Server Analyst Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.