Elekto MCP for SQL Server

Name: Elekto MCP for SQL Server
Author: elekto-com-br

作者：elekto-com-br版本 2.3.4i★ –i在你的电脑上运行

注册名称io.github.elekto-com-br/elekto-mcp-sql

安装

概览

作者提供的说明（英文原文）

Read-only SQL Server introspection and querying: schema, definitions, dependencies and data.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 数据库与数据集

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
注册中心没有列出需要填写的密钥。

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "elekto-sql": {
      "command": "dnx",
      "args": [
        "Elekto.Mcp.Sql",
        "--yes"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add elekto-sql -- dnx Elekto.Mcp.Sql --yes

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "elekto-sql": {
      "command": "dnx",
      "args": [
        "Elekto.Mcp.Sql",
        "--yes"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "elekto-sql": {
      "type": "stdio",
      "command": "dnx",
      "args": [
        "Elekto.Mcp.Sql",
        "--yes"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 elekto-com-br 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“数据库与数据集”中的其他服务器比较i

星标数多于此分类中其他 1137 个服务器的 0%
发布到注册中心的时间比此分类中其他 1137 个服务器的 66% 更新
基础检查结果等于或优于此分类中其他 1137 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Elekto MCP for SQL Server 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（2.3.4）于23天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 .NET。

有什么可以替代它？

同一分类中有：Supabase, MongoDB MCP Server, Elasticsearch MCP Server

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Supabase

作者：supabase

MCP server for interacting with the Supabase platform

电脑或云端★ 2,993Apache-2.0昨天更新

安装

MongoDB MCP Server

作者：mongodb-js

MongoDB Model Context Protocol Server

在你的电脑上运行★ 1,157Apache-2.03天前更新

安装

Elasticsearch MCP Server

作者：cr7258

MCP server for interacting with Elasticsearch

在你的电脑上运行★ 315Apache-2.014个月前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Elekto.Mcp.Sql

Read-only MCP server for SQL Server 2017+ introspection and querying (tested on 2019 and 2022). Exposes schema metadata, object definitions, and data queries via the MCP protocol (stdio), allowing GitHub Copilot (and other MCP clients, like Claude, etc.) to understand your database structure without storing credentials in the repository.

⚠️ Privacy and Data Security Warning

MCP servers act as a bridge between your local data and AI language models. When you use this server with an AI assistant (such as GitHub Copilot, Claude, or others), the following happens:

The AI agent calls tools on this server to read data from your SQL Server database.
The results — which may include table schemas, stored procedure definitions, or actual row data — are sent back to the AI agent and transmitted to the LLM provider's infrastructure for analysis.
This means your data leaves your machine and is sent to a third-party service (Microsoft, Anthropic, OpenAI, etc.), subject to their respective terms of service and privacy policies.

Before connecting this server to any database, carefully consider:

What data could be read? Does it include PII, financial records, trade secrets, or other sensitive information?
Who is the LLM provider and what are their data retention and privacy policies?
Are you authorized to share this data with that third party under applicable laws and regulations?

Recommendations:

Never connect to databases containing sensitive data unless you have explicitly assessed and accepted this risk.
Use database accounts with the minimum required privileges (read-only, restricted to specific schemas where possible).
Use max_query_rows to limit how much data can be returned in a single call.
Prefer databases with anonymized or synthetic data for development and exploration.
AI agents can be extremely creative in finding ways to execute a task. Altouht this server is designed to be read-only and to validate all inputs, there is always a risk of unintended consequences when exposing database access to an AI agent.

Regardless of the precautions you take, the responsibility for any consequences arising from the use of this tool rests entirely with you. This software is provided *as is* with no warranties of any kind.

Available Tools

Tool	Description
`list_databases`	Databases registered in the configuration
`get_database_overview`	High-level database summary (counts, size, connection metadata), and whether the login sees everything
`check_permissions`	What the connected login can and cannot see, the GRANT that completes it, and whether it could write
`get_schema_summary`	Aggregated metrics by schema (objects, rows, size)
`list_schemas`	Schemas in a database (excluding system schemas)
`list_tables`	User tables with schema, dates, approximate rows and estimated size; filterable by schema and name pattern
`list_views`	User views, filterable by schema and name pattern
`find_columns`	Every table and view holding a column whose name matches a pattern
`list_procedures`	User stored procedures (with basic complexity metrics)
`list_functions`	User-defined functions (with basic complexity metrics)
`get_table_schema`	Columns with unambiguous type declarations, all extended properties, PKs, FKs, checks, uniques and indexes with key order and declared key width
`get_view_definition`	DDL definition + columns of a view, with the same column detail
`get_procedure_definition`	CREATE PROCEDURE text
`get_function_definition`	CREATE FUNCTION text
`get_dependency_graph`	Object dependency edges (FK + SQL dependencies)
`get_table_usage`	References to a table across FKs and SQL modules
`get_data_profile`	Column profile (null ratio, distinct count, min/max, top values)
`get_index_health`	Duplicate/unused index diagnostics + missing-index suggestions
`compare_schemas`	Compares table/column structure between two configured databases
`generate_dependency_dot`	Graphviz DOT dependency graph with node metadata (`node_kind`)
`query_table`	SELECT from a table or view with filtering, grouping, secure aggregates, sorting, sampling and pagination

Upgrading from 1.x

Version 2.0.0 changes what the tools return and how their parameters are declared. Nothing needs reconfiguring — connection files, .mcp.json and the CLI arguments are unchanged — but anything that parses the output will notice:

Change	What to do
`query_table` returns an object, not an array	Read the rows from `rows`; check `truncated`
Failures return `ok: false` content instead of raising a tool error	Test for `ok === false` before treating the payload as data
Column results gained `type_declaration`, `max_length_chars`, `is_persisted` and `extended_properties`	Prefer `type_declaration` over `max_length`, which is bytes
`description` on a column is now an alias for `extended_properties.MS_Description`	Nothing; it still works
Optional tool parameters are no longer nullable	Nothing over MCP. Direct C# callers pass `""` (or `0`) instead of `null`
New: `find_columns`; `list_tables` and `list_views` take a `name_pattern`	Nothing; both are additive

Everything else — every other tool, every other field — is unchanged.

What changed in 2.1.0

Nothing changes shape: arrays are still arrays and objects keep every field they had. A few values now say "unknown" instead of passing a guess for a fact, which is worth knowing if you parse them:

Change	Why
New: `check_permissions`	Says what the login is missing, per tool, with the GRANT that fixes it
`get_database_overview`, `get_table_usage`, `get_index_health` and `generate_dependency_dot` gained a `visibility` block	So a result the login could only partly see says so
`list_procedures` / `list_functions` rows gained `definition_visible`; `line_count` and `join_count` are `null` when it is false	A hidden definition used to read as a body of 0 lines
`referenced_object_count` is `null`, and `get_table_usage`'s `sql_module_usage` is `null`, when the login cannot read `sys.sql_expression_dependencies`	Both used to fail the whole call with error 229
`get_index_health` returns the duplicates and `null` for the DMV sections when the login lacks the server permission	It used to fail outright, losing the part that needs no permission
`get_*_definition` of a name the login cannot see returns `ok: false` instead of `[]`	`[]` read the same for "does not exist" and "hidden from you"
SQL errors carry their number, and the hint tells permission, missing name and syntax apart	One generic hint covered all three

What changed in 2.2.0

No tool result changes shape. What changes is how the server starts and how it is packaged:

Change	Why
The server starts without any connection, states it in its server instructions, and every tool answers `ok: false` with the file to create, where it looked and an example	A server that exited at startup showed only as "failed", and failed in every project when registered for all of them
A configuration that cannot be read (invalid JSON, a `%{VARIABLE}` that is not set, a `--connections` file that is missing or empty) is reported the same way, instead of ending the process	The error now reaches whoever calls the tools
While nothing is loaded, every call looks for the configuration again	A connections file created after the server started is used without a restart
The package is listed among nuget.org's MCP servers and carries `.mcp/server.json`	So it can be found there, with a ready configuration on its MCP Server tab

The process no longer exits with code 1 when the configuration is missing or unreadable. Anything that relied on that exit code should read a tool's answer instead. The README also gained setup instructions for Claude Code and Codex.

What changed in 2.3.0

No tool result changes shape; what changes is what the tools say about themselves, which is what an agent chooses them by:

Change	Why
Every tool declares a title and the MCP annotations `readOnlyHint`, `idempotentHint`, `destructiveHint: false` and `openWorldHint: false`	Clients can show the tools as safe, and agents need not infer it from prose
Every description says what the tool does, when to use it and which tool to use instead	So an agent picks the right one of 21 tools the first time
The server always sends instructions on connecting, describing how the tools fit together	Previously it sent them only when no connection was configured

What changed in 2.3.1

Nothing changes shape. generate_dependency_dot now says which way its arrows point, what it returns besides the DOT text, how to render it and when another tool fits better. The server is listed in the MCP Registry as "Elekto MCP for SQL Server", and each release now also appears under the repository's GitHub Releases.

What changed in 2.3.2

Nothing changes shape. When no connection is configured, the guidance returned to the agent now tells it to agree with the user before writing anything, and never to write a password into the connections file or anywhere else, using %{VARIABLE} in its place. It also points to connections the project may already keep where this server does not look (spring.datasource.url in application.properties or application.yml, or a sqlserver:// or mssql:// URL in a .env file), for the agent to show the user rather than for the server to parse.

What changed in 2.3.3

Nothing changes shape. The tool shipped System.Security.Cryptography.Pkcs 9.0.13, which Microsoft.Data.SqlClient brings in and which two .NET denial of service advisories affect: GHSA-846f-f764-76mx (CVE-2026-84008, high) and GHSA-2fmv-rv2c-59x7 (CVE-2026-70162, moderate). It now ships the fixed 10.0.13. Update the global tool with dotnet tool update -g Elekto.Mcp.Sql; a dnx configuration that names no version picks up 2.3.3 by itself.

This is also the first release whose GitHub Release carries the package, with a build provenance attestation; Verifying a release shows how to check it.

What changed in 2.3.4

Nothing changes shape. The tool now runs on `Microsoft.Data.SqlC

只显示了开头部分；其余内容请在仓库中阅读