Connect Grok to your database.
Use the Grok Build CLI already signed in on your machine. Valv detects it, gives it read-only tools for your database, and shows every query and result in a desktop client.
Already have Valv? Go to the setup steps.
Grok handles the analysis. Valv handles the database connection.
Ask Grok inside Valv, with tables, charts, files, and the current selection beside the chat. Valv connects Grok to the active workspace for that conversation.
Use the Grok login you already have.
Valv launches the local Grok CLI with its cached login. Pick from the models available to that account and choose the reasoning level for a new chat.
Existing Grok login · no xAI key in Valv
Ask about the data in front of you.
Grok can inspect the allowed schema, query live data, and use the table open in Valv. Its answers link back to the query result behind each finding.
Source: cancellation totals · 4 rows
Setup
From an installed Grok CLI to your first database answer.
You connect Grok to Valv, not directly to a database password. The setup takes place on your machine.
- 1
Install and sign in to Grok Build.
Valv uses the local
grokcommand and its cached login. Run Grok once to complete browser authentication, then check that the command is available.
Grok Build installation guidegrok --version - 2
Pick Grok in Valv.
Valv scans the same shell environment you use in a terminal. Pick Grok during onboarding. If you installed it afterwards, open Settings, Providers, then select Re-scan.
- 3
Add your database.
Paste a PostgreSQL, MySQL, or ClickHouse connection string, try the experimental MongoDB support, or choose a local SQLite file. You can test the connection before saving. Valv stores secrets with your OS keychain.
postgres://user:password@host:5432/database - 4
Review AI access, then ask.
Valv makes the schemas you selected available to Grok. Before the first question, hide any table or column it should not inspect. Then open Ask and choose Grok for the new chat.
Which customer segments grew fastest this quarter?
The database tools are read-only.
Grok can discover the allowed schema and compose structured queries. Valv validates each query before it reaches the database. Grok does not receive tools to insert, update, delete, or run raw SQL.
Hide data before Grok discovers it.
AI access is separate from your own access in Valv. Hide a whole table or individual columns such as email and card number. You can still open that data yourself in the read-only table viewer.
AI access
Grok inside Valv
Valv attaches database tools for each chat.
Valv starts Grok Build through ACP and passes it a temporary, authenticated connection to the current workspace. The connection is scoped to that chat, so there is no MCP file to maintain.
Grok starts in the workspace files folder and keeps its native file, shell, and web tools. Valv disables plan mode and subagents for these direct chat turns.
Current workspace
Files and connected databases
Valv tools
Discover, query, cite
Grok and your database, answered
How do I connect Grok to a database?
Install and sign in to Grok Build, then open Valv Desktop. Valv detects the Grok CLI on your machine. Pick Grok as your agent, add a database, review its AI access, and ask your first question. You do not paste database credentials into Grok.
Do I need to configure MCP in Grok?
No, not for chat inside Valv. Valv starts Grok through the Agent Client Protocol and attaches an authenticated MCP connection pinned to that chat's workspace. For agents you run outside Valv, the MCP Server page in Settings exposes whichever workspace is active while the app is open.
Can Grok write to my database?
No. The database tools Valv gives Grok are read-only. Grok can inspect the allowed schema and run structured queries, but it does not receive database write tools. Valv's own table viewer is read-only too, so nothing in Valv writes to your database.
Which databases work with Grok through Valv?
PostgreSQL, MySQL and MariaDB, SQLite, and ClickHouse are supported. MongoDB support is experimental. You can connect more than one database to the same workspace and ask Grok to work across them.
What data is sent to Grok?
Valv keeps database credentials in your OS keychain and never sends them to Grok. Valv queries the database directly on your machine. The schema and query results Grok needs are processed through your signed-in Grok account, under your xAI account settings and terms.
Do I need an xAI API key in Valv?
No API key goes into Valv. Grok Build must already be installed and signed in on your machine. Valv uses the CLI's cached login, and usage follows the Grok account and plan you use with the CLI.
What else can Grok access during a Valv chat?
Grok keeps its native file, shell, and web tools. Valv starts it in the workspace files folder and approves tool requests for the current call. The read-only limit applies to Valv's database tools, not Grok's native tools.
Put Grok to work on your data.
Free for personal use, every feature included. Commercial use needs a seat at beta pricing. See pricing.