AgentIndex icon
AgentIndex
rekal logo
rekal
★ 53
vs
jdocmunch-mcp logo
jdocmunch-mcp
★ 206

rekal vs jdocmunch-mcp

rekal: rekal provides long-term memory for LLMs via an MCP server. It stores memories in a local SQLite file and retrieves them using hybrid search (BM25 keywords + vector semantics + recency decay). It works with any MCP-capable agent like Claude Code, Codex CLI, and OpenCode.; jdocmunch-mcp: jDocMunch-MCP indexes documentation once by heading hierarchy and section structure, then gives MCP-compatible agents precise access to the explanations they actually need. It saves tokens and context window space by retrieving only the relevant section instead of entire files. This improves agent efficiency and reduces costs.

01

TL;DR

rekal logo
rekalRAG / Knowledge Base · ★ 53

Persistent memory for coding agents across sessions to remember user preferences and decisions

Read rekal full review →
jdocmunch-mcp logo
jdocmunch-mcpRAG / Knowledge Base · ★ 206

Agent-driven documentation exploration

Read jdocmunch-mcp full review →
02

Side-by-Side Comparison

Field
rekal logorekal
jdocmunch-mcp logojdocmunch-mcp
Category
RAG / Knowledge Base
RAG / Knowledge Base
Stars
★ 53
★ 206
License
MIT
NOASSERTION
Install Command
pip install rekal
pip install jdocmunch-mcp && jdocmunch-mcp --help
Updated
1mo ago
1d ago
Open Source
Yes
Yes
Website
↗ Visit
↗ Visit
GitHub
↗ GitHub
↗ GitHub
Tags
llm, mcp, mcp-server
claude, claude-code, docs
03

Features

rekal logorekal
01Local SQLite storage, no cloud or API keys
02Hybrid search combining BM25 keywords, vector semantics, and recency decay
03MCP server compatible with various coding agents
04Comprehensive tool-based memory management (store, search, update, delete, prune)
05Smart write operations with supersede and linking for knowledge evolution
jdocmunch-mcp logojdocmunch-mcp
01Section-first retrieval
02Byte-precise extraction
03Stable section IDs
04Local-first architecture
05MCP-native workflow
04

Use Cases

rekal logorekal
↳Persistent memory for coding agents across sessions to remember user preferences and decisions
↳Storing project-specific knowledge and conventions without external services
↳Maintaining a searchable history of agent interactions and decisions
jdocmunch-mcp logojdocmunch-mcp
↳Agent-driven documentation exploration
↳Finding configuration and API reference sections
↳Onboarding to unfamiliar frameworks
FAQ

FAQ

What is the difference between rekal and jdocmunch-mcp?
Both rekal and jdocmunch-mcp are in the RAG / Knowledge Base category. rekal has 53 stars, while jdocmunch-mcp has 206 stars.
Which is better, rekal or jdocmunch-mcp?
The best choice depends on your use case. Choose rekal if Persistent memory for coding agents across sessions to remember user preferences and decisions, and jdocmunch-mcp if Agent-driven documentation exploration.
Is rekal free or open source?
Yes, rekal is open source on GitHub (MIT).
Is jdocmunch-mcp free or open source?
Yes, jdocmunch-mcp is open source on GitHub (NOASSERTION).
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

Alternatives to rekal →Alternatives to jdocmunch-mcp →rekal details →jdocmunch-mcp details →