Mcp Sqlite3
Give your agent direct SQLite read/write and schema operations through MCP while prototyping apps and local-first tools.
Overview
io.github.daedalus/mcp-sqlite3 is an MCP server for the Build phase that exposes Python sqlite3 database operations to coding agents over stdio.
What is this MCP server?
- Stdio MCP server mcp-sqlite3 v0.1.3 on PyPI exposing sqlite3 library capabilities
- Local database access without standing up Postgres for early prototypes
- MCP 2025-12-11 manifest with github.com/daedalus/mcp-sqlite3 source
- Pairs with agent workflows for migrations, queries, and data fixes in-repo
- Lightweight stdio transport for Claude Code, Cursor, and Codex
- Package version 0.1.3 on PyPI identifier mcp-sqlite3
- Stdio transport per MCP 2025-12-11 server schema
- Repository github.com/daedalus/mcp-sqlite3
Community signal: 1 GitHub stars.
What problem does it solve?
Agents cannot safely inspect or fix your local SQLite data without a structured database bridge.
Who is it for?
Local-first SaaS prototypes, side projects, and agent tools that store state in SQLite during active development.
Skip if: Production multi-tenant Postgres fleets or teams that forbid agent access to database files.
What do I get? / Deliverables
You register one MCP server and let the agent run queries and sqlite3 workflows against designated database files in the build loop.
- MCP-accessible sqlite3 operations for agent-driven development
- Configured stdio server entry (mcp-sqlite3 v0.1.3)
- Faster query and schema iteration on local SQLite stores
Recommended MCP Servers
Journey fit
SQLite MCP fits Build because solo products lean on embedded databases during backend and integration work before ops-scale data platforms. Integrations subphase is the right shelf for wiring the sqlite3 library into agent toolchains alongside APIs and local services.
How it compares
Embedded-database MCP integration, not a hosted DBaaS skill or ORM generator.
Common Questions / FAQ
Who is io.github.daedalus/mcp-sqlite3 for?
Solo builders using SQLite in prototypes who want Claude Code, Cursor, or Codex to run sqlite3-backed operations through MCP.
When should I use io.github.daedalus/mcp-sqlite3?
Use it while building backends and integrations when you need iterative SQL, schema checks, or data repair on local .db files.
How do I add io.github.daedalus/mcp-sqlite3 to my agent?
Install PyPI package mcp-sqlite3 (0.1.3), add a stdio MCP server block using identifier mcp-sqlite3, and restart your MCP-capable client.