Potencialize seu agente
Instalação do publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
Ainda não há uma versão empacotada no registro. Siga o README do repositório.
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDo publicador
# Install (macOS, Linux, Windows)
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?"
That's it. No API keys, no Python, no cloud required. First run downloads the embedding model (~200MB, one-time) and you're running.
Long-term memory for AI agents (MCP). One Rust binary, offline, 98.2% recall@5 on LongMemEval-S. Works with Claude Code, Cursor, Codex. Self-host free or use Uteke Cloud.
Want your agent (Claude Code, Cursor, Hermes) to use it? 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 everything up. 📖 Onboarding docs
LongMemEval-S (ICLR 2025) hides the facts an agent needs across ~115 chat sessions per question and checks whether retrieval finds the evidence. 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.
Per-release stability (full 500 questions, scored from committed raw — RESULTS.md):
¹ agentmemory's published numbers, same benchmark, same 500-question split (their recall_any@5 basis; verified apples-to-apples in our head-to-head). ² Strict = every gold session in top-5; 65% of questions have multiple gold sessions. Mathematical ceiling 99.4%. ³ MRR, not recall_all (not directly comparable; shown for completeness). By question category (recall_any@5: the category-level story most tools don't show):
The hard part isn't finding a needle; every question's evidence lands in the top-50 (zero misses). The residual gap is ordering when a question needs several sessions at once: strict recall_all@5 is 88.0% against a 99.4% ceiling.
🎯 Don't trust our benchmark. Run it yourself. The full harness is in this repo: public dataset, committed raw outputs for all three releases (v0.16/v0.17/v0.19), deterministic scoring you can recompute in ~20 lines of Python. No embedder needed to verify, ~$10 to re-run the whole 500 questions yourself. 👉 benchmarks/longmemeval/REPRODUCING.md
Also built in: uteke bench --counts 100,1000,10000 for latency/throughput on
your own machine. 📖 Full benchmark docs · RESULTS.md
🤖 Building AI agents? Give them persistent memory without cloud dependencies. Your agent remembers user preferences, past decisions, and context across sessions, fully offline.
👥 Working in a team? Use Rooms to share knowledge. Meeting notes, project decisions, architecture choices: searchable by everyone, attributed by author.
🔒 Building for privacy-sensitive domains? Healthcare, finance, legal: data stays on your machine. No API calls, no telemetry, no cloud. Local embeddings (ONNX, 768d).
⌨️ Power user who lives in the terminal? Uteke is your personal knowledge graph. Remember anything, recall by meaning, link related thoughts. All from the command line.
You just spent 2 hours explaining your codebase to ChatGPT. Next session? Blank slate. Again.
Every AI tool forgets. Context windows fill up, sessions end, and your AI starts over every single time. Uteke gives it persistent memory and keeps it on your machine.
Note: Tool labels (A–G) represent common categories of AI memory layers available as of August 2026. Capabilities are assessed from public documentation and may change. This table is a starting point for your own evaluation, not a definitive ranking.
Uteke vs Tool A (Python local-first): Both offer local-first with semantic + FTS5 search. Uteke's edge: single binary (no Python runtime), native time-travel (vs temporal triples), rooms, and zero runtime dependencies.
Uteke vs Tool G (Go single binary): Both are single-binary, offline, no-API-key, and both ship MCP servers. Tool G is FTS5-only (keyword search). Uteke adds vector semantic search + RRF fusion + rooms + time-travel + graph relationships + smart decay + document engine + batch import. Same simplicity thesis, more capabilities.
Uteke vs Tool F (TypeScript local mode): Tool F now offers a local binary mode with Ollama support, a solid step toward offline-first. But it's still TypeScript/Node.js under the hood. Uteke is Rust: smaller footprint, faster startup, zero runtime. And Uteke has hybrid search with FTS5 (Tool F's local mode uses vector-only, no keyword fallback).
Uteke vs Tools B/D/E: Those are powerful, but all require cloud LLM API keys and Docker infrastructure. Your data goes to external LLM providers. Uteke runs fully offline with local ONNX embeddings. No Docker, no Python, no API keys.
Uteke vs Tool C: Tool C has 54 MCP tools and multi-agent shared memory via a local engine. Uteke's edge: zero dependencies (no npm, no extra engine), hybrid search (Tool C lacks FTS5), and time-travel queries.
graph LR
Input[User Query] --> Embed[Local ONNX Embedder<br/>768d, EmbeddingGemma Q4]
Embed --> HNSW[HNSW Vector Index<br/>usearch]
Embed --> FTS5[FTS5 Full-Text<br/>SQLite]
HNSW --> RRF[Reciprocal Rank Fusion<br/>k=60]
FTS5 --> RRF
RRF --> Results[Ranked Results]
style Input fill:#4a9eff,color:#fff
style Results fill:#4aff9e,color:#000
style RRF fill:#ff9e4a,color:#fff
How hybrid search works:
Everything runs in-process. No network. No cloud. No server required (unless you want server mode).
Local-first (default): single binary, zero infrastructure.
curl -sSL codecora.dev/uteke/install | sh
uteke remember "first memory"
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 ghcr.io/codecoradev/uteke:latest
# or: uteke serve --host 0.0.0.0 --port 8767
# Create a shared room
uteke room create "engineering" --description "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 recall "caching decision" --room engineering
Author attribution on every memory; cross-agent recall without manual sync. 📖 Full Rooms documentation →
// .mcp.json (Claude Code, Cursor)
{ "mcpServers": { "uteke": { "command": "uteke-mcp" } } }
For Claude Desktop, Hermes, and HTTP transport, see MCP docs.
Many memory layers (Python-based or TypeScript-based) require cloud API keys (OpenAI/LLM) and external infrastructure (Docker, Postgres, Qdrant). Your data gets sent to a cloud LLM provider. Uteke is a single binary with zero API keys. All embeddings run locally via ONNX. Your data never leaves your machine. See comparison table.
Some platforms offer dozens of MCP tools and multi-agent shared memory via a local engine. They're packed with integrations, but require npm, a separate runtime, and LLM API keys for embeddings. Uteke is Rust, zero dependencies, and works fully offline with local ONNX embeddings. If you want maximum integrations → those platforms. If you want privacy, speed, zero setup, and hybrid search → Uteke.
Some single-binary tools share our philosophy: one binary, zero deps, MCP server, local-first. The key difference is search: most are FTS5-only (keyword matching). Uteke uses hybrid search (HNSW vector similarity + FTS5 + Reciprocal Rank Fusion), meaning you can search by meaning, beyond exact words. Uteke also adds rooms, time-travel, graph relationships, smart decay, document engine, and batch import.
Yes. The embedding model (EmbeddingGemma Q4, 768d) downloads once (~200MB) on first run. After that, zero network calls. No telemetry. If the local model fails, Uteke degrades gracefully to a no-op embedder. It never crashes and never calls a cloud API.
~45ms as a CLI (measurements: 31ms avg @10K on the published bench host, 100–10K memories, flat with store size). No network round-trip because everything is local. The LRU recall cache eliminates redundant embedding computation for repeated queries.
Yes. Uteke ships with an MCP server that works with Claude Code, Cursor, and Hermes. You can also use the HTTP API directly in any language. See MCP setup →
Uteke is at v0.21.1 with 200+ tests, CI/CD on every commit, and a benchmark harness. It's used in production by the CodeCora team and other early adopters. Still in 0.x, so expect rough edges, but the core is stable.
The open-source engine stays full-capability. Nothing about the benchmark results above is paywalled. Cloud adds hosted convenience on top.
cargo build --workspace # Build
cargo test --workspace # Test (200+ tests)
cargo clippy -- -D warnings # Lint
cargo fmt # Format
Contributions welcome! Read CONTRIBUTING.md for the full guide.
Apache License 2.0. Use it, fork it, ship it.
Long-term memory for AI agents (MCP). One Rust binary, offline, 98.2% recall@5 on LongMemEval-S. Works with Claude Code, Cursor, Codex. Self-host free or use Uteke Cloud.
Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
Uteke roda localmente via stdio.
Última verificação: 2026-11-15. Long-term memory for AI agents (MCP). One Rust binary, offline, 98.2% recall@5 on LongMemEval-S. Works with Claude Code, Cursor, Codex. Self-host free or use Uteke Cloud.