Summary
I built a new Zed MCP extension called MCP S3 Browser and would like to add it to the Zed extensions registry.
Repository: https://github.com/Bnjoroge1/mcp-s3-browser
What it provides
MCP S3 Browser adds S3-aware browsing and inspection workflows to Zed for:
- AWS S3
- Garage
- SeaweedFS
- other S3-compatible object stores
It is designed to work with both local and remote Zed projects through project-scoped configuration in .zed/settings.json.
Current tool support includes:
- listing configured connections
- listing buckets
- listing objects with pagination
- searching object keys
- inspecting object metadata
- previewing text objects
Why this is useful
Zed does not currently ship an S3 browser, and object storage is a common part of remote development environments and self-hosted infra workflows.
One motivating use case is browsing a Garage deployment running in Docker on a remote VM opened through Zed Remote Development.
Validation
The extension repository currently includes:
- CI for
npm run check and cargo check --target wasm32-wasip2
- a checked-in bundled runtime file needed by the extension at runtime
- a dev-installable Zed extension manifest
If this looks good, I can open the corresponding PR to add the extension submodule and registry entry.
Summary
I built a new Zed MCP extension called MCP S3 Browser and would like to add it to the Zed extensions registry.
Repository: https://github.com/Bnjoroge1/mcp-s3-browser
What it provides
MCP S3 Browser adds S3-aware browsing and inspection workflows to Zed for:
It is designed to work with both local and remote Zed projects through project-scoped configuration in
.zed/settings.json.Current tool support includes:
Why this is useful
Zed does not currently ship an S3 browser, and object storage is a common part of remote development environments and self-hosted infra workflows.
One motivating use case is browsing a Garage deployment running in Docker on a remote VM opened through Zed Remote Development.
Validation
The extension repository currently includes:
npm run checkandcargo check --target wasm32-wasip2If this looks good, I can open the corresponding PR to add the extension submodule and registry entry.