Skip to content
Custom Connectors

Connect Microsoft SQL Server to Claude Code

Let Claude run scoped reads and writes against your Microsoft SQL Server data. From the terminal, inside the sessions where you already work.

How do you connect Microsoft SQL Server to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Microsoft SQL Server, you add a Microsoft SQL Server MCP server: a small hosted service that exposes Microsoft SQL Server's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Microsoft SQL Server account. No API keys pasted into config files.

claude mcp add --transport http microsoft-sql-server https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Microsoft SQL Server once connected?

Full read-write access lets Claude run parameterized INSERT, UPDATE, and DELETE statements, execute stored procedures, manage indexes, and apply schema migrations inside a transaction you approve. The investigation that used to mean opening SSMS and hand-writing SQL happens against the live database, with the same guardrails a careful engineer would use.

  • Run a parameterized INSERT or UPDATE against a specific table
  • Execute a stored procedure with the arguments you supply
  • Apply a schema migration (add a column, create an index) inside a transaction
  • Backfill or correct rows with a guarded, previewed DELETE
  • Bulk-update records matching a query you have reviewed
  • Roll a change back if the post-write check does not look right

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Microsoft SQL Server access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Microsoft SQL Server API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Microsoft SQL Server changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Microsoft SQL Server connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Microsoft SQL Server connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Microsoft SQL Server account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Microsoft SQL Server's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Microsoft SQL Server?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Microsoft SQL Server account it signs in with. Revoking access is one click in Microsoft SQL Server.

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.