Enterprise DNA
M MCP Servers Developer low

jparkerweb/mcp-sqlite

by Various

๐Ÿ‡ Model Context Protocol (MCP) server that provides comprehensive SQLite database interaction capabilities

J

MCP

jparkerweb/mcp-sqlite

Added 1 June 2026

#aitooling #cursor #database #development #equill-service #mcp #nodejs #sqlite

Overview

An MCP server that enables AI assistants to interact with SQLite databases. It exposes database operations like querying, inserting, and schema exploration through the Model Context Protocol. Built in JavaScript, it can be self-hosted and configured by developers.

Best for

Best for
Developers building AI assistants that need local or embedded database access

Use cases

  • Querying databases via natural language through an AI assistant
  • Automating database tasks with LLM-driven agents
  • Integrating SQLite data into AI workflows for context and retrieval

Notes

An MCP server that enables AI assistants to interact with SQLite databases. It exposes database operations like querying, inserting, and schema exploration through the Model Context Protocol. Built in JavaScript, it can be self-hosted and configured by developers.

107 stars on GitHub. Last updated 2026-04-05. Licensed MIT.

Use cases

  • Querying databases via natural language through an AI assistant
  • Automating database tasks with LLM-driven agents
  • Integrating SQLite data into AI workflows for context and retrieval

Pros

  • Simple to set up with standard MCP clients
  • Handles common SQLite operations including schema introspection
  • Active open-source project with responsive maintainer

Cons

  • Requires MCP-compatible client or host
  • No built-in authentication for database access
  • Limited to SQLite; not for production multi-user databases

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.

Pros

  • Simple to set up with standard MCP clients
  • Handles common SQLite operations including schema introspection
  • Active open-source project with responsive maintainer

Cons

  • Requires MCP-compatible client or host
  • No built-in authentication for database access
  • Limited to SQLite; not for production multi-user databases