MCP Memory Server vs SQLite MCP Server

MCP Memory Server

MCP Servers

SQLite MCP Server

MCP Servers

Tagline

MCP Memory Server

Persistent knowledge-graph memory for Claude and other MCP clients

SQLite MCP Server

Reference MCP server for querying and analyzing SQLite databases through Claude and other MCP clients.

Pricing

MCP Memory Server

Free· Free and open source (MIT). Self-hosted; no vendor charges. Runs locally via npx or Docker.

SQLite MCP Server

Free· Free / open source (MIT). No usage fees; runs locally against a SQLite file you control.

API

MCP Memory Server

Yes

SQLite MCP Server

Not listed

Open source

MCP Memory Server

Yes · NOASSERTION

SQLite MCP Server

Yes · MIT

GitHub stars

MCP Memory Server

91,651

checked 2026-10-29

SQLite MCP Server

305

checked 2026-10-29

Last GitHub push

MCP Memory Server

2026-10-29

SQLite MCP Server

2025-05-28

First commit

MCP Memory Server

2024-11

SQLite MCP Server

2025-05

Package downloads (30 d)

MCP Memory Server

175,042 · pypi mcp-server-git

checked 2026-10-15

SQLite MCP Server

—

Best for

MCP Memory Server

Developers and power users who already run Claude Desktop, Claude Code or another MCP client and want a free, local, hand-inspectable persistent memory layer they can wire up in five minutes.

SQLite MCP Server

Developers and analysts who want an LLM to explore a local SQLite database through Claude Desktop or VS Code, and MCP server authors looking for a small, readable reference implementation to fork.

Not for

MCP Memory Server

Teams that need multi-user memory, semantic search over thousands of facts, SSO or an audited managed service - reach for a hosted memory product or a real graph/vector database instead.

SQLite MCP Server

Teams that need a maintained, hardened database connector, non-SQLite engines, multi-user access controls, or any production system where an archived upstream is a non-starter.

Editorial score

MCP Memory Server

—

SQLite MCP Server

—

Use cases

MCP Memory Server

Persistent Claude Desktop memory across chatsLong-lived coding-agent project memoryLightweight personal CRM of people and companiesResearch-agent scratch knowledge graphCross-session preference and style memoryTeam convention and past-bug recall for coding assistantsStructured note-taking backend for MCP clientsLocal-first alternative to hosted memory APIs

SQLite MCP Server

Ad-hoc SQL exploration of a local SQLite database from Claude DesktopPrototyping agentic business-intelligence workflowsTeaching an LLM to write SQL against an introspected schemaBuilding a running insights memo across a multi-turn analysis sessionReference implementation for authoring a custom MCP serverWiring a local SQLite cache into a larger MCP-based agent stackQuick schema documentation via `list_tables` and `describe_table`Lightweight data prep and table creation inside a chat session

Pros

MCP Memory Server

• Official, Anthropic-maintained reference implementation - the canonical way to add persistent memory to an MCP client
• Zero-config install via npx or a one-line Docker command; works out of the box with Claude Desktop's claude_desktop_config.json
• Simple, inspectable JSONL storage on disk that you can grep, diff, back up and edit by hand
• Structured entity/relation/observation model is more queryable than a raw text scratchpad and cheaper than a vector DB
• Nine well-scoped tools plus a live-updating knowledge-graph Resource, so agents can both read and mutate memory
• Fully open source (MIT) and vendor-neutral - runs against any MCP-speaking model, not just Claude
• Trivial to fork or wrap for team-specific schemas since the codebase is a single small TypeScript file

SQLite MCP Server

• Zero-config local database access for any MCP client — point it at a .db file and Claude can query, schema-introspect and write immediately.
• Clean, minimal tool surface (six tools) that maps cleanly to how an LLM actually reasons about a database.
• Novel `append_insight` + `memo://insights` pattern gives the model a persistent scratchpad for multi-turn analysis.
• MIT-licensed and open source, so it doubles as a canonical example for building your own MCP server.
• Multiple install paths — uv, Docker, VS Code one-click — cover most developer setups.
• No API keys, no cloud, no per-query cost; everything runs on your machine against a file you own.

Cons

MCP Memory Server

• Reference-quality, not production-grade: single-file JSONL storage with no concurrency control, indexing or replication
• search_nodes is a plain substring match with no embeddings or semantic ranking - large graphs degrade quickly
• No built-in multi-user, auth or per-project isolation; a shared install mixes memories from every session
• The model still has to be prompted to actually call the memory tools - forgetful assistants forget to remember
• No web UI, visualisation or admin surface; you inspect and clean the graph by editing the JSONL yourself
• Only a local filesystem backend - no Postgres, SQLite or cloud sync option is shipped

SQLite MCP Server

• Repository was archived on 29 May 2025 — no more upstream fixes, security patches or new features.
• Exposes `write_query` and `create_table` to the model, so a careless prompt can mutate or drop data; there is no built-in read-only mode or row-level safety.
• SQLite-only — no Postgres, MySQL, DuckDB or cloud-warehouse support; you need a different MCP server for those.
• No authentication, quota or audit layer; intended for local single-user use, not shared/multi-tenant deployments.
• Insight-memo state lives in the running server process, so it does not survive restarts or multiple concurrent clients cleanly.

Website

MCP Memory Server

github.com

SQLite MCP Server

github.com

Editorial score: rule-based, 0–10, from AI-assisted profile inputs (see /methodology) — not a user rating; “—” means unscored. “Not listed” means we have no record of it, not that it is absent. GitHub figures and prices carry the date they were checked or captured; prices are shown as published, unconverted.