Memory LibSQLSAFE
🧠 High-performance persistent memory system for Model Context Protocol (MCP) powered by libSQL. Features vector search, semantic knowledge storage, and efficient relationship management - perfect for AI agents and knowledge graph applications.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
A high-performance, persistent memory system for the Model Context Protocol (MCP) powered by libSQL with optimized text search for LLM context efficiency.
Features
- 🚀 High-performance text search with relevance ranking
- 💾 Persistent storage of entities and relations
- 🔍 Flexible text search with fuzzy matching
- 🎯 Context-optimized for LLM efficiency
- 🔄 Knowledge graph management
- 🌐 Compatible with local and remote libSQL databases
- 🔒 Secure token-based authentication for remote databases
Configuration
This server is designed to be used as part of an MCP configuration. Here are examples for different environments:
Cline Configuration
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"
}
}
}
}Claude Desktop with WSL Configuration
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"
]
}
}
}Database Configuration
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_URLae470e183b7cOBSERVED · 2026-10-07Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add mcp-memory-libsql --env LIBSQL_AUTH_TOKEN=${LIBSQL_AUTH_TOKEN} -- npx -y [email protected]{
"mcpServers": {
"mcp-memory-libsql": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"LIBSQL_AUTH_TOKEN": "${LIBSQL_AUTH_TOKEN}"
}
}
}
}Exposed tools (6)
2 read · 2 write · 2 destructive. Blast radius: 2 tools can delete or overwrite — an agent that can be talked into calling a tool can be talked into calling this one.
| Tool | Risk | Description |
|---|---|---|
create_entities | write | Create new entities with observations |
create_relations | write | Create relations between entities |
delete_entity | destructive | Delete an entity and all its associated data (observations and relations). This is a destructive operation that cannot be undone. |
delete_relation | destructive | Delete a specific relation between entities. This is a destructive operation that cannot be undone. |
read_graph | read | Get recent entities and their relations |
search_nodes | read | Search for entities and their relations using text search with relevance ranking |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | WARN |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (1 observation(s))
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (3)
delete_entity, delete_relation
.prettierignore
@libsql/client, @tmcp/adapter-valibot, @tmcp/transport-stdio, dotenv, tmcp, valibot, @changesets/cli, @types/node
Gates applied: no_behavioural_pass.
ae470e183b7cfull audit observations/trust-audit/mcp-server/spences10__memory-libsql-1.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-07 | ae470e183b7c | SAFE | B | 89 | first audit |
Questions
What is the Memory LibSQL MCP server?
🧠 High-performance persistent memory system for Model Context Protocol (MCP) powered by libSQL. Features vector search, semantic knowledge storage, and efficient relationship management - perfect for AI agents and knowledge graph applications.
What tools does Memory LibSQL expose?
6 in total: 2 read-only, 2 that write, and 2 that can delete or overwrite (delete_entity, delete_relation). Every one is listed on this page with its risk.
Is Memory LibSQL safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B. Separately from the audit: 2 of its tools can destroy data, so scope the token you give it to what you actually need.
What credentials does Memory LibSQL need?
It reads LIBSQL_AUTH_TOKEN from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How current is this page?
The grade is for one exact copy of the source (ae470e183b7c), read on 2026-10-07. The repository is watched and re-audited when it changes.