Back to JetBrains

AI Agents for SQL and Databases in DataGrip

JetBrainsAugust 26, 202613m

Topics9

Getting Started with AI Agents in DataGrip0:02 Creating Data Sources Using AI Agents0:30 Querying Data Sources Through AI3:31 Executing SQL Queries Automatically5:31 Database Schema Management7:01 Reviewing Past Activities9:01 Mentioning Database Objects9:30 Working with Files11:00 Conclusion13:01

In a Nutshell

DataGrip's AI agents connect directly to databases via MCP tools, letting users create data sources, query schemas, and run SQL through natural language conversation. The agent can discover connections from other tools, analyze database structure, execute read queries, and even drop objects after safety checks, with all permissions managed in IDE settings. Users can reference specific database objects or files using @mentions, and the AI provides detailed explanations while maintaining security by never receiving actual credentials.

AI-Generated Notes

These notes were generated by AI and may contain inaccuracies.

Once the AI assistant plugin is installed, the AI assistant button appears in the top toolbar. Clicking it opens the tool window, where users can choose between chat mode or any agent installed on the machine. Available agents include Claude, Codex, Gemini, or any other agent from the ACP registry. Claude is used for this demonstration.

There might be a need to configure the MCP server for the specific agent. Refer to DataGrip's documentation to accomplish this.

Method 1: Using JDBC URL

The simplest method to create a data source is to use a JDBC URL. Type "create data source from URL" and paste the URL into the agent chat. Claude first asks for permission to run a skill called database connection management. Once allowed, Claude requests permission to run the MCP tool called create database connection. After allowing this, it asks for credentials since they aren't transferred via the URL. After entering username and password, the data source is created and visible in the database explorer tool window, complete with all its objects.

A connection is created within DataGrip, and credentials are never passed to the AI agent.

Method 2: Providing Connection Details Directly

Another straightforward way to create a data source is to provide the agent with all known connection details. Type "create another data source" and specify the database type (MySQL), host (locally), port (33081), and database name (guest). Claude asks to use the database connection management skill, then prompts for credentials. After entering credentials and clicking okay, the second data source is created. All details are visible in the chat, the test connection is successful, and objects are visible in the database explorer.

Method 3: Exporting Connections from Other Tools

The agent can locate relevant files for any database tools installed and import the connections. Type "find my connections in pgAdmin and import them here." Claude searches for where pgAdmin connections are stored on the computer. After granting permissions, two servers are found in pgAdmin and appear on the left side of the screen. Username and password must be entered for both. Once completed, the data sources are ready to use. The agent provides details about these connections in the chat and they appear in database explorer. They aren't automatically introspected, but can be manually refreshed to see all underlying objects.

Because the AI agent knows about data sources, users can essentially talk to their connections. For example, asking "In which schema do I have data about employees?" triggers Claude to use MCP DataGrip tools. Claude asks permission to read the database schema. After allowing this, Claude provides the answer and displays the relevant table. The locally hosted MySQL data source contains a database with employee data.

When asked "Tell me about this database. What is it about? What tables are there and how are they connected?" regarding the Sakila database and PG AI data source, Claude requests permission to read the database schema. The actual SQL query that Claude intends to run is displayed, with a warning that the statement will read database data. After reviewing and allowing, multiple queries are prompted. Checking the box for "always allow Claude code to read database data" prevents future confirmation prompts. Claude provides information about where the database is hosted, how tables are connected, and other important details, giving a complete schema overview.

Sign in to read the full notes

Get access to AI-generated notes, topic timestamps, and more.