A
securityA
licenseA
qualityA high-performance MCP server utilizing libSQL for persistent memory and vector search capabilities, enabling efficient entity management and semantic knowledge storage.
Last updated -
6
77
51
TypeScript
MIT License
SQLite is a C-language library that implements a small, fast, self-contained, high-reliability, full-featured, SQL database engine.
Why this server?
Uses SQLite as a local database option for persistent storage of entities, relations and vector embeddings
Why this server?
Enables vector similarity searches using SQLite vector extensions, allowing for querying vector data stored in Turso databases with customizable parameters.
Why this server?
Provides database interaction capabilities through SQLite, enabling users to run SQL queries, analyze business data, and generate business insight memos
Why this server?
Leverages SQLite database to store and query airtime transaction data, enabling features like transaction history retrieval and aggregation.
Why this server?
Version 1.5.4 was the last version of ATLAS that used SQLite as the database before switching to Neo4j in version 2.0.
Why this server?
Connects to SQLite databases to run SQL queries and perform data analysis
Why this server?
Provides SQLite as an alternative to Turso for local development, storing memory system data locally.
Why this server?
Supports connections to SQLite databases, enabling schema queries, table exploration, and SQL execution.
Why this server?
Stores travel logs to enable continuing journeys even after closing the application
Why this server?
Uses SQLite for local storage of memory data
Why this server?
Provides persistent storage for projects and tasks using a local SQLite database, with support for complex querying and relationship management.
Why this server?
Uses SQLite for local chat history storage
Why this server?
Enables working with SQLite databases to analyze and visualize data in presentations, as mentioned in the usage example for reviewing sales data
Why this server?
Provides tools for interacting with SQLite databases, including executing SQL queries, creating tables, viewing schema information, and analyzing data to generate business insights.
Why this server?
Allows retrieval of data from SQLite databases for inclusion in PowerPoint presentations, specifically mentioned for creating presentations based on database content
Why this server?
Allows importing data from CSV and Excel files into SQLite databases
Why this server?
Supports local SQLite databases for persistent storage of entities, relations, and vector embeddings
Why this server?
Uses SQLite as the database backend for storing all task data in tables for todos, tags, and todo_tags relationships
Why this server?
Uses SQLite as the persistent storage backend for Infrastructure-as-Code components, allowing configuration through the DATABASE_URL environment variable.
Why this server?
Stores conversation variations in a SQLite database with robust query capabilities, allowing users to read logs, execute SQL queries, create tables, and analyze stored interaction patterns.
Why this server?
Provides persistent storage for voice generation history, allowing retrieval and management of past text-to-speech jobs.
Why this server?
Stores and provides access to grid coordinates data for Korean administrative regions, enabling location-based weather queries.
Why this server?
Manages SSH credentials storage through a SQLite database, enabling persistence of connection details for remote command execution.
Why this server?
Provides direct access to SQLite database files, allowing for executing queries, schema modifications, and data operations against local SQLite databases.
Why this server?
Implements an ephemeral SQLite database in memory for storing and analyzing financial data, with tools for setting up, querying, and managing database tables
Why this server?
Self-hosted Convex works well with SQLite as a database option
Why this server?
Leverages SQLite with sqlite-vec for efficient vector similarity search and FTS5 for full-text search capabilities when indexing documentation.
Why this server?
Offers SQLite database integration with support for password protection, providing SQL query capabilities, table structure information, and constraint analysis.
Why this server?
Enables connection to SQLite databases to browse available tables, view schema information, and run protected read-only SQL queries.
Why this server?
Targeted for integration in Q3 2025 to support lightweight database understanding, enabling AI to work with SQLite databases with full context awareness.
Why this server?
Provides SQLite database integration with auto-discovery, data browsing, and manipulation features.
Why this server?
Uses SQLite database to maintain conversation history for coherent responses across multiple queries
Why this server?
Accesses the Bear Notes SQLite database to extract note content and metadata through SQL commands.
Why this server?
Supports SQLite databases, generating REST and MCP interfaces with automatic API documentation and security features.
Why this server?
Stores transaction data in a SQLite database file for tracking financial transactions and calculating profit/loss metrics.
Why this server?
Enables connection to SQLite databases for executing queries and exploring database structure
Why this server?
Supports integration with SQLite database for persistence in examples like the CRUD Todo List
Why this server?
The MCP server supports SQLite as a storage backend for content and graph data in the knowledge base
Why this server?
Provides tools for connecting to SQLite databases, executing queries, and managing database schema with options for automatic database creation.
Why this server?
Stores exploit data in a SQLite database that can be configured and updated on customizable intervals.
Why this server?
Enables execution of SQL queries against an SQLite database, with support for SELECT operations to retrieve and analyze data stored in the database.
Why this server?
References SQLite database integration for persistence of data, as demonstrated in the CRUD example with full database operations
Why this server?
The project was inspired by and based on code from the SQLite MCP Server, suggesting some level of SQLite compatibility or similar functionality
Why this server?
Provides ability to query and analyze SQLite databases through DuckDB's interface, extending analytical capabilities to SQLite data sources.
Why this server?
Supports connecting to SQLite databases (including downloadable sample databases), with tools for querying and manipulating data
Why this server?
Uses SQLite as the database backend for storing source information and relationships
Why this server?
Uses SQLite for persistent storage of chat history data, allowing conversations with Perplexity AI to be continued across sessions.
Why this server?
Uses SQLite database to store and manage medical content, topic mappings, and user documents.
Why this server?
Stores context items in an SQLite database, allowing persistence of memory across sessions
Why this server?
Connects to the Bear SQLite database in read-only mode to safely retrieve note data without modifying the underlying database.
Why this server?
Supports SQL output format with SQLite dialect for random user data, including CREATE TABLE statements and proper type handling.
Why this server?
Provides an example integration for querying SQLite databases, exposing database schema information and executing SQL queries
Why this server?
Uses SQLite as the backend database for storing the knowledge graph data, providing persistent storage of entities, relations, and observations
Why this server?
Uses SQLite for storing system state and token usage data, with querying capabilities for resource monitoring
Why this server?
Stores and manages data for the MCP system, including action history tracking
Why this server?
Provides persistent storage for the MCP server to maintain user data and conversation state.
Why this server?
Provides safe, read-only access to SQLite databases through tools like read_query, list_tables, and describe_table
Why this server?
Powers the law office database that handles client data, case management, billable time tracking, and invoice generation with specialized legal tools for proper documentation and billing validation
Why this server?
Stores and queries fetched EHR data in a SQLite database, allowing read-only SQL operations against structured FHIR resources.
Why this server?
Supports SQLite-based storage for the vector database with the chroma.sqlite3 format, providing persistent document indexing
Why this server?
Used as the default database backend for storing the TPC data with simple file-based storage requiring no separate database server.
Why this server?
Provides database functionality for storing and retrieving data about cars, enabling querying of the vehicle information stored in an SQLite database through the MCP protocol.
Why this server?
Stores and caches fetched RSS feeds in a local database for persistence and efficient retrieval
Why this server?
Uses SQLite databases for storing API definitions and Fast Memory capabilities, allowing efficient API endpoint lookups and storage of frequently used queries.
Why this server?
Provides access to Cursor IDE's SQLite databases, allowing for querying and analyzing data stored in state.vscdb files
Why this server?
Uses SQLite database for persistent storage of tasks, enabling the MCP server to maintain task data beyond AI context limitations
Why this server?
Provides SQLite database operations including executing SQL queries, managing tables, and tracking business insights through standardized MCP tools
Why this server?
Provides database integration for storing and querying CAD elements through an internal SQLite database.
Why this server?
Implements a Model Context Protocol server for SQLite databases, allowing AI assistants to query and interact with SQLite databases
Why this server?
Connects to Bear Notes' SQLite database to access and search notes content for retrieval and context enhancement.
Why this server?
The README includes an example 'SQLite Explorer' that demonstrates database integration with SQLite, allowing users to query SQLite databases and retrieve schema information.
Why this server?
Allows to connect to an SQLite database and query log data through the Model Context Protocol (MCP) server
Why this server?
Provides primary email storage, full-text search capabilities, processing status tracking, and efficient filtering with proper connection management
Why this server?
Facilitates natural language communication with SQLite databases, allowing conversational data exploration and manipulation.