Customization

1DevTool MCP Tools in Grok

New Grok sessions can discover and run your 1DevTool database and HTTP tools over MCP, so Grok can query a connection or fire a saved request without leaving the terminal. MCP Settings now lists and manages Grok alongside Claude Code, Gemini CLI, Codex, and OpenCode.

Screenshot coming soon

Why You Need This

How this feature boosts your daily productivity

An AI agent that cannot reach your database or your HTTP client spends its turns asking you to paste things in. Grok already ran as a first-class agent in 1DevTool; what it lacked was the tools. Wiring 1DevTool's MCP server into Grok's config means Grok can inspect a schema, run a read query, or replay a saved request itself — and because MCP Settings treats Grok like every other agent, installing and uninstalling that server is one click rather than hand-editing TOML.

How It Works

Get started in 4 simple steps

1
1

Open Settings → MCP

MCP Settings lists servers configured across Claude Code, Gemini CLI, Codex, OpenCode, and Grok. Grok reads from ~/.grok/config.toml.

2
2

Install the 1DevTool server

One click writes the shared server entry into Grok's config under the key onedevtool, alongside whatever else Grok already has.

3
3

Start a new Grok session

New sessions discover the tools on connect. Existing sessions need a restart to pick up the config change.

4
4

Let Grok use your tools

Grok can call the database tools (list_connections, describe_schema, query, preview_table) and HTTP tools (request, list_saved_requests, run_saved_request, list_environments).

Without 1DevTool

The manual way vs. the 1DevTool way

The Hard Way

# Ask Grok about a table
# Grok can't see your database
# Open the DB client yourself
# Run the query, copy the rows
# Paste them back into the prompt
# Repeat for every schema question

The 1DevTool Way

Grok discovers your 1DevTool tools on connect.
It queries the connection and reads the schema itself.
Saved HTTP requests too — no copy-paste relay.

Key Capabilities

Everything included with 1DevTool MCP Tools in Grok

Expose 1DevTool's database tools to Grok over MCP
Expose the HTTP client's saved requests and environments to Grok
Install or uninstall the 1DevTool server in Grok with one click
View Grok's configured MCP servers next to every other agent
Share one server entry across Claude, Gemini, Codex, OpenCode, and Grok
Read and write Grok's ~/.grok/config.toml without hand-editing TOML

Why It Matters

The productivity impact of having customization built into your workspace

No copy-paste relay

Grok reads your schema and runs your saved requests itself instead of asking you to paste results.

One server, every agent

The same MCP entry serves Claude, Gemini, Codex, OpenCode, and Grok.

No TOML by hand

MCP Settings writes ~/.grok/config.toml for you, one click to install or remove.

Ready to boost your workflow?

Download 1DevTool for free and experience 1DevTool MCP Tools in Grok along with 170 other features — all in one app.