H
huggingface/funes
Durable memory for your AI coding agents.
★ 598·updated 2026-11-18
View on GitHub ↗Direct link · no redirect page
We have neither an install command nor a public remote endpoint from this repository, so we do not print a config. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 598 ★ · huggingface/funes · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 598 ★ · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
huggingface/funes;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# funes
Excerpted from the repository README (abridged)
Durable memory for your AI coding agents. funes indexes your past sessions across Claude
Code, Codex, pi, and Hermes and lets any agent recall the past decisions, rationale, and findings.
Your memory is a dataset you can publish to the Hugging Face Hub — then any machine, teammate, or
agent can recall from it.
Put a question to a memory and borrow a coding agent to answer it: funes recalls the relevant sessions, hands them over, and you get one grounded answer that names the sessions it drew from — nothing installed. Here it reads the public huggingface/funes-memory dataset named right in the command.
## Features at a glance
Your agent recalls your past work. The model spontaneously uses funes to recall prior decisions, rationale, and findings mid-task.
One memory across your agents. Index Claude Code, Codex, pi, and Hermes into a single memory;
recall spans all of them, and every hit shows which agent it came from.
Your memory is a Hugging Face dataset. Publish it to the Hugging Face Hub; a teammate,
another of your machines — or anyone, if you make it public — recalls from it with one flag.
And it happens on its own: with funes added, your agent reaches for recall mid-conversation — no command to run. Here it recalls to answer a question about funes's own design, grounded, naming the session it drew from.
## Get funes
The installer detects your platform, downloads the matching prebuilt binary,
verifies its tagged release checksum and version, and puts it on your PATH (~/.local/bin by
default):
bash
curl -fsSL "https://huggingface.co/buckets/huggingface/funes/resolve/install.sh?src=readme" | sh
Then add it to your agent:
bash
funes add claude # or codex, pi, hermes
Another agent? Integrations their authors maintain are listed in
funes-integrations/COMMUNITY.md,
and funes add --from … installs one from wherever it is published.
To build and share your own, start with Writing an integration.
One command onboards you: your agent gets recall and get as tools, and — for Claude, Codex, and
Hermes — funes builds your first index, installs a hook that keeps it current every turn, and (with a
memory bound) publishes at each session boundary. From here you just work. See
docs/add.md for the agents, memory binding, and what a run does; funes status tells
you whether recall is reading your own memory yet.
Tagged binaries and their SHA256SUMS manifest are also available in the
release bucket:
| Platform | Binary |
| Linux x86_64 | funes-x86_64-linux |
| Linux aarch64 | funes-aarch64-linux |
| macOS Apple Silicon | funes-arm64-apple-darwin |
The checksum detects corrupt, truncated, or mismatched release downloads. Because the binary and
checksum share the same bucket, it does not authenticate the bucket itself.
Already installed? funes update replaces the binary in place with the latest build for your
platform (--force reinstalls the current one), then brings your agent integrations to their newest
release; funes status tells you when a newer release is out. To build it yourself, see
Building from source.
funes names itself to the Hub: the User-Agent of its Hugging Face requests carries its version and
an anonymous install id. The id is a random UUID kept in ~/.funes/install-id, created on the
Code, Codex, pi, and Hermes and lets any agent recall the past decisions, rationale, and findings.
Your memory is a dataset you can publish to the Hugging Face Hub — then any machine, teammate, or
agent can recall from it.
Put a question to a memory and borrow a coding agent to answer it: funes recalls the relevant sessions, hands them over, and you get one grounded answer that names the sessions it drew from — nothing installed. Here it reads the public huggingface/funes-memory dataset named right in the command.
## Features at a glance
Your agent recalls your past work. The model spontaneously uses funes to recall prior decisions, rationale, and findings mid-task.
One memory across your agents. Index Claude Code, Codex, pi, and Hermes into a single memory;
recall spans all of them, and every hit shows which agent it came from.
Your memory is a Hugging Face dataset. Publish it to the Hugging Face Hub; a teammate,
another of your machines — or anyone, if you make it public — recalls from it with one flag.
And it happens on its own: with funes added, your agent reaches for recall mid-conversation — no command to run. Here it recalls to answer a question about funes's own design, grounded, naming the session it drew from.
## Get funes
The installer detects your platform, downloads the matching prebuilt binary,
verifies its tagged release checksum and version, and puts it on your PATH (~/.local/bin by
default):
bash
curl -fsSL "https://huggingface.co/buckets/huggingface/funes/resolve/install.sh?src=readme" | sh
Then add it to your agent:
bash
funes add claude # or codex, pi, hermes
Another agent? Integrations their authors maintain are listed in
funes-integrations/COMMUNITY.md,
and funes add --from … installs one from wherever it is published.
To build and share your own, start with Writing an integration.
One command onboards you: your agent gets recall and get as tools, and — for Claude, Codex, and
Hermes — funes builds your first index, installs a hook that keeps it current every turn, and (with a
memory bound) publishes at each session boundary. From here you just work. See
docs/add.md for the agents, memory binding, and what a run does; funes status tells
you whether recall is reading your own memory yet.
Tagged binaries and their SHA256SUMS manifest are also available in the
release bucket:
| Platform | Binary |
| Linux x86_64 | funes-x86_64-linux |
| Linux aarch64 | funes-aarch64-linux |
| macOS Apple Silicon | funes-arm64-apple-darwin |
The checksum detects corrupt, truncated, or mismatched release downloads. Because the binary and
checksum share the same bucket, it does not authenticate the bucket itself.
Already installed? funes update replaces the binary in place with the latest build for your
platform (--force reinstalls the current one), then brings your agent integrations to their newest
release; funes status tells you when a newer release is out. To build it yourself, see
Building from source.
funes names itself to the Hub: the User-Agent of its Hugging Face requests carries its version and
an anonymous install id. The id is a random UUID kept in ~/.funes/install-id, created on the
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/huggingface-funes/)
- Source
- awesome · https://github.com/huggingface/funes
- Browse by field
- MCP servers
- Traction
- 598 ★
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.