mcp-local-memory

★ 60

sense

★ 40

mcp-local-memory vs sense

Q: Which is better, mcp-local-memory or sense?

By GitHub stars, mcp-local-memory has more community adoption, but the best choice depends on your specific use case.

mcp-local-memory: mcp-local-memory is a local-first MCP server designed to provide AI agents with shared, durable memory without relying on Docker or cloud services. It achieves this through a powerful combination of hybrid semantic search, SQLite FTS5, and a structured knowledge graph, supporting features like temporal recall and adaptive ranking.; sense: Sense is an MCP server designed to provide AI coding agents with a deep structural understanding of codebases. It indexes repositories locally, offering tools like symbol graph, semantic code search, and convention detection to enhance agent efficiency and accuracy.

TL;DR

mcp-local-memoryMemory & Context · ★ 60

Provide persistent and shared memory for AI agents in local environments.

Read mcp-local-memory full review →

senseMemory & Context · ★ 40

Enable AI agents to efficiently answer structural code questions like 'who calls this function?' by using pre-computed graphs.

Read sense full review →

Side-by-Side Comparison

Field

mcp-local-memory

sense

Features

mcp-local-memory

01Shared memory across multiple AI agents

02Hybrid semantic and keyword recall

03Structured knowledge graph for context management

04Temporal memory recall with natural language dates

05Adaptive memory ranking based on multiple factors

sense

01Provides symbol relationships, callers, callees, inheritance, tests, and dead code detection via `sense_graph`.

02Offers hybrid semantic code search (`sense_search`) with bi-encoder, cross-encoder, keyword, and text fallback.

03Calculates blast radius, affected code, affected tests, and risk score using `sense_blast`.

04Detects project-specific coding conventions from source via `sense_conventions` for style adherence.

Use Cases

mcp-local-memory

↳Provide persistent and shared memory for AI agents in local environments.

↳Build knowledge bases and manage context for complex AI applications.

↳Facilitate local-first AI agent development and testing without external dependencies.

↳Serve as a centralized memory server for distributed AI agent systems via HTTP/SSE.

sense

↳Enable AI agents to efficiently answer structural code questions like 'who calls this function?' by using pre-computed graphs.

↳Reduce AI agent tool calls, token usage, and session time, leading to significant cost and time savings for code-related tasks.

↳Help AI agents write code that adheres to specific project conventions and styles, improving code quality and consistency.

↳Perform advanced code analysis such as identifying dead code or understanding the blast radius of changes.

FAQ

What is the difference between mcp-local-memory and sense?

Both mcp-local-memory and sense are in the Memory & Context category. mcp-local-memory has 60 stars, while sense has 40 stars.

Which is better, mcp-local-memory or sense?

The best choice depends on your use case. Choose mcp-local-memory if Provide persistent and shared memory for AI agents in local environments., and sense if Enable AI agents to efficiently answer structural code questions like 'who calls this function?' by using pre-computed graphs..

Is mcp-local-memory free or open source?

Yes, mcp-local-memory is open source on GitHub (MIT).

Is sense free or open source?

Yes, sense is open source on GitHub (MIT).

Cloud Infrastructure

Deploy on DigitalOcean

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

Claim $200 Free Credit

→

Alternatives to mcp-local-memory →Alternatives to sense →mcp-local-memory details →sense details →

TL;DR

Side-by-Side Comparison

Features

Use Cases

FAQ

Deploy on DigitalOcean

Related