E2B vs Rust Filesystem
E2B is an MCP server published by e2b-dev. Marketplaces we read that list it: 1 (Docker MCP Catalog). Rust Filesystem is an MCP server published by rust-mcp-stack. Marketplaces we read that list it: 1 (Docker MCP Catalog). As of our marketplace pass on 2026-10-13. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  E2B |  Rust Filesystem |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ff4f9608cc4c Forks (GitHub): 72 Pulls (Docker Hub): 23 208 Stars (Docker Hub): 2 Stars (GitHub): 393 Not marked · First seen |
Listed Version: sha256:0a8d6879a676 Forks (GitHub): 28 Pulls (Docker Hub): 42 549 Stars (Docker Hub): 2 Stars (GitHub): 180 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | E2B | Rust Filesystem |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 393 (better) | 180 (worse) |
| Pulls (Docker Hub) (differs) | 23 208 (worse) | 42 549 (better) |
| Forks (GitHub) (differs) | 72 (better) | 28 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/e2b) | On your machine (mcp/rust-mcp-filesystem) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 1 | 24 |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 2, secrets among them: 0 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/e2b-dev/mcp-server | github.com/rust-mcp-stack/rust-mcp-filesystem |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
E2B
Giving Claude ability to run code with E2B via MCP (Model Context Protocol).
Rust Filesystem
The Rust MCP Filesystem is a high-performance, asynchronous, and lightweight Model Context Protocol (MCP) server built in Rust for secure and efficient filesystem operations. Designed with security in mind, it operates in read-only mode by default and restricts clients from updating allowed directories via MCP Roots unless explicitly enabled, ensuring robust protection against unauthorized access. Leveraging asynchronous I/O, it delivers blazingly fast performance with a minimal resource footprint. Optimized for token efficiency, the Rust MCP Filesystem enables large language models (LLMs) to precisely target searches and edits within specific sections of large files and restrict operations by file size range, making it ideal for efficient file exploration, automation, and system integration.
How to run each
E2B As a local MCP server: Docker image
claude mcp add --env "E2B_API_KEY=<YOUR_E2B_API_KEY>" --transport stdio e2b -- docker run -i --rm -e E2B_API_KEY mcp/e2bRequires: E2B_API_KEY (secret)
Rust Filesystem As a local MCP server: Docker image
claude mcp add --transport stdio rust-mcp-filesystem -- docker run -i --rm mcp/rust-mcp-filesystemCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Only E2B declares
run_code
Only Rust Filesystem declares
calculate_directory_sizecreate_directorydirectory_treeedit_filefind_duplicate_filesfind_empty_directoriesget_file_infohead_filelist_allowed_directorieslist_directorylist_directory_with_sizesmove_file
Show the remaining 12
read_file_linesread_media_fileread_multiple_media_filesread_multiple_text_filesread_text_filesearch_filessearch_files_contenttail_fileunzip_filewrite_filezip_directoryzip_files
Both declare
None
Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.
Settings each asks for
Only E2B asks for
E2B_API_KEY (secret)
Only Rust Filesystem asks for
ALLOW_WRITEENABLE_ROOTS
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: E2B · What it can do: Rust Filesystem · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.