SQL Server MCP (Model Context Protocol) Server

Created By
MCPRUNNERa year ago
MCP Server for MSSQL (Microsoft SQL Server)
Overview

What is SQL Server MCP?

SQL Server MCP (Model Context Protocol) Server is a server designed to connect to one or more SQL Server databases, enabling Visual Studio Code and GitHub Copilot to interact with SQL databases via the Model Context Protocol.

How to use SQL Server MCP?

To use SQL Server MCP, set up the server with the required environment variables, start the server using the provided scripts, and configure Visual Studio Code to connect to the MCP server.

Key features of SQL Server MCP?

  • SQL query execution
  • Database metadata retrieval (tables, views, stored procedures, functions)
  • Connection string encryption with AES-256
  • Robust logging with Serilog
  • Dependency injection for testable components
  • Strongly-typed models for database metadata

Use cases of SQL Server MCP?

  1. Executing SQL queries through Visual Studio Code.
  2. Retrieving detailed database schema information.
  3. Managing multiple database connections securely.

FAQ from SQL Server MCP?

  • Can SQL Server MCP connect to multiple databases?

Yes, it can connect to one or more SQL Server databases.

  • Is there a way to encrypt connection strings?

Yes, connection strings are encrypted using AES-256 encryption.

  • How do I manage database connections?

You can manage connections through the MCP interface or programmatically using the provided tools.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCPRUNNER
Star
0
Language
C#
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago