하이브리드 벡터 및 전체 텍스트 검색과 룸(rooms) 및 타임 트래블 기능을 지원하여 AI agent에게 장기 기억을 제공합니다.
다른 이름 codecoradev/uteke
- 스타
- 288
- Tools
- —
- 다운로드, 30일
- —
- 최신 버전
- 0.24.0
- 마지막 커밋
- 2026년 11월 14일
- 라이선스
- Apache-2.0
Uteke MCP란?
Uteke은(는) MCP server입니다. 하이브리드 벡터 및 전체 텍스트 검색과 룸(rooms) 및 타임 트래블 기능을 지원하여 AI agent에게 장기 기억을 제공합니다.
프로젝트 README에서 생성된 요약
Uteke MCP server 정보
Uteke는 벡터 검색과 SQLite 전체 텍스트 검색을 결합하여 AI agent에게 장기 기억을 제공합니다. 룸 기능을 통해 Claude Code, Cursor, Hermes와 같은 다양한 클라이언트가 단일 메모리 저장소를 공유할 수 있습니다. 이 시스템은 단일 Rust 바이너리로 로컬에서 작동하며, API key나 별도의 벡터 데이터베이스 없이 오프라인으로 실행됩니다. 임베딩 모델은 첫 실행 시 한 번 다운로드되어 의미 기반 검색을 가능하게 합니다.
개발자는 엔진을 자신의 기기에 직접 호스팅하거나 Uteke Cloud를 통해 호스팅된 환경을 사용할 수 있습니다. 로컬에서 실행할 때 서버는 uteke-mcp 명령을 사용하여 stdio를 통해 MCP 클라이언트에 연결합니다. --at 플래그를 사용한 특정 시점의 회상(point-in-time recall), 관계 그래프, 그리고 개인정보 보호를 위한 API key와 같은 비밀 정보의 자동 마스킹 기능을 갖추고 있습니다. 이 시스템은 고성능을 위해 설계되었으며 CPU만으로도 빠른 검색 성능을 구현합니다.
활용 사례
- 1여러 agent 간 메모리 공유개발자는 룸을 사용하여 서로 다른 AI 도구들이 동일한 과거 컨텍스트에 접근하도록 할 수 있습니다.
- 2의미 또는 키워드로 정보 검색의미론적 이해와 정확한 텍스트 매칭을 모두 사용하여 agent에게 특정 세부 정보를 찾도록 요청할 수 있습니다.
- 3특정 시점의 과거 데이터 접근agent가 과거의 특정 시점에 알고 있었던 내용을 다시 살펴볼 수 있습니다.
- 4로컬 실행을 통한 개인정보 보호사용자는 데이터가 클라우드에 전송되지 않도록 자신의 하드웨어에서 전체 메모리 시스템을 실행할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
Uteke MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 Uteke MCP 설치
$ claude mcp add --transport http uteke https://uteke.app/mcpCursor에 Uteke MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"uteke": {
"url": "https://uteke.app/mcp"
}
}
}VS Code에 Uteke MCP 설치
.vscode/mcp.json
{
"servers": {
"uteke": {
"type": "http",
"url": "https://uteke.app/mcp"
}
}
}VS Code CLI에 Uteke MCP 설치
$ code --add-mcp '{"name":"uteke","type":"http","url":"https://uteke.app/mcp"}'Codex에 Uteke MCP 설치
$ codex mcp add uteke --url https://uteke.app/mcpCodex config.toml에 Uteke MCP 설치
~/.codex/config.toml
[mcp_servers.uteke] url = "https://uteke.app/mcp"
Gemini CLI에 Uteke MCP 설치
$ gemini mcp add -s user --transport http uteke https://uteke.app/mcpGemini settings.json에 Uteke MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"uteke": {
"url": "https://uteke.app/mcp",
"type": "http"
}
}
}자동 검사
2026년 11월 12일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 이는 보안 감사가 아닙니다. 코드를 직접 읽고 서버에 필요한 최소한의 권한만 부여하십시오. 검사 방식
- 소스 저장소 연결 및 접근 가능통과
- 오픈 소스 라이선스 (OSI)통과
- 최근 1년 내 커밋 또는 릴리스통과
- 패키지 이름이 인기 패키지와 유사하지 않음검사되지 않음
- 원격 엔드포인트가 HTTPS 사용통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 모델에 대한 숨겨진 지침 없음통과
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
README
GitHub에서 보기Why Uteke
On Monday you tell your agent how you deploy. By Thursday it has no idea. Every session starts from zero, and every agent keeps its own half-memory.
Uteke gives all of them one long-term memory that runs on your own machine:
- Verifiable recall. 98.2% recall@5 on LongMemEval-S, with the stricter numbers shown next to it and the raw outputs in this repo.
- Fast and cheap to query. ~45 ms warm recall, 0 LLM tokens per query, CPU only.
- One binary. No Python, no Docker, no vector database, no API key. The embedding model (~200 MB) downloads once.
- One memory, every agent. Claude Code, Claude Desktop, Cursor, Codex, Hermes and any MCP client share the same store. Rooms record which agent or person wrote what.
- Finds by meaning and by keyword. Local vectors and SQLite full-text search, fused into one ranking (how it works).
- Remembers over time. Point-in-time recall (
--at), a relationship graph, a document engine, and decay for stale memories. - Private by default. No telemetry. Secrets such as API keys are masked before a memory is stored.
- Open source. Apache-2.0, cosign-signed releases.
Quick start
# Install (macOS Apple Silicon, Linux; Windows: see below)
curl -sSL codecora.dev/uteke/install | sh
# Store a memory
uteke remember "Deploy v2.1 to staging at 3pm"
# Search it back: by meaning AND by keyword
uteke recall "when do we deploy?"
# Look at what is stored, in a read-only browser page
uteke view
No API keys, no Python, no cloud account. The first run downloads the embedding model (~200 MB, one time).
Give your agent (Claude Code, Cursor, Hermes) the same memory with one line:
// .mcp.json
{ "mcpServers": { "uteke": { "command": "uteke-mcp" } } }
New to Uteke, or you are an AI agent? Run uteke onboard. It detects your setup, asks which agent you use, and wires it up. 📖 Onboarding
Rather not run anything locally? Uteke Cloud runs the same engine for you: add one URL to Claude, sign in, done. Free during the open beta.
| Method | Command |
|---|---|
| Homebrew | brew install codecoradev/tap/uteke (macOS Apple Silicon & Linux) |
| Cargo | cargo install uteke-cli |
| Docker | docker run -d -p 127.0.0.1:8767:8767 -v uteke-data:/data codecoradev/uteke:latest --host 0.0.0.0 |
| Binary | GitHub Releases (macOS, Linux, Windows) |
| Windows (PowerShell) | powershell -ExecutionPolicy Bypass -Command "irm https://raw.githubusercontent.com/codecoradev/uteke/main/install.ps1 | iex" |
📖 Full install guide · Docker docs
Self-host or Cloud
Same engine, two ways to run it.
| Self-host (this repo) | Uteke Cloud | |
|---|---|---|
| Engine and recall | Full, nothing paywalled | Same engine |
| Runs on | Your laptop or your server | Hosted for you |
| Connect an agent | uteke-mcp in .mcp.json |
Add https://uteke.app/mcp to Claude, sign in |
| Your data | Never leaves your machine | Stored by us; export any time |
| Price | Free, Apache-2.0 | Free during the open beta (limits) |
Choose self-host if your data must stay on your machine, or you want to run Uteke inside your own infrastructure. Choose Cloud if you want one memory across several devices and agents without running a server.
Benchmarks
LongMemEval-S (ICLR 2025) hides the facts an agent needs across ~115 chat sessions per question and checks whether retrieval finds them. 500 hand-curated questions, five memory abilities. Uteke runs the full suite with zero LLM calls in the retrieval path: local embeddings, one CPU, deterministic.
| Metric | Uteke v0.20.0 | MemPalace¹ | agentmemory¹ |
|---|---|---|---|
| recall_any@5 (evidence in top 5) | 98.2% | 96.6% | 95.2% |
| recall_any@10 | 98.8% | — | 98.6% |
| strict recall_all@5 (all evidence in top 5) | 88.0%² | not published | not published³ |
| LLM calls in retrieval | 0 | — | 0 |
¹ Their published numbers on the same benchmark and 500-question split, on their own recall_any@5 basis (head-to-head notes); evaluation setups differ. ² Strict = every gold session in the top 5; 65% of questions have more than one. Max possible 99.4%. ³ agentmemory publishes MRR 88.2%, which is a different metric.
Stable across releases (full 500 questions, scored from committed raw, RESULTS.md):
| Release | v0.16.0 | v0.17.0 | v0.19.0 | v0.20.0 | fix 32a5cf3b |
|---|---|---|---|---|---|
| recall_any@5 | 98.2% | 98.4% | 98.2% | 98.2% | 98.2% |
| strict recall_all@5 | 88.0% | 88.0% | 88.0% | 88.0% | 88.0% |
Re-validated 2026-11-08 after the #1690 import fix: strict@5 identical (88.0%), strict@10 +1 question (95.4%), zero misses@50 — four questions shifted partial gold ordering, none lost all evidence.
By question type (recall_any@5, v0.20.0):
| knowledge-update | single-session | temporal | multi-session |
|---|---|---|---|
| 100% | 96.7–98.2% | 98.4% | 98.3% |
Every question's evidence lands in the top 50 (zero misses). What's left is ordering when a question needs several sessions at once: strict recall_all@5 is 88.0% against a 99.4% ceiling, and most misses lose exactly one session.
🎯 Don't trust our benchmark. Run it yourself. Public dataset, committed raw outputs for every validated release, scoring you can recompute in ~20 lines of Python. Verifying the committed results takes a minute and needs no embedder; re-running all 500 questions costs about $10. 👉 benchmarks/longmemeval/REPRODUCING.md · 🧾 Receipts for the headline number (v0.19.0 run)
LoCoMo. LoCoMo end-to-end QA measures answer accuracy, and the result depends on the LLM answerer and the LLM judge used. In an internal comparison, identical answers were scored up to 8 points apart when only the judge model was swapped. For that reason we do not publish a single LoCoMo number in this README. The full table, the per-judge figures and the receipts are in benchmarks/locomo/RESULTS.md. Retrieval recall, which needs no judge, remains the metric we rely on.
uteke bench --counts 100,1000,10000 measures latency and throughput on your own machine. 📖 Benchmark docs
Connect your agent
| Client | How |
|---|---|
| Claude Code | .mcp.json: { "mcpServers": { "uteke": { "command": "uteke-mcp" } } } · details |
| Claude Desktop | config snippet |
| Cursor | same .mcp.json as Claude Code · details |
| Codex | uteke connect codex installs recall and capture hooks · details |
| Hermes | stdio or HTTP · details |
| Any MCP client | stdio (uteke-mcp) or Streamable HTTP (uteke-serve) · transports |
| Claude on the web, desktop or mobile | add https://uteke.app/mcp as a connector, sign in (Uteke Cloud) |
| No MCP? | any agent that can run a shell command can call the uteke CLI |
# Create a shared room
uteke room create engineering --title "Team decisions"
# Alice's agent stores a decision
uteke remember "We chose Redis for caching over Memcached" \
--room engineering --author alice
# Bob's agent adds context
uteke remember "Redis cluster: 3 nodes, 2 replicas each" \
--room engineering --author bob
# Any agent can recall the shared history
uteke room recall engineering "caching decision"
Author attribution on every memory; cross-agent recall without manual sync. 📖 Rooms
Features
| Memory | Search | Integrations | Privacy & operations |
|---|---|---|---|
| Rooms with author attribution | Fusion of vector + full-text (default) | MCP over stdio and Streamable HTTP | Fully offline, no telemetry |
Point-in-time recall (--at) |
Relationship graph and auto-links | Server mode and Docker image | Secrets masked before storage |
| Tags, entities, typed memories | Salience and recency boosts | Document engine (uteke doc) |
Signed upgrades (cosign) |
| Partial updates and citations | Dream cycle: dedup, backlinks, orphans | Batch import, full export/import | Two vector engines (usearch, vecq) |
Core memory
| Feature | What it does |
|---|---|
| 🧠 Hybrid + Fusion Search | Vector similarity + FTS5 full-text search, merged by Reciprocal Rank Fusion (RRF). Since v0.16.0, fusion (a weighted RRF of the vector and hybrid rankings) is the default recall strategy. Finds by meaning AND exact keywords. |
| 🏠 Rooms | Multi-agent shared memory. Group memories by context (meetings, projects, clients). Multiple agents read/write to the same room with author attribution. Cross-agent recall without manual sync. |
| ⏳ Time-travel | Recall memories as they existed at any point in time. uteke recall "deploy" --at 2025-01-15T00:00:00Z |
| 🏷️ Rich Metadata | Tags, entities, categories, key:value pairs on every memory. |
| 🧩 Memory Types | Typed categories (fact, procedure, decision, etc.) with auto-inference. |
| ✏️ Partial Updates | uteke update <id> changes content, tags, importance, pin or type in place. |
| 📎 Citations | Source attribution on every memory (URL, file, user, import batch). |
| 👤 Author | Who wrote a memory, with or without a room (--author), plus human vs agent type. |
| 🚫 Rejected Values | uteke forget <id> --reason wrong records a tombstone: every write path (remember, update, import, supersede) refuses that value again, matched after normalization, until uteke tombstone remove. |
Search & intelligence
| Feature | What it does |
|---|---|
| 🔗 Relationship Graph | Link memories with typed edges (supersedes, contradicts, references). Auto-backlinks. |
| 🔗 Cross-Entity Linking | Bidirectional memory↔document references via [[doc-slug]] wikilinks. |
| 🤖 Cosine Auto-Linking | Automatically creates similar_to edges between related memories. |
| 📉 Smart Decay | Composite importance scoring. Pin what matters, let stale memories fade. |
| 📈 Salience + Recency | Dual-axis recall boost by memory type and age. |
| 🔍 Orphan Detection | Find disconnected, low-importance memories for cleanup. |
| 🌙 Dream Cycle | One-command maintenance: lint → backlinks → dedup → orphans. |
| 🧬 Consolidation | Merge near-duplicate room memories into fewer, denser records: segment-level planner, provenance trust policy, per-pair control. |
Integrations
| Feature | What it does |
|---|---|
| 🔌 MCP Server | JSON-RPC over stdio + Streamable HTTP. Works with Claude Code, Cursor, Hermes. |
| 🖥️ Server Mode | Persistent daemon: eliminates cold-start embedding load on every call. |
| 📂 Batch Import | Import entire directories with auto-strategy routing (document vs. memory extraction). --defer-embed stores a JSONL file first and embeds later in portions (repair --reembed --limit). |
| 🪝 Agent Hooks | uteke connect claude|codex|cursor installs recall and capture hooks in the agent app (pi/hermes: the memory-provider plugin); uteke disconnect removes exactly them. See Claude Code, Codex, Cursor. |
| 🎙️ Raw Capture | Queue conversation turns with no LLM call (uteke capture, POST /capture, MCP uteke_capture); extract-queue run or the server's schedule turns them into memories later, on a budget. Opt-in. |
| 📝 Document Engine | Wiki/knowledge base with uteke doc create/get/list and auto-chunking. |
| 📥 Import/Export | JSONL backup and restore; export --full / import --full move the whole store: documents, rooms, the graph and each memory's author and provenance (vectors are rebuilt on the target). |
| 🔑 View-Only API Keys | Read-only tokens for safe GET-only access to the server. |
Performance & privacy
| Feature | What it does |
|---|---|
| 📦 Single Binary | Zero dependencies. No Python, no API keys. Local-first by default. |
| 🐳 Docker Ready | Official multi-arch image on Docker Hub. Run as a shared service for teams or cloud deployments. |
| 🔒 Fully Offline | Local ONNX embeddings (EmbeddingGemma Q4, 768d). No telemetry, no cloud. The only network call is a daily release check, off with UTEKE_NO_UPDATE_CHECK=1. |
| 🧱 Fenced MCP Output | MCP read tools wrap stored text in <uteke-stored-data> so an agent treats recalled memories as data, not instructions (UTEKE_MCP_FENCE=0 turns it off). |
| 🛡️ Privacy Filter | Secrets (API keys, tokens, .env values) are masked before a memory is embedded or stored; [privacy] mode = "strict" refuses the write instead. |
| ✍️ Signed Upgrades | uteke upgrade verifies the release's cosign (Sigstore keyless) signature before installing. |
| ⚡ Recall Cache | LRU cache eliminates redundant embedding for repeated queries. |
| 🔥 Tiered Memory | Hot/Warm/Cold tracking with auto-cleanup of stale memories. |
| 🧮 Two Vector Engines | usearch (HNSW, default) or vecq (4-bit quantized, pure Rust, ~3x smaller index), chosen at runtime. |
| 🔄 Embed Fallback | Gracefully degrades to no-op embedder if local model fails (never crashes). |
| 📊 Benchmarks | Built-in uteke bench for perf testing. See results. |
How it works
graph LR
Input[Query] --> Embed[Local embedder<br/>EmbeddingGemma Q4, 768d]
Input --> FTS5[Full-text search<br/>SQLite FTS5]
Embed --> Vec[Vector index<br/>usearch or vecq]
Vec --> Hybrid[Hybrid<br/>vector + FTS5, RRF k=60]
FTS5 --> Hybrid
Vec --> Fusion[Fusion<br/>vector x1.7 + hybrid x1]
Hybrid --> Fusion
Fusion --> Boost[Salience + recency]
Boost --> Results[Ranked results]
style Input fill:#131A15,color:#F3F8F4
style Fusion fill:#1F908C,color:#fff
style Results fill:#0B6667,color:#fff
- Vector index finds by meaning ("deploy" matches "rollout").
- FTS5 finds by exact terms ("deploy" matches "deploy").
- Hybrid merges the two lists with Reciprocal Rank Fusion (k=60).
- Fusion merges the vector ranking (weight 1.7) with the hybrid ranking (weight 1), then adds small salience and recency boosts.
Everything runs in-process: no network, no server required. --strategy vector | fts5 | hybrid | graph picks a single stage instead.
Local-first (default): single binary, zero infrastructure. Your data stays in ~/.codecora/uteke/.
Docker / server mode: for teams or remote agents.
docker run -d -p 127.0.0.1:8767:8767 -v uteke-data:/data codecoradev/uteke:latest --host 0.0.0.0
# or, without Docker: uteke-serve --port 8767
📖 Docker setup · Server mode · Remote access
Compared with other memory tools
| Uteke | Tool A | Tool B | Tool C | Tool D | Tool E | Tool F | Tool G | |
|---|---|---|---|---|---|---|---|---|
| Language | Rust (single binary) | Python (pip) | Python | TypeScript | TypeScript | Python | TypeScript | Go (single binary) |
| Setup | One binary (curl | sh) |
pip install + venv | pip + Docker + Qdrant | npm + iii-engine | npm (Node.js) | pip + Docker + Neo4j | Cloud or local binary | One binary |
| API keys | ❌ None | ⚠️ For remote embeddings | ✅ OpenAI/LLM | ✅ LLM key | ✅ LLM key | ✅ LLM key | ⚠️ Cloud only | ❌ None |
| Works offline | ✅ Fully | ⚠️ Optional | ❌ Cloud embedding | ❌ Needs LLM | ❌ Needs LLM | ❌ Needs LLM + vector DB | ✅ Local binary + Ollama | ✅ Fully |
| Search | Fusion (vector + hybrid) | sqlite-vec + FTS5 | Vector + Graph | Vector + Graph | Vector | Hybrid (semantic + keyword + graph) | Vector + rerank | FTS5 only |
| Recall speed | ~45ms | ~50ms+ | Network round-trip | Network round-trip | Network round-trip | Network round-trip | Network round-trip | ~Fast (local) |
| Multi-agent | ✅ Rooms | ✅ Multi-agent surface | ❌ | ✅ Shared server | ✅ Multi-agent groups | ❌ | ❌ | ⚠️ Shared via MCP |
| Time-travel | ✅ Native point-in-time | ⚠️ Temporal triples | ❌ | ❌ | ❌ | ✅ Temporal graphs | ❌ | ❌ |
| MCP server | ✅ stdio + HTTP | ✅ stdio + SSE | ❌ | ✅ 54 MCP tools | ❌ | ✅ Graphiti MCP | ✅ Open-source MCP | ✅ stdio MCP |
| Your data | ✅ Never leaves machine | ✅ Local-first | ⚠️ Sent to LLM cloud | ✅ Local (iii-engine) | ⚠️ Sent to LLM cloud | ⚠️ Sent to LLM cloud | ⚠️ Cloudflare-hosted | ✅ Local |
| License | Apache 2.0 | MIT | Apache 2.0 | Apache 2.0 | Apache 2.0 | Apache 2.0 | MIT | MIT |
Tool labels (A–G) stand for common categories of AI memory layers as of August 2026, assessed from public documentation. Use this as a starting point for your own evaluation, not a ranking.
Documentation
| Getting started | Installation · Getting started · Onboarding |
| Reference | CLI reference · Configuration · Docker · HTTP API |
| Concepts | Viewer · Rooms · Organizing memories · Architecture |
| Integrations | MCP setup (Claude Code, Claude Desktop, Cursor, Hermes) · Hermes · Claude Code / Codex / Cursor hooks |
| Security | SECURITY.md (vulnerability reports, release signing) |
| Benchmarks | docs/benchmarks.md · RESULTS.md · Reproduce it yourself |
Uteke MCP 질문
Uteke MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add --transport http uteke https://uteke.app/mcp를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
Uteke MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
Uteke를 사용하려면 API key가 필요한가요?
아니요, Uteke는 오프라인으로 작동하며 API key가 필요하지 않습니다.
로컬 버전을 사용할 때 데이터가 비공개로 유지되나요?
네, 로컬 버전은 기본적으로 비공개이며 텔레메트리를 수집하지 않고 저장 전 API key와 같은 비밀 정보를 마스킹합니다.