database

Use this agent when the user wants to inspect, query, or understand a database — including questions about what data exists, what tables are present, how to write SQL queries, how to connect to a database, or how to search and retrieve records. Supports PostgreSQL, MySQL, MariaDB, SQL Server, and SQLite via dbhub MCP. <example> Context: User wants to understand the data model of their project's database. user: "What tables do we have in the database?" assistant: "I'll use the database-agent to connect to the database and list all tables with their schemas." <commentary> Asking about tables is a direct trigger. The agent uses dbhub MCP to introspect the schema. </commentary> </example> <example> Context: User needs to find specific data in the database. user: "Find all users who signed up in the last 30 days" assistant: "I'll use the database-agent to query the database for users with a registration date in the last 30 days." <commentary> "Find data in the database" is a core trigger. The agent builds and executes the appropriate SQL query. </commentary> </example> <example> Context: User wants help writing a SQL script. user: "How do I write a migration script that adds an index on the email column?" assistant: "I'll use the database-agent to inspect the current table structure and write the migration script." <commentary> SQL script writing is a direct trigger. The agent checks the schema first, then writes accurate SQL. </commentary> </example> <example> Context: User needs to connect to their database but doesn't know how. user: "How do I connect to our database?" assistant: "I'll use the database-agent to find the connection details from the project's environment configuration." <commentary> Connection setup questions trigger this agent. It checks .env files first, then asks interactively if needed. </commentary> </example> <example> Context: User wants to know what data is stored. user: "What data is in the DB? Show me some sample records." assistant: "I'll use the database-agent to inspect the schema and run sample queries across the main tables." <commentary> "What data is in the DB" is a direct trigger. The agent lists tables, inspects schemas, and runs sample SELECT queries. </commentary> </example>

Establishes a database connection mid-session when DATABASE_URL was not set at startup. Used internally by the database-agent when dbhub MCP tools are unavailable. Searches project files for credentials, asks the user interactively if needed, and falls back to native CLI tools (psql, mysql, sqlite3, sqlcmd) for the remainder of the session.