Connect Claude to SQL Server | MSSQL MCP Server Setup

If you have data sitting in Microsoft SQL Server — case files, customer records, sales history, inventory, whatever your line-of-business application stores — there's a good chance you've wanted to ask Claude about it without writing SQL yourself or hiring someone to build a custom dashboard.

This guide walks through exactly how to do that. By the end, you'll have Claude Desktop talking directly to your SQL Server database, ready to answer questions in plain English.

The whole setup takes about 60 seconds.

What you'll need

Before you start, make sure you have:

A SQL Server instance that's reachable from the internet. This works with Azure SQL Database, Azure SQL Managed Instance, AWS RDS for SQL Server, Google Cloud SQL for SQL Server, on-prem SQL Server with a public IP, or a SQL Server instance running on a VPS. SQL Server 2014 and newer are supported. SQL Server Express works too.
A SQL Server user with read access to the database you want Claude to query. We strongly recommend creating a dedicated user with read-only permissions specifically for this — more on why below.
Claude Desktop installed on your Mac or PC. If you don't have it yet, download it from Anthropic.
A Synra account. Free to start at mcpserver.design.

That's it. You don't need to install any local software, edit configuration files, or set up any kind of bridge or proxy on your own machine.

Why you need an MCP server at all

Claude itself can't reach into a database. It only talks to the outside world through something called an MCP server (Model Context Protocol server) — a small piece of software that exposes tools Claude can use, like "list tables" or "run a query."

The traditional way to set one up is to install an open-source MCP server on your own machine, edit Claude Desktop's config files to point at it, and manage your database credentials in a .env file. It works, but it's fiddly. And if you want Claude to query SQL Server from a different machine, you have to set it all up again.

Synra is a managed SQL Server MCP server. You paste your database credentials into a web dashboard, Synra encrypts them and hosts the MCP server for you, and you get back a URL. Paste that URL into Claude Desktop and you're done — Claude can now query your SQL Server through Synra's gateway, with read-only safety built in.

Step 1: Sign up for Synra

Head to mcpserver.design and create a free account. You can use email and password or sign in with Google. The free tier lets you connect one database, which is plenty for testing.

Step 2: Add your SQL Server connection

In the Synra dashboard, click Add Connection and choose Microsoft SQL Server (also labeled MSSQL in some places).

You'll need to fill in:

Host — the address of your SQL Server. For Azure SQL this looks like yourserver.database.windows.net. For AWS RDS it looks like yourdb.xxxxx.us-east-1.rds.amazonaws.com. For on-prem or VPS, it's the IP address or hostname.
Port — usually 1433 (the SQL Server default). If your DBA changed it, use what they changed it to.
Database — the name of the specific database you want to connect, e.g. production, crm, salesdata.
Username — the SQL Server login.
Password — the password for that login.
Encrypt connection — leave this on if your SQL Server supports it (most modern setups do).

Give the connection a name you'll recognize — "Production DB" or "CRM" or similar — and save.

Synra encrypts your password with AES-256 the moment you submit the form. The plaintext password is never stored.

Step 3: Copy your MCP endpoint URL

After you save the connection, Synra generates a unique MCP endpoint URL that looks like this:

https://app.mcpserver.design/api/mcp/abc123xyz

This URL is yours alone — it's the address Claude will use to talk to your SQL Server through Synra. Copy it to your clipboard.

Step 4: Add the endpoint to Claude Desktop

Open Claude Desktop. In the left sidebar, click Customize, then select Connectors.

Click the + button at the top right of the connector list and choose Add custom connector. A dialog appears with two fields you need to fill in:

Name — anything memorable, like "SQL Server" or "Production Database"
Remote MCP server URL — paste your Synra endpoint URL

Leave the Advanced settings (OAuth Client ID and Secret) blank — you don't need them.

Click Add. Claude connects to Synra, and Synra connects to your SQL Server. Within a few seconds, the new connector appears in your connector list and is ready to use. No config files, no command-line tools, no local bridges.

Step 5: Ask Claude about your data

You're done. Start a new conversation in Claude Desktop and try a few questions:

"What tables are in my database?"
"Show me the schema of the orders table."
"How many customers did we add last month?"
"What were our top 10 products by revenue in Q1?"
"Find any rows in the invoices table where the status is 'overdue' and the amount is over $5,000."

Claude will translate your question into SQL, send it through Synra to your SQL Server, get the results back, and explain them to you in plain English. You don't write a single line of SQL.

What you can actually do with this

Once Claude is connected to your SQL Server, the practical uses fall into a few categories:

Exploratory analysis. Ask questions you'd normally need a BI tool or a SQL-fluent analyst to answer. "Which clients have we lost in the last 6 months?" "What's our average invoice payment time, and how has it changed year over year?"

Reporting without dashboards. Skip the Tableau/Power BI build-out for one-off reports. Ask Claude to summarize anything in your database and copy the answer into a doc or email.

Data spot-checks. "Are there any orders with no associated customer?" "How many records in this table are missing a value in the email column?" Useful for catching data quality issues before they hit production.

Onboarding new tools. When you're integrating SQL Server with another system, Claude can help you understand the existing schema, suggest joins, and sanity-check assumptions — without you needing to write exploratory queries by hand.

Security: what Synra does and doesn't do

This is the part most people skim. Don't.

What Synra does:

Encrypts your SQL Server credentials with AES-256 at rest. They're only decrypted at request time, in memory, to make the connection to your database.
Enforces read-only by default. The Synra MCP gateway blocks destructive SQL keywords (DROP, DELETE, UPDATE, INSERT, ALTER, TRUNCATE, CREATE, GRANT, REVOKE) before they reach your database. Even if Claude tries to generate a destructive query, it won't make it through.
Logs every request for audit. You can see what queries were run and when.
Never stores your data. Query results pass through Synra to Claude — they aren't retained on Synra's servers.

What you should do as well:

Create a dedicated read-only SQL Server user just for Synra. Don't reuse your application's database user. This way, even if something goes wrong, the Synra user has no permissions to modify anything anyway. Belt and suspenders.
Restrict the user to the specific databases you want Claude to access. Don't give it server-wide read access if you only want it to see one database.
Consider IP allowlisting. If your SQL Server supports firewall rules (Azure SQL definitely does), you can restrict connections to Synra's IP range for an extra layer.

The read-only-by-default design is the most important guarantee. It means you can experiment freely — there's nothing Claude can do that will damage your data.

SQL Server MCP — Frequently Asked Questions

Does this work with Azure SQL Database? Yes. Azure SQL Database, Azure SQL Managed Instance, and SQL Server on Azure VMs all work the same way. Use your Azure SQL hostname (ends in .database.windows.net), port 1433, and a SQL authentication login.

Does this work with on-prem SQL Server? Yes, as long as the SQL Server is reachable from the internet. If it's behind a firewall, you'll need to either expose it (with appropriate firewall rules), put it behind a VPN that Synra can reach, or run it on a server with a public IP. Self-hosted on a VPS or rented dedicated server works out of the box.

What SQL Server versions are supported? SQL Server 2014 and newer. SQL Server Express, Standard, and Enterprise editions are all supported. Older versions (2012 and below) may work but aren't officially tested.

Can Claude modify or delete data in my SQL Server? No, by default. Synra's gateway blocks all destructive SQL operations before they reach your database. Even if Claude generates a DELETE or UPDATE statement, Synra rejects it. If you specifically want to allow writes, that's an enterprise feature that requires explicit configuration — it's off by default for everyone.

What about Windows Authentication? Synra connects using SQL Server authentication (username + password). Windows Authentication (Active Directory / Entra ID) isn't currently supported because Synra's servers aren't joined to your domain. Most cloud SQL Server deployments use SQL authentication anyway. For on-prem, create a SQL login specifically for Synra.

How fast is it? Query latency is dominated by your SQL Server's own response time. Synra adds 50–200ms of overhead on top, mostly for the round-trip to Synra's servers and back. For typical analytical queries on indexed columns, you won't notice the difference.

What if my SQL Server has hundreds of tables? Claude handles this fine. The first thing it does is ask Synra to list tables, and from there it picks the relevant ones for your question. You can also tell Claude up-front which tables to focus on — "I want to ask questions about the orders and customers tables" — to keep its responses focused.

Try it

If you have SQL Server data and you've been wanting Claude to be useful against it, this is the fastest path:

Sign up at mcpserver.design
Add your SQL Server connection
Paste the URL into Claude Desktop

Sixty seconds, no developer required. The managed SQL Server MCP server is what you're looking for.