Filesystem MCP vs Memory MCP
Side-by-side comparison built from DeepYard's structured catalog. Content updated Aug 21, 2026.
Direct Answer
Filesystem MCP suits teams needing open-source access, file read focus, and 89,768 GitHub stars in current listing data. Memory MCP suits teams needing open-source access, persistent memory focus, and 89,768 GitHub stars in current listing data. This summary reflects catalog metadata only for decision support, not independent testing.
What this comparison weighs
- Pricing and free-tier availability
- License model and deployment fit
- GitHub adoption and contributor depth
- Catalog tags, integrations, and supported workflows
| Metric | Filesystem MCP | Memory MCP |
|---|---|---|
| GitHub Stars | 89.8K | 89.8K |
| Contributors | 426 | 426 |
| Last Commit | Aug 20, 2026 | Aug 20, 2026 |
| Open Issues | 533 | 533 |
| License | open-source | open-source |
| Pricing | open-source | open-source |
| Free Tier | Yes | Yes |
| Category | mcp-servers | mcp-servers |
| Trending | No | No |
Choose Filesystem MCP if you need
- • Filesystem MCP is the stronger pick when File Read matters because that capability is listed only on its profile.
- • Filesystem MCP is the cleaner fit if you specifically need Filesystem workflows from the catalog tags.
Choose Memory MCP if you need
- • Memory MCP is the stronger pick when Persistent Memory matters because that capability is listed only on its profile.
- • Memory MCP is the cleaner fit if you specifically need Memory workflows from the catalog tags.
Meaningful differences
Shared capabilities
- • Anthropic
- • Reference Server
Shared Tags
Only in Filesystem MCP
Only in Memory MCP
Limitations and evidence
- • DeepYard compares structured public metadata; this is not an independent benchmark unless a test record is shown.
- • Signals such as stars, contributors, and last commit indicate public activity, not purchase fit or runtime quality.
- • Pricing and feature coverage reflect the stored listing snapshot and may lag vendor changes between refreshes.
Source links
About Filesystem MCP
The official Anthropic filesystem MCP server provides sandboxed access to your local file system with configurable allowed directories. It exposes tools to read file contents, list directories, write and create files, move files, search by pattern, and get file metadata — giving AI assistants controlled, auditable access to your codebase without arbitrary shell execution. Ships as part of Anthropic's reference MCP servers collection.
View full listingAbout Memory MCP
The official Anthropic memory MCP server gives AI assistants persistent, cross-session memory using a local knowledge graph stored as a JSON file. Claude can create entities (people, projects, concepts), record relations between them, and add observations over time — then recall that information in future sessions. Ideal for long-running projects where continuity matters: the assistant remembers your architecture decisions, team conventions, and in-progress work without you having to repeat context.
View full listing