MCP & coding agents

After the stack is healthy, the installer installs the DeepSQL MCP server globally:

npm install -g @deepsql/mcp@latest

Auto-login

As of v1.0.2, the installer then authorizes the CLI against the local instance using your admin email and password — no browser callback, no device code:

echo "$DEEPSQL_INITIAL_ADMIN_PASSWORD" | deepsql login \
  --password \
  --email "$DEEPSQL_INITIAL_ADMIN_EMAIL" \
  --password-stdin \
  --url "http://localhost:9085"

A long-lived MCP token is persisted to ~/.config/deepsql/auth.json. Subsequent deepsql mcp invocations (which your coding agents run under the hood) work without re-auth.

When auto-login is skipped

Login is skipped if the admin credentials aren’t in your environment when you re-run the installer (e.g. a re-install where you’ve cleared them). In that case, install prints the manual command. Run it yourself with the credentials you remember:

deepsql login --password --email <admin-email> --url http://localhost:9085

Configure the agents

Then it prompts you to pick which coding agents to wire up:

  Which coding agent(s) will you use DeepSQL with?
  1) Claude Code
  2) Codex
  3) Cursor
  a) All of the above
  s) Skip

  Enter choice(s) separated by spaces (e.g. 1 3):

For each agent you pick, it runs:

deepsql mcp config --install --for <agent> --force

That command writes the MCP server configuration into the right location for that agent. --force overwrites any existing DeepSQL MCP block (it leaves other servers untouched).

Where each agent’s config goes

Claude Code

~/.claude.json — adds a deepsql entry under mcpServers. Claude Code picks it up on next launch.

Codex

~/.codex/config.toml — adds a [mcp_servers.deepsql] section.

Cursor

~/.cursor/mcp.json — adds a deepsql entry under mcpServers.

Add agents later

You can re-run any of these at any time without re-running the full installer:

npm install -g @deepsql/mcp@latest
deepsql mcp config --install --for claude-code --force
deepsql mcp config --install --for codex --force
deepsql mcp config --install --for cursor --force

Skipping MCP install entirely

If you don’t want any MCP wiring, just pick s (skip) at the prompt — or have npm missing from PATH (the installer skips MCP with a clear message in that case).