A hyper-mcp WebAssembly plugin (v2) for interacting with one or more SQLite databases over the Model Context Protocol. It bundles SQLite (via rusqlite compiled to wasm32-wasip1), so no external SQLite installation is required.

Connections are keyed by an alias and stay open across tool calls until you explicitly close them.

• read — opens read-only; the database file must already exist.
• write — opens read-write, creating the file if it does not exist.

attach applies the same semantics to the attached database via a SQLite URI filename (mode=ro / mode=rwc).

Setting create: true on connect ignores mode and always opens in write mode. It creates any missing parent directories and refuses to overwrite an existing file, so it is the safe way to provision a fresh database.

execute_sql always returns structured content with a result_type discriminator:

• result_type: "query" → columns (array of names) and rows (array of rows, each an array of values aligned with columns). rows_affected is 0.
• result_type: "execute" → rows_affected (integer). columns/rows are empty.

SQLite values map to JSON as follows: NULL → null, INTEGER → number, REAL → number, TEXT → string, and BLOB → { "$base64": "<data>" }.

execute_sql runs a single statement. To run several statements, call the tool once per statement.

Because the plugin runs in a WASM sandbox, it can only reach database files that are explicitly mounted via allowed_paths. Map the host directory containing your databases into the plugin and use the in-sandbox path in connect/attach.

{
  "plugins": {
    "sqlite": {
      "url": "oci://ghcr.io/hyper-mcp-rs/sqlite-plugin:latest",
      "runtime_config": {
        "allowed_paths": ["/host/path/to/data:/data"]
      }
    }
  }
}

With the mapping above, open a database with:

{ "alias": "app", "path": "/data/app.db", "mode": "write" }

For local development, point the plugin at a freshly built .wasm:

{
  "plugins": {
    "sqlite": {
      "url": "file:///path/to/target/wasm32-wasip1/release/plugin.wasm",
      "runtime_config": {
        "allowed_paths": ["/host/path/to/data:/data"]
      }
    }
  }
}

The plugin targets wasm32-wasip1. Because the bundled SQLite is compiled from C, a C toolchain that can target WebAssembly is required — the WASI SDK.

# One-time setup
rustup target add wasm32-wasip1

# Install the WASI SDK and point the C cross-compiler at it
export WASI_SDK_PATH=/opt/wasi-sdk
export CC_wasm32_wasip1="$WASI_SDK_PATH/bin/clang"
export AR_wasm32_wasip1="$WASI_SDK_PATH/bin/llvm-ar"

# Build
cargo build --release --target wasm32-wasip1
# Result: target/wasm32-wasip1/release/plugin.wasm

CI (.github/workflows/ci.yml) and the release workflows install the WASI SDK and set these variables automatically.

Apache-2.0. See LICENSE.