local_fire_departmentHoneystax
search⌘K
loginLog Inperson_addSign Up
layers
HONEYSTAX TERMINAL v1.0
HomeNewsSavedSubmitMethodology
Back to the live board
R

rekal

MCP Server

Long-term memory for LLMs. MCP server backed by hybrid search in a single SQLite file.

Copy the install, test the workflow, then decide if it earns a permanent slot.

50
Why nowLower urgency

The signal is softer here. Treat it like a pattern source unless it solves a very specific gap.

DecisionKeep on the radar

Copy the install, test the workflow, then decide if it earns a permanent slot.

Trial costFast eval

You can test this quickly and remove it cleanly if it misses.

Risk43/100

GitHub health unknown. no security policy. 0 open issues make this testable, but not something to trust blind.

What You Are Adopting

AI Agent

Universal

Model

Multiple

Test This In Your Stack

One command inClean rollbackLow commitment
settingsRegistryAdds a named entry to Claude config. One command to remove.

Fastest way to find out if rekal belongs in your setup.

Copy the install command, run a real test, and back it out cleanly if it slows you down.

Try now
claude mcp add rekal -- npx rekal

Run this first. You will know quickly if the workflow earns a permanent slot.

Back out
claude mcp remove rekal

No messy cleanup loop. If it misses, remove it and keep moving.

Install Location

~/  └─ .claude.json    └─ mcp_servers/      └─ rekal ← registers here

About

Long-term memory for LLMs. MCP server backed by hybrid search in a single SQLite file.

Source & freshness

Source: GitHub repository

Source check: No source check recorded

Repository state: Not marked archived

Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.

Open Live ProjectAudit Repo

Reviews0

Log in to write a review.

Submitted June 23, 2026

auto_awesomeYour strongest next moves after rekal