Strut Stack SQL

Light strut. Extreme load.

A token-efficient MCP server that lets AI agents query PostgreSQL , MySQL , SQLite , DuckDB , ClickHouse , and SQL Server — safely, in one small Rust binary.

⭐ If this saves you tokens, star the repo — it is the single biggest thing that helps other people find it.

---

Install in one command — binary + AI setup included

This is the fastest path. It downloads the release binary (SHA256-verified), then configures every AI tool it finds on your machine — Claude Code, Cursor, VS Code, Claude Desktop, Codex, OpenCode, Windsurf, and Zed — so you do not hand-edit a single JSON file. Existing entries for other servers are kept, and every file it touches is backed up first.

curl -fsSL https://raw.githubusercontent.com/rzlco666/strut-stack-sql/main/install.sh | bash -s -- --setup

With your database URL baked in (recommended):

curl -fsSL https://raw.githubusercontent.com/rzlco666/strut-stack-sql/main/install.sh | bash -s -- --setup --database-url 'postgresql://user:pass@localhost:5432/mydb'

Other useful forms:

# Only specific tools

curl -fsSL https://raw.githubusercontent.com/rzlco666/strut-stack-sql/main/install.sh | bash -s -- --setup --tools cursor,vscode,opencode

Project-local configs (.cursor/mcp.json, .vscode/mcp.json, .mcp.json, opencode.json, .codex/config.toml)

curl -fsSL https://raw.githubusercontent.com/rzlco666/strut-stack-sql/main/install.sh | bash -s -- --setup --project

Binary already installed? Just do the setup step

curl -fsSL https://raw.githubusercontent.com/rzlco666/strut-stack-sql/main/install.sh | bash -s -- --setup --skip-install

Install only, no setup

curl -fsSL https://raw.githubusercontent.com/rzlco666/strut-stack-sql/main/install.sh | bash

Then restart your AI tool and ask it:

"List the tables in my database, then show me the 5 most recent orders."

You should see the tables listed, then the 5 most recent orders.

If you run the installer without a URL, configs reference ${env:DATABASE_URL} (or forward it, for Codex) — export DATABASE_URL in the environment that launches your editor before starting it. Full installer reference: docs/INSTALL.md.

One-click install

No terminal? These links open your editor with the server pre-filled. Replace the placeholder database URL with your own where prompted.

GitHub does not render cursor:// / vscode: links clickable. If a button above does not open your editor, paste this into your browser's address bar instead:

vscode:mcp/install?%7B%22command%22%3A%22strut-stack-sql%22%2C%22args%22%3A%5B%22--url-env%22%2C%22DATABASE_URL%22%2C%22--full-tools%22%5D%2C%22env%22%3A%7B%22DATABASE_URL%22%3A%22%24%7Binput%3Adatabase_url%7D%22%7D%2C%22inputs%22%3A%5B%7B%22type%22%3A%22promptString%22%2C%22id%22%3A%22database_url%22%2C%22description%22%3A%22DATABASE_URL%20for%20strut-stack-sql%20%28e.g.%20postgresql%3A%2F%2Fuser%3Apassword%40localhost%3A5432%2Fdbname%29%22%2C%22password%22%3Atrue%7D%5D%7D

Set up by hand (copy-paste)

Prefer the installer above. If you configure by hand, every block below is read-only by default: 13 tools (3 core + 10 introspection), no writes, no DDL. Replace DATABASE_URL with your real URL, or keep --url-env DATABASE_URL and export it. Every block is also machine-checked in docs/CLIENTS.md.

Claude Code

claude mcp add --scope user --transport stdio \

--env DATABASE_URL='postgresql://user:pass@localhost:5432/mydb' \ strut-stack-sql -- strut-stack-sql --url-env DATABASE_URL --full-tools

Or in .mcp.json (project) — Claude Code expands ${VAR} here:

{

"mcpServers": { "strut-stack-sql": { "type": "stdio", "command": "strut-stack-sql", "args": ["--url-env", "DATABASE_URL", "--full-tools"], "env": { "DATABASE_URL": "postgresql://user:pass@localhost:5432/mydb" } } } }

Check it with claude mcp get strut-stack-sql (or /mcp inside a session).

Cursor

Global ~/.cursor/mcp.json, or project .cursor/mcp.json. Cursor interpolates ${env:NAME}, so this works with an exported DATABASE_URL and no secret in the file:

{

"mcpServers": { "strut-stack-sql": { "type": "stdio", "command": "strut-stack-sql", "args": ["--url-env", "DATABASE_URL", "--full-tools"], "env": { "DATABASE_URL": "${env:DATABASE_URL}" } } } }

