Verified

SQLite Bridge MCP Server

SQLite databases accessed via type-safe, validated tools over Stdio and HTTP transports.

Data last scanned today · Reviewed today

533 tools★ 1TypeScriptMIT

Overview

The SQLite Bridge MCP Server provides a modular interface for AI agents to interact with SQLite databases. It leverages Zod schema validation to ensure that all tool interactions remain type-safe, whether running locally via Stdio or remotely over the Streamable HTTP transport. Designed for flexibility, the server includes an error handler interceptor and a repository layer to manage database operations. It supports both local desktop environments and stateless remote deployments, ensuring consistent access patterns across different infrastructure setups.

Our verdict

This server carries a high risk level (33/100) due to its status as a community-maintained project rather than an official vendor release. Because the authentication method has not yet been editorially reviewed, users should exercise caution before deploying this in environments where data access control is critical. It is best suited for developers experimenting with SQLite integration who can independently verify the security posture of the codebase.

Supports both Stdio and Streamable HTTP transport modes
Uses Zod schema validation for robust parameter handling
Contains only 9 direct dependencies to minimize supply chain surface

Community-maintained with no official vendor backing
Security score of 33/100 indicates significant unverified risks
Read-only mode and authentication methods remain unreviewed

Setup

Claude Desktop

{
  "mcpServers": {
    "mcp-sqlite-bridge": {
      "args": [
        "-y",
        "mcp-server"
      ],
      "command": "npx"
    }
  }
}

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.

No read-only mode — running this grants full read/write access.
No built-in authentication — anyone with access to this config can invoke every tool it exposes.

Tools

Tool	Description	Risk
query_data_source	Retrieves records matching the requested category/domain (e.g. headcount, internal_metrics, engineering_delivery).	low
add_database_record	Inserts a new record into the database table.	medium
update_database_record	Modifies an existing database row by its unique ID.	medium

Compatibility

Client	Local	Docker	Remote	Read-only
ChatGPT
Claude Desktop
Cursor
VS Code
Windsurf

Frequently asked questions

›What are the environment prerequisites?

This server requires Node.js version 18 or higher.

›How do I switch the server from read-only to write mode?

The server defaults to read-only mode. To enable mutation tools like add_database_record or update_database_record, you must explicitly set the environment variable READ_ONLY=false.

›What MCP transports are supported?

The server supports both Stdio transport for local desktop applications and the Streamable HTTP transport for remote clients and cloud deployments.

›How does the server handle SQL injection threats?

The server prevents SQL injection by binding client values as parameterized queries and performing Zod schema validation on all tool arguments at the protocol boundary.

›How does the server handle validation errors when communicating with AI agents?

The server intercepts raw Zod validation errors and reformats them into human-readable strings, allowing the LLM to identify and correct missing or invalid fields automatically.