engrim logo
engrim
★ 299
vs
3dcitydb-mcp-server logo
3dcitydb-mcp-server
★ 18

engrim vs 3dcitydb-mcp-server

engrim: Engrim is a universal, local-first SQLite memory engine specifically engineered for autonomous AI coding agents, designed to solve the '200,000-token context window trap'. It provides high-precision, curated episodic working memory, allowing developers to switch between various models and environments on the same codebase without losing architectural decisions or project state.; 3dcitydb-mcp-server: The 3DCityDB MCP Server enables AI assistants to access and reason about semantic 3D city models stored in a 3DCityDB v5 geodatabase using natural language. It dynamically resolves CityGML schema, properties, and attributes, allowing AI to execute SQL queries and understand spatial and semantic information without manual prompt engineering.

01

TL;DR

engrim logo
engrimMemory & Context · ★ 299

Maintaining Project Context Across Agent Sessions: Developers can use Engrim to prevent LLMs from losing architectural decisions, user constraints, or project state when chat sessions are cleared or models are switched.

3dcitydb-mcp-server logo
3dcitydb-mcp-serverMemory & Context · ★ 18

Enabling AI assistants to answer natural language queries about 3D city models.

02

Side-by-Side Comparison

Field
engrim logoengrim
3dcitydb-mcp-server logo3dcitydb-mcp-server
Category
Memory & Context
Memory & Context
Stars
★ 299
★ 18
License
MIT
Apache-2.0
Install Command
pip install engrim
pip install 3dcitydb-mcp-server
Updated
3w ago
1d ago
Open Source
Yes
Yes
Tags
Episodic Memory, LLM Context Management, AI Agents
3D City Models, CityGML, PostgreSQL
03

Features

engrim logoengrim
01Precision Working Memory: Replaces raw transcript replay with ~4,000 characters of high-precision, curated episodic memory, injected at boot with zero attention dilution.
02Cross-Model/Agent Compatibility: Provides a universal substrate for memory, allowing decisions made in one agent (e.g., Claude Code) to be visible and usable in others (e.g., Antigravity, Cursor).
03Local-First & Private Storage: Stores all memories locally in a SQLite file (~/.engrim/memory.db) with WAL mode and POSIX 0600 permissions, ensuring 100% privacy with no cloud sync or telemetry.
04Self-Healing Diagnostics: The `engrim doctor --fix` command verifies all hooks and installs portable PATH fallbacks, ensuring reliable operation across machines and OSes without silent failures.
05Hybrid Retrieval & Minder: Employs a hybrid lexical (BM25) and vector (model2vec) search for efficient and relevant memory recall in approximately 30ms.
3dcitydb-mcp-server logo3dcitydb-mcp-server
01Dynamic schema resolution for CityGML object classes and properties.
02Secure read-only SQL query execution against 3DCityDB.
03Integrated Gradio chat UI with multi-LLM support and live reasoning traces.
04One-click import functionality for CityGML, CityJSON, and IFC files (Docker Fullstack).
04

Use Cases

engrim logoengrim
↳Maintaining Project Context Across Agent Sessions: Developers can use Engrim to prevent LLMs from losing architectural decisions, user constraints, or project state when chat sessions are cleared or models are switched.
↳Collaborative Multi-Agent Development: Enabling multiple AI coding agents (e.g., Antigravity, Claude Code, Cursor) to work on the same codebase and share a consistent, evolving memory store.
↳Continue-As-Clear Workflow: Allows users to clear their agent's context window at any time, with Engrim automatically re-injecting the active memory pack for seamless continuation without memory loss.
↳Auditing Agent Provenance: Tracking which agent made specific architectural decisions or added facts to the project's memory, enhancing transparency in multi-agent environments.
3dcitydb-mcp-server logo3dcitydb-mcp-server
↳Enabling AI assistants to answer natural language queries about 3D city models.
↳Developing software to interact with OGC CityGML compliant 3D city models.
↳Performing complex spatial and semantic analyses on 3D city data through an interactive chat interface.
FAQ

FAQ

What is the difference between engrim and 3dcitydb-mcp-server?
Both engrim and 3dcitydb-mcp-server are in the Memory & Context category. engrim has 299 stars, while 3dcitydb-mcp-server has 18 stars.
Which is better, engrim or 3dcitydb-mcp-server?
The best choice depends on your use case. Choose engrim if Maintaining Project Context Across Agent Sessions: Developers can use Engrim to prevent LLMs from losing architectural decisions, user constraints, or project state when chat sessions are cleared or models are switched., and 3dcitydb-mcp-server if Enabling AI assistants to answer natural language queries about 3D city models..
Is engrim free or open source?
Yes, engrim is open source on GitHub (MIT).
Is 3dcitydb-mcp-server free or open source?
Yes, 3dcitydb-mcp-server is open source on GitHub (Apache-2.0).
Cloud Infrastructure
Ad

Deploy on DigitalOcean

Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.

Claim $200 Free Credit
→

Related