Spike: evaluate SQLite Explorer demo as a future advanced MCP example

[itprodirect]

Objective

Research and design, but do not fully build yet, a safe read-only SQLite Explorer MCP demo that could become an advanced example after the core insurance-sales demo is stable.

Context

The research report suggested a SQLite Explorer pattern for business users who want to query local structured data through MCP. That is a strong future demo, but it should be treated as an advanced spike so the repo does not become too complex too early.

Scope

• Review the current repo structure and dependency constraints.
• Decide whether a SQLite Explorer belongs in this repo, a sibling repo, or a later branch.
• Propose a minimal schema using synthetic/sample insurance or claims-operation data only.
• Propose safe read-only query boundaries.
• Create a short design note, not a full implementation.

Suggested output:

docs/design/sqlite-explorer-spike.md

Acceptance criteria

• Design note explains the learning value of a SQLite Explorer MCP server.
• Design note defines a small synthetic schema.
• Design note defines read-only constraints and row limits.
• Design note lists risks: SQL injection, data exposure, overbroad local access, hallucinated queries.
• Design note recommends whether to build now, later, or in a separate repo.
• No production client data is introduced.
• No full SQLite server implementation is included in this spike unless explicitly approved in a later issue.

Non-goals

• Do not build the SQLite server in this issue.
• Do not add new dependencies unless needed for documentation validation.
• Do not connect to real claims data.
• Do not create write-capable database tools.

Validation

ruff check .
mypy --strict .
pytest -q

Suggested Codex /goal summary

Create a design note for a future read-only SQLite MCP demo, with strict safety and scope boundaries.