Sqloom: MSSQL
AI-assisted database chat for Microsoft SQL Server in Visual Studio Code. Chat with your SQL Server databases using natural language and get intelligent schema insights through an integrated chat participant.
Highlights
- Natural-language database chat: mention
@sqloom in the VS Code chat to answer questions about your SQL Server databases.
- Object Explorer integration: right-click a database and choose Open in Sqloom to launch a bound chat session.
- Schema scripting: use
/scriptTable, /showDefinition, and related commands to emit full CREATE scripts with dependency analysis.
- Performance diagnostics: run
/diag or /optimize to surface expensive queries and tuning recommendations.
- Local-first MCP architecture: all requests run against a bundled Model Context Protocol server; no database metadata leaves your environment.
Requirements
- Visual Studio Code 1.93.0 or later.
- Microsoft SQL Server (mssql) extension.
- Windows 10/11 (x64) with network access to your SQL Server instance. (Fingerprint-based licensing currently requires Windows; cross-platform support is on the roadmap.)
Installation
From the VS Code Marketplace
- Open the Extensions view (
Ctrl+Shift+X or Cmd+Shift+X).
- Search for Sqloom: MSSQL.
- Click Install.
From a local VSIX
- Download the VSIX (for example, from a release page or CI build).
- Run
code --install-extension .\sqloom-mssql-<version>.vsix or drag the file into the Extensions view.
- Reload VS Code when prompted.
Getting Started
- Install and configure the Microsoft SQL Server extension, then connect to a server.
- In the Object Explorer, right-click a database and choose Open in Sqloom.
- In the chat window, mention
@sqloom to start a conversation that uses the selected database as context.
Example prompts:
@sqloom Give me a summary of the Sales schema.
@sqloom /scriptTable dbo.Orders
@sqloom /verifyLicense sq-1234-ABCD-5678
@sqloom What indexes protect the dbo.Invoice table?
| Command |
Chat Syntax |
Description |
| Open in Sqloom |
Command Palette / Object Explorer |
Launches a Sqloom-bound chat session for the selected database. |
/scriptTable |
@sqloom /scriptTable dbo.Table |
Returns CREATE scripts for the table and first-order dependencies. |
/showDefinition |
@sqloom /showDefinition dbo.Object |
Retrieves the full definition for tables, views, procedures, functions, and more. |
/optimize |
@sqloom /optimize dbo.Object [type] |
Generates tuning guidance by combining detailed object metadata with Copilot analysis. |
/diag |
@sqloom /diag health (also index, query) |
Runs targeted diagnostics for health, index, or query analysis. |
/verifyLicense |
@sqloom /verifyLicense <key> |
Validates a Sqloom license key and returns structured JSON. |
Every command is surfaced through the sqloom.agent chat participant and backed by a VS Code language model tool, so Copilot-based experiences can invoke them autonomously.
How Sqloom Works
Sqloom keeps database work local: the extension orchestrates Copilot for conversational responses while delegating actual SQL analysis and scripting to the MCP server running on your machine.
Sqloom bundles a local database agent that powers the chat experience. Key capabilities include:
| Capability |
Description |
Typical Inputs |
| Schema scripting |
Generate full CREATE scripts for a table and its first-order dependencies. |
Table name, optional connection details. |
| Object definition |
Retrieve the full definition for tables, views, procedures, functions, synonyms, sequences, and user-defined types. |
Object name, optional type hint and connection details. |
| Health diagnostics |
Produce prioritized health findings covering backups, DBCC checks, and configuration safety nets. |
Optional connection overrides and result limits. |
| Index diagnostics |
Highlight missing, unused, fragmented, and heap-related index issues. |
Optional connection overrides plus toggles for heap and fragmentation analysis. |
| Query diagnostics |
Surface the heaviest queries by CPU, logical reads, or duration, optionally annotating plan warnings. |
Optional connection overrides, limit, and preferred sort. |
| License verification |
Validate a Sqloom license key and return the signed verification payload. |
License key. |
Extension Settings
Sqloom exposes a handful of settings under Settings > Extensions > Sqloom: MSSQL, but you usually do not need to change them because the packaged MCP server and defaults work out of the box:
sqloom.mcp.serverPath: absolute path to a Sqloom MCP server executable. Leave blank to use the bundled binaries (the extension discovers the bundled server automatically in most scenarios).sqloom.mcp.args: optional array of command-line arguments passed to the MCP server.- Advanced diagnostics toggle: enable additional heuristics during
/diag runs (disabled by default).
Bundled MCP Server
The extension ships with a .NET-based MCP server that performs all SQL Server operations. No additional installation is required; Sqloom starts the server automatically when you open a chat session.
Privacy and Security
- Sqloom never transmits connection strings or query data to cloud services.
- All chat requests are executed locally through the MCP server over stdio.
- License verification uses signed responses and can be run entirely offline if you provide an on-premises licensing endpoint.
Review your organization's security policies before connecting production systems.
Troubleshooting
- Chat participant missing: reload VS Code after installation and ensure the Microsoft SQL Server extension is active.
- Cannot find MCP server: reinstall the extension or point
sqloom.mcp.serverPath to the Sqloom MCP server executable.
- No database context: initiate the chat from Object Explorer or specify
/scriptTable schema.table so Sqloom can resolve the target.
- Extension activation errors: open Developer: Toggle Developer Tools to review the console and include logs when filing issues.
Support and Feedback
License
Distributed under the MIT License.