VS Code

Workspace .vscode/mcp.json (or the user configuration via MCP: Open User Configuration). Note: VS Code uses a top-level servers object, not mcpServers — do not paste a Cursor block here unchanged:

{

"servers": { "strut-stack-sql": { "type": "stdio", "command": "strut-stack-sql", "args": ["--url-env", "DATABASE_URL", "--full-tools"], "env": { "DATABASE_URL": "${env:DATABASE_URL}" } } } }

Claude Desktop

claude_desktop_config.json (~/Library/Application Support/Claude/ on macOS, ~/.config/Claude/ on Linux):

{

"mcpServers": { "strut-stack-sql": { "command": "strut-stack-sql", "args": ["--url-env", "DATABASE_URL", "--full-tools"], "env": { "DATABASE_URL": "postgresql://user:pass@localhost:5432/mydb" } } } }

Codex

~/.codex/config.toml (or project .codex/config.toml). Codex uses TOML, not JSON:

[mcp_servers.strut-stack-sql]

command = "strut-stack-sql" args = ["--url-env", "DATABASE_URL", "--full-tools"] env = { DATABASE_URL = "postgresql://user:pass@localhost:5432/mydb" } startup_timeout_sec = 20

No URL in the file? Use env_vars = ["DATABASE_URL"] instead of env to forward it from Codex's environment.

OpenCode

The CLI is the version-proof path (it writes the right shape for your OpenCode):

opencode mcp add strut-stack-sql --env DATABASE_URL='postgresql://user:pass@localhost:5432/mydb' -- strut-stack-sql --url-env DATABASE_URL --full-tools

Or in opencode.json (global ~/.config/opencode/opencode.json, or project root). command is one array and env vars go in environment, not env:

{

"$schema": "https://opencode.ai/config.json", "mcp": { "strut-stack-sql": { "type": "local", "command": ["strut-stack-sql", "--url-env", "DATABASE_URL", "--full-tools"], "enabled": true, "environment": { "DATABASE_URL": "postgresql://user:pass@localhost:5432/mydb" }, "timeout": 30000 } } }

Verify with opencode mcp list. On OpenCode v2, if the server does not appear, nest it under mcp.servers instead of directly under mcp.

Windsurf

~/.config/devin/mcp_config.json (current builds; older builds read ~/.codeium/windsurf/mcp_config.json — use whichever Open MCP config file in Cascade opens):

{

"mcpServers": { "strut-stack-sql": { "command": "strut-stack-sql", "args": ["--url-env", "DATABASE_URL", "--full-tools"], "env": { "DATABASE_URL": "postgresql://user:pass@localhost:5432/mydb" } } } }

Press refresh in Cascade after editing.

Zed

~/.config/zed/settings.json (merged under context_servers, everything else kept):

{

"context_servers": { "strut-stack-sql": { "command": "strut-stack-sql", "args": ["--url-env", "DATABASE_URL", "--full-tools"], "env": { "DATABASE_URL": "postgresql://user:pass@localhost:5432/mydb" } } } }

Any other MCP client

This is the whole contract — stdio, one binary, one env var:

{

"mcpServers": { "strut-stack-sql": { "command": "strut-stack-sql", "args": ["--url-env", "DATABASE_URL", "--full-tools"], "env": { "DATABASE_URL": "postgresql://user:pass@localhost:5432/mydb" } } } }

Try it

Once your AI tool shows the server as connected, these prompts exercise the whole surface. Start read-only; writes and DDL stay off until you explicitly enable them (see Tools).

"List the tables in my database, with row counts."

"Show me the schema of the orders table, including its foreign keys." "Why is this query slow, and which index would fix it?" (paste any SELECT — analyze_query_performance returns an EXPLAIN tree, tiered findings, and index advice; the advice is text only, never executed) "Find every table that references customers.id."

What the agent sees: execute_sql returns columnar JSON — column names once, compact meta:

{

"ok": true, "data": { "cols": ["id", "email", "name"], "rows": [[42, "ada@example.com", "Ada"]], "meta": { "n": 1, "truncated": false, "limit_injected": true } } }

Smoke-test the binary itself (no database needed) — a JSON initialize response means the server speaks MCP:

echo '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"smoke","version":"0"}}}' \

| strut-stack-sql --url 'sqlite::memory:' --full-tools

Connect your database

One URL, one flag. Credentials belong in the environment (or .env discovery in your project), never in a pasted config — prefer --url-env DATABASE_URL.

| DuckDB | duckdb:///absolute/path/analytics.duckdb, `duckdb::memory