# alexbakers/mcp-ipfs [Health: Active]

**Category:** ☁️ Cloud Platforms  
**Repository:** https://github.com/alexbakers/mcp-ipfs  
**GitHub Stars:** 21  
**npm Downloads (last month):** 189  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/alexbakers-mcp-ipfs

## Description
upload and manipulation of IPFS storage

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "mcp-ipfs": {
    "command": "npx",
    "args": ["-y","mcp-ipfs"],
    "env": {
      "W3_LOGIN_EMAIL": ""
    }
  }
}
```

**Requires environment variables:** `W3_LOGIN_EMAIL` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What alexbakers/mcp-ipfs MCP server does

The alexbakers/mcp-ipfs MCP server connects MCP-compatible clients to the storacha.network platform through the `@web3-storage/w3cli` command-line interface. Instead of implementing storage operations independently, it translates MCP tool calls into `w3` commands and returns their results to the client.

Its scope covers more than uploading files. Agents can inspect and select Storacha spaces, add or provision spaces, upload and list data, remove data, create public `w3s.link` URLs, and work with delegations and proofs. The server also exposes tools for account authorization, key creation, bridge token generation, plan and usage information, coupons, and several advanced `w3 can ...` storage operations.

## How it works

The server runs as a Node.js process and communicates with an MCP client using the client’s standard server configuration. Each tool has a defined input schema, and the implementation invokes the corresponding `w3` command. The underlying CLI must already be installed and authenticated outside the MCP tool layer.

Install the w3 CLI globally, run `w3 login` with the Storacha account email, and complete the email verification flow before using storage tools. The `w3_login` tool also expects `W3_LOGIN_EMAIL` to contain the same email address. The `w3_space_create` operation is not wrapped for normal automated use because it requires interactive prompts; it must be run manually.

## Setup and configuration

The alexbakers/mcp-ipfs MCP server requires Node.js 22.0.0 or later and a working npm installation. For local use, an MCP client can launch it with `npx -y mcp-ipfs` and pass `W3_LOGIN_EMAIL` in the server environment. A built checkout can be installed with `npm install`, compiled with `npm run build`, and started with `node dist/index.js`.

Docker is also supported. The published image is `alexbakers/mcp-ipfs`, or the image can be built locally. When running in Docker, mount host directories that contain files the agent must upload or read. Tool arguments must use absolute paths visible inside the container, not paths that exist only on the host. The same path rule applies to upload, delegation output, proof, blob, and store operations.

## Tools and capabilities

Available tool groups include:

- Authentication and agent state: `w3_login`, `w3_reset`, and `w3_account_ls`.
- Spaces: `w3_space_ls`, `w3_space_use`, `w3_space_info`, `w3_space_add`, and `w3_space_provision`.
- Data: `w3_up`, `w3_ls`, and `w3_rm`.
- Sharing: `w3_open` for generating a `w3s.link` URL.
- Delegations and proofs: create, list, revoke, add, and inspect operations.
- Keys and tokens: `w3_key_create` and `w3_bridge_generate_tokens`.
- Advanced storage: blob, CAR, upload, index, access claim, and Filecoin information commands.
- Account and billing: plan details, coupon creation, and usage reports.

The exact arguments are defined by the server’s tool schemas. Operations involving local files require paths accessible to the process that runs the server.

## Limitations and notes

This server depends on the external w3 CLI and Storacha account configuration, so it is not a standalone IPFS node or independent storage implementation. Authentication must be completed through the w3 workflow, and the login tool depends on `W3_LOGIN_EMAIL`. Interactive space creation is intentionally outside the automated tool set. Containerized deployments also need explicit volume mounts for host files.

_Full upstream README: https://allmcps.com/mcp/alexbakers-mcp-ipfs/readme_