by spences10
LibSQL Memory offers a persistent memory database using LibSQL to store and retrieve knowledge graph entities and relati
Provides a persistent LibSQL database for storing knowledge graph entities and relationships that persist across AI conversations. Enables AI assistants to remember and build upon previous interactions.
LibSQL Memory is a community-built MCP server published by spences10 that provides AI assistants with tools and capabilities via the Model Context Protocol. LibSQL Memory offers a persistent memory database using LibSQL to store and retrieve knowledge graph entities and relati It is categorized under ai ml, databases.
You can install LibSQL Memory in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
LibSQL Memory is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Enable Claude to query your database directly using natural language
Example
Ask 'Show me top 10 customers by revenue this month' and get SQL results instantly
Eliminate manual SQL writing for ad-hoc queries, get insights 10x faster
Generate complex reports and analytics without leaving conversation
Example
Analyze sales trends, cohort retention, user behavior patterns conversationally
Democratize data access—non-technical team members can query databases
Understand database structure, relationships, and data models
Example
'Explain the user_orders table schema and its relationships'
Onboard engineers faster, explore unfamiliar databases efficiently
Share your MCP server with the developer community
We wired LibSQL Memory into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
According to our notes, LibSQL Memory benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
LibSQL Memory reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
I recommend LibSQL Memory for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Useful MCP listing: LibSQL Memory is the kind of server we cite when onboarding engineers to host + tool permissions.
LibSQL Memory has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
LibSQL Memory reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Strong directory entry: LibSQL Memory surfaces stars and publisher context so we could sanity-check maintenance before adopting.
We evaluated LibSQL Memory against two servers with overlapping tools; this profile had the clearer scope statement.
I recommend LibSQL Memory for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
showing 1-10 of 37
A high-performance, persistent memory system for the Model Context Protocol (MCP) powered by libSQL with optimized text search for LLM context efficiency.
<a href="https://glama.ai/mcp/servers/22lg4lq768"> <img width="380" height="200" src="https://glama.ai/mcp/servers/22lg4lq768/badge" alt="Glama badge" /> </a>This server is designed to be used as part of an MCP configuration. Here are examples for different environments:
Add this to your Cline MCP settings:
{
"mcpServers": {
"mcp-memory-libsql": {
"command": "npx",
"args": ["-y", "mcp-memory-libsql"],
"env": {
"LIBSQL_URL": "file:/path/to/your/database.db"
}
}
}
}
For a detailed guide on setting up this server with Claude Desktop in WSL, see Getting MCP Server Working with Claude Desktop in WSL.
Add this to your Claude Desktop configuration for WSL environments:
{
"mcpServers": {
"mcp-memory-libsql": {
"command": "wsl.exe",
"args": [
"bash",
"-c",
"source ~/.nvm/nvm.sh && LIBSQL_URL=file:/path/to/database.db /home/username/.nvm/versions/node/v20.12.1/bin/npx mcp-memory-libsql"
]
}
}
}
The server supports both local SQLite and remote libSQL databases through the LIBSQL_URL environment variable:
For local SQLite databases:
{
"env": {
"LIBSQL_URL": "file:/path/to/database.db"
}
}
For remote libSQL databases (e.g., Turso):
{
"env": {
"LIBSQL_URL": "libsql://your-database.turso.io",
"LIBSQL_AUTH_TOKEN": "your-auth-token"
}
}
Note: When using WSL, ensure the database path uses the Linux
filesystem format (e.g., /home/username/...) rather than Windows
format.
By default, if no URL is provided, it will use file:/memory-tool.db
in the current directory.
The server implements the standard MCP memory interface with optimized text search:
The server uses a libSQL database with the following schema:
Due to npm 2FA requirements, publishing needs to be done manually:
pnpm changeset
pnpm changeset version
pnpm release
Contributions are welcome! Please read our contributing guidelines before submitting pull requests.
MIT License - see the LICENSE file for details.
Run data quality queries to catch anomalies and inconsistencies
Example
Find duplicate records, missing values, orphaned foreign keys automatically
Maintain data integrity with less manual SQL work
Prerequisites
Time Estimate
15-30 minutes including configuration and testing
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
MCP server acts as bridge between Claude and database, translating natural language to SQL queries and returning results in structured format.
Protocols
Compatibility
✓ Use when
Use for ad-hoc data queries, exploratory analysis, report generation, schema exploration, and democratizing data access. Best for read-heavy analytics workloads.
✗ Avoid when
Avoid for production write operations, mission-critical transactions, real-time OLTP workloads, or when database contains sensitive PII without proper access controls. Use read replicas, not primary.