Connecting SQL Server
Greppilot integrates with SQL Server databases to allow AI agents to interact with your data programmatically. This integration enables schema introspection, read-only querying, and dynamic tool generation based on your database structure.
Connection String
To connect Greppilot to your SQL Server instance, provide a valid connection string. This string follows a standard URL format and specifies all necessary details for establishing a connection.
Greppilot encrypts your connection string at rest using industry-standard encryption.
{
"connectionString": "mssql://user:password@hostname:port/database?options"
}
Parameters
The only required configuration parameter for SQL Server integration is connectionString.
| Parameter | Type | Description |
|---|---|---|
connectionString | string | The full connection string for your SQL Server database. Must be a valid URL starting with mssql:// or sqlserver://. Example: mssql://greppilot_user:mysecret@my-sql-server.example.com:1433/prod_db |
Greppilot validates all connection strings to prevent Server-Side Request Forgery (SSRF) attacks. Connections to private IP ranges (e.g., 169.254.x.x) or hostnames containing "metadata" are blocked.
What You Can Do
Once connected, the Greppilot agent can interact with your SQL Server database:
- Query your data — Ask questions in plain English and the agent writes and executes read-only SQL queries on your behalf.
- Explore your schema — Ask the agent what tables and columns are available in your database.
- Refresh the schema — If your database structure changes, ask the agent to re-introspect and update its understanding.
All queries are read-only. The agent only executes SELECT statements against your database.