Quick Configuration
Choose the setup that matches your environment.
Before You Start
- Confirm you have the account, endpoint, or API key required for SQLite.
- Start with minimum scopes and read-only access where possible.
- Keep secrets in environment variables instead of hardcoding them in JSON.
Last verified: 2026-06-13
Environment: uvx with mcp-server-sqlite over stdio
Install command:
uvx mcp-server-sqlite --db-path /path/to/database.dbLocal config
JSON Local config json
{
"sqlite": {
"command": "uvx",
"args": ["mcp-server-sqlite", "--db-path", "/path/to/database.db"]
}
}After copying
Check the SQLite JSON before running it in OpenClaw, then verify the server with a real prompt.
Verify prompt
List all tables and describe their columns.
Expected success output
You should see the table list and column definitions for the SQLite file.
Common Pitfalls & Fixes
- ⚠️ Watch out: File path permissions and safely running write queries.
- 🔑 Always store API keys in environment variables, never hardcode them in JSON.
- 🛡️ Start with read-only scopes if available to verify connection safely.
Security checklist
- Point --db-path at a specific database file, not a directory of unrelated data.
- Back up the database before allowing any write queries.
Common errors
| Error | Cause | Fix |
|---|---|---|
uvx not found | uv is not installed or not on PATH. | Install uv (which provides uvx), or use pipx to install the server. |
unable to open database file | The --db-path is wrong or unreadable. | Use an absolute path to an existing .db file the process can read. |
attempt to write a readonly database | The file or directory is not writable. | Grant write permission only if you intend to run write queries. |
Example Prompts
Once connected, try these prompts to test capabilities:
- List all tables and describe their columns.
- Run a sample query to fetch the latest 20 rows from a table and summarize patterns.
- Find the top 10 most frequent values in a chosen column and return counts.
Verification Checklist
- Run 1-2 real prompts to confirm SQLite returns usable data.
- Check that error messages are clear enough for troubleshooting.
- Document the required scopes, dependencies, and env vars for future reuse.