Set up the SQL Server Toolbox MCP server
SQL Server Toolbox is a hosted Mintive (formerly MintMCP) connector, built on Google's MCP Toolbox, that exposes SQL and schema tools against a single Microsoft SQL Server database. You choose which tools it exposes (a ready-made table listing plus your own parameterized SQL) by declaring them in a configuration value.
Prerequisites
- A Mintive admin account
- A SQL Server database Mintive can reach: a managed instance (e.g., Azure SQL Database, Azure SQL Managed Instance, Amazon RDS for SQL Server, Cloud SQL for SQL Server), any host reachable over the internet, or a server inside your network reached through a Private Network
- Credentials for a SQL Server login, since the connector uses SQL authentication
Create a connector user
All users of this connector share a single database connection using the user you configure, so create a dedicated, least-privilege user rather than reusing sa or an admin login.
- Connect to your server as a user with sufficient privileges and create a login, then map it to a user in your database with read access. Replace
mydbwith your database name and choose a strong password:
CREATE LOGIN mintmcp_ro WITH PASSWORD = 'choose-a-strong-password';
GO
USE mydb;
CREATE USER mintmcp_ro FOR LOGIN mintmcp_ro;
ALTER ROLE db_datareader ADD MEMBER mintmcp_ro;
On Azure SQL Database, where server logins are optional, you can create a contained user directly in the database instead:
CREATE USER mintmcp_ro WITH PASSWORD = 'choose-a-strong-password';
ALTER ROLE db_datareader ADD MEMBER mintmcp_ro;
- The
mssql-list-tablestool reads the catalog views, which only show objects the user has some permission on. If you want it to describe tables the user can't read (for example, to document a schema without exposing its rows), also grant:
GRANT VIEW DEFINITION TO mintmcp_ro;
A few things to keep in mind:
db_datareadercovers only the database you run it in. If your data lives in several databases, map the login and add the role in each one, and remember that each connector still connects to a single database.- The user is the real boundary on what the connector can do. If you expose write or arbitrary-SQL tools (see below), they can only run what this user is granted, so keep it read-only unless you intend to allow writes.
Choose how Mintive reaches the database
The setup dialog asks for an Authentication Method, which is how the connector reaches your database:
- Direct connection if the database is reachable from the internet, usually behind an IP allowlist
- Private Network if it's only reachable inside your infrastructure
Direct connection
SQL Server Toolbox uses a dedicated egress IP shown on its Mintive connector settings page.
- In Mintive, go to MCP store > Manage store and open the SQL Server Toolbox connector page.
- Note the Egress IP shown there.
- If your database or its firewall / security group restricts inbound traffic, add that IP to the allowlist and confirm port
1433is open. For Azure SQL Database, add it as a server-level firewall rule; for Amazon RDS, add it to the instance's security group.
Private Network
Set up a Private Network with a route to the database that has Hosted connectors enabled, and note the route's name or pnrte_... id. The connector dials that route instead of a hostname, so the database needs no public listener or allowlist.
Through a route, the driver sees the address Mintive supplies rather than your server's hostname, so every MSSQL_ENCRYPT value that checks the certificate (false, true and strict) fails. Leave MSSQL_ENCRYPT unset.
Define the tools
The connector exposes only the tools you declare in the TOOLBOX_TOOLS environment variable. Every tool runs against the database you configure in Add SQL Server Toolbox to Mintive, so tools never set a source. Each tool has a kind and an optional description, and you can group tools into named toolsets.
There are two categories of tools:
- Ready-made tools:
mssql-list-tableshas its query built in and exposes its own input parameters (an optional comma-separatedtable_namesfilter, andoutput_formatset tosimplefor names only ordetailed), so it never takes astatement. - Custom SQL tools:
mssql-sqlruns a fixed, parameterizedstatementyou write, with parameters referenced as@name;mssql-execute-sqlruns an arbitrary statement supplied by the caller.
{
"tools": {
"list_tables": { "kind": "mssql-list-tables", "description": "List tables in the database." },
"get_customer": {
"kind": "mssql-sql",
"description": "Look up a customer by id.",
"statement": "SELECT id, name, created_at FROM customers WHERE id = @id",
"parameters": [
{ "name": "id", "type": "integer", "description": "Customer id." }
]
},
"execute_sql": { "kind": "mssql-execute-sql", "description": "Execute an arbitrary SQL statement." }
},
"toolsets": {
"read": ["list_tables", "get_customer"],
"write": ["execute_sql"]
}
}
Available tools
Pick a category to see what each tool returns, then expand Copy as JSON to grab a ready-to-paste config for that category. mssql-list-tables needs only a kind and a description; mssql-sql and mssql-execute-sql are the custom SQL tools.
- Custom SQL
- Schema
| Kind | Required fields | Purpose |
|---|---|---|
mssql-sql | statement, plus parameters (bound @name) and/or templateParameters ({{.name}}) | A fixed query you define and expose as a single tool |
mssql-execute-sql | none | Run an arbitrary SQL statement passed by the caller (read or write) |
Copy as JSON
{
"tools": {
"top_customers": {
"kind": "mssql-sql",
"description": "Highest-spending customers.",
"statement": "SELECT TOP (@limit) name, total FROM customers ORDER BY total DESC",
"parameters": [
{ "name": "limit", "type": "integer", "description": "Number of rows to return.", "default": 10 }
]
},
"execute_sql": { "kind": "mssql-execute-sql", "description": "Execute an arbitrary SQL statement." }
},
"toolsets": { "sql": ["top_customers", "execute_sql"] }
}
| Kind | Returns |
|---|---|
mssql-list-tables | Table schema: columns, constraints, indexes, and triggers (or names only with output_format: simple) |
Copy as JSON
{
"tools": {
"list_tables": { "kind": "mssql-list-tables", "description": "List table schema." }
},
"toolsets": { "schema": ["list_tables"] }
}
SQL Server-only lock
The connector only talks to SQL Server. If TOOLBOX_TOOLS declares its own sources or uses a tool kind outside mssql-*, the connector refuses to start and logs the reason, so it never connects anywhere unexpected.
Add SQL Server Toolbox to Mintive
- Go to app.mintmcp.com/vmcps?tab=manage-store.
- Find SQL Server Toolbox and click to install it.
- Pick the Authentication Method you chose in Choose how Mintive reaches the database and fill in its fields.
- Direct connection
- Private Network
| Field | Value |
|---|---|
Host (MSSQL_HOST) | Database hostname or IP |
Port (MSSQL_PORT) | Port, pre-filled with 1433 |
Database (MSSQL_DATABASE) | Database name |
User (MSSQL_USER) | Database user (e.g., mintmcp_ro) |
Password (MSSQL_PASSWORD) | User password, stored as a secret |
Tool Definitions (TOOLBOX_TOOLS) | The tool definitions (see Define the tools) |
To change encryption, add MSSQL_ENCRYPT (disable, false, true, or strict) as a Global environment variable after installing. It isn't in the setup dialog.
Click Save. On startup the connector connects to your database and loads your tools, and it becomes available once the connection succeeds. If the database is unreachable or TOOLBOX_TOOLS is invalid, the connector fails to start and its logs say why.
| Field | Value |
|---|---|
Private Network Route (MSSQL_PRIVATE_NETWORK_ROUTE) | The route's name or pnrte_... id |
Database (MSSQL_DATABASE) | Database name |
User (MSSQL_USER) | Database user (e.g., mintmcp_ro) |
Password (MSSQL_PASSWORD) | User password, stored as a secret |
Tool Definitions (TOOLBOX_TOOLS) | The tool definitions (see Define the tools) |
Then:
- Click Save. The store installs the connector outside any network, so it starts with no tools and its logs say it isn't in a Private Network yet.
- Move it into the network that owns the route. It restarts, connects through the route, and loads your tools.
If the route can't be used, for example because the network has no route with that name or two routes share it, the connector fails to start and its logs say why.
Security considerations
- Every user queries your database as the single configured user, so use a read-only, least-privilege user unless you intend to allow writes.
- The SQL Server-only lock prevents the connector from reaching other databases or services, but it does not restrict SQL operations. The
mssql-execute-sqltool and any writemssql-sqltools can run whatever the user is granted, so the database user is the real guardrail. Omit those tools, or keep the user read-only, to prevent writes. - Connection details are stored as Mintive global environment variables; the password is held as a secret.
- For managed or remote databases reached directly over the internet, add
MSSQL_ENCRYPT=trueafter installing so the server certificate is verified. - Combine the dedicated egress IP with a database firewall allowlist so only Mintive can reach the database, or use a Private Network so the database needs no public listener at all.
Next steps
- Tool customization: Control which tools are exposed to users
- MCP gateway administration: Manage access and permissions
- Private Networks: Reach databases inside your infrastructure