MemoFS MCP Server
dev.memofs/mcp-server
About MemoFS MCP Server
MemoFS MCP Server is an MCP server published by memofs.dev. Persistent memory and virtual filesystem MCP server for AI agents.
It runs on your own machine: your AI client starts it from the npm package @memofs/mcp-server at version 1.3.0-beta.3, or you can connect to the hosted version instead.
It asks for one secret: MEMOFS_API_KEY. Give it a key with the least access that still works.
Version 1.3.0-beta.3 was published on 17 August 2026, and the source code is public, so you can read it before installing.
Written from the registry entry. 10 automated checks on the registry entry and the package code: 8 pass, 0 warn, 0 fail, 2 info. How we check.
What it asks for
| Variable | Required | Secret | Description |
|---|---|---|---|
MEMOFS_API_KEY | No | Yes | API key for MemoFS Cloud synchronization (required for hybrid mode) |
MEMOFS_RUNTIME | No | No | Runtime mode: local or hybrid |
Checks
| Check | Result | Detail |
|---|---|---|
| Source repository linked | Pass | https://github.com/memo-fs/memofs |
| Version pinned | Pass | Every package has an explicit version |
| Remote uses HTTPS | Pass | All remote endpoints use https:// |
| Secrets requested | Info | Asks for 1 secret: MEMOFS_API_KEY |
| Known package registry | Pass | All packages come from npm, PyPI, OCI, NuGet or MCPB |
| Namespace ownership | Info | Name verified via domain memofs.dev |
| Registry text aimed at the AI | Pass | Description and settings contain no hidden characters or instructions to the AI |
| Install scripts | Pass | @memofs/mcp-server@1.3.0-beta.3 runs nothing at install |
| Code red flags | Pass | Read 19 files in @memofs/mcp-server@1.3.0-beta.3: no obfuscation, encoded execution, credential reads or data-collection endpoints found |
| Text aimed at the AI | Pass | No hidden characters or instructions to the AI in 19 files, including comments and the README |
Popularity & health: 63 / 100
Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.
2 forks, 25 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.
What people say
No Hacker News threads link to its source code.
Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.
Facts
| Registry name | dev.memofs/mcp-server |
|---|---|
| Publisher | Domain memofs.dev |
| How the name is verified | Name verified via domain memofs.dev. The registry ties the name prefix to that account or domain; it does not check the code. |
| Type | Local package and a hosted remote |
| Packages | npm @memofs/mcp-server 1.3.0-beta.3 (stdio) |
| Remote endpoints | streamable-http https://memofs.dev/api/v1/projects/{projectId}/mcp |
| Version | 1.3.0-beta.3 |
| Published | |
| Last updated | |
| Source repository | https://github.com/memo-fs/memofs |
| Website | https://memofs.dev |
| Category | Files & documents (assigned by keyword rule, not by hand) |
Related servers in Files & documents
- Octofs6/7Standalone MCP filesystem tools server — view, edit, shell, workdir.
Agent Workspace MCP4/4A sandboxed, agentic workspace providing secure filesystem, bash,…
- Patchloom5/7Agent-safe structured edits: JSON/YAML/TOML/md/AST, dry-run,…
- Filesystem MCP6/7Filesystem MCP server for AI assistants.
- FileSystem MCP Server7/7Secure filesystem access for AI agents with configurable directory…
- local-workspace-mcp6/7Bounded, read-oriented filesystem, git and named-task tools over…