Storacha Network IPFS
STDIONode.js server implementing Model Context Protocol for storacha.network platform interaction.
Node.js server implementing Model Context Protocol for storacha.network platform interaction.
A Node.js server implementing the Model Context Protocol (MCP) for interacting with the storacha.network platform via the w3
command-line interface (@web3-storage/w3cli
).
This server empowers language models 🤖 and other MCP clients to manage storacha.network spaces, upload/download data, manage delegations, and perform various other tasks by seamlessly wrapping w3
commands.
w3
CLI for native integration with storacha.network.w3
functionality:
w3_login
, w3_reset
, w3_account_ls
(for checking authorization)w3_space_ls
, w3_space_use
, w3_space_info
, w3_space_add
, w3_space_provision
(Note: w3_space_create
must be run manually due to interactive prompts)w3_up
, w3_ls
, w3_rm
w3_open
(generates w3s.link URL)w3_delegation_create
, w3_delegation_ls
, w3_delegation_revoke
, w3_proof_add
, w3_proof_ls
w3_key_create
, w3_bridge_generate_tokens
w3 can ...
): Blob, CAR, Upload, Index, Access Claim, Filecoin Info managementw3_plan_get
, w3_coupon_create
, w3_usage_report
node -v
).w3
CLI: The server executes w3
commands directly. Ensure @web3-storage/w3cli
is installed globally and configured:
npm install -g @web3-storage/w3cli w3 login <[email protected]> # Follow email verification steps
w3_login
tool requires the W3_LOGIN_EMAIL
environment variable to be set to the same email used for w3 login
.The codebase is organized as follows:
src/
├── index.ts # Main server entry point, MCP setup, request routing
├── schemas.ts # Zod schemas defining input arguments for each tool
├── tool_handlers.ts # Implementation logic for each MCP tool
├── utils.ts # Helper functions (e.g., running w3 commands, parsing JSON)
└── utils/
└── logger.ts # Basic logger configuration
This server can be used with any MCP-compatible client. You need to configure your client to connect to this server.
This assumes npm
and the prerequisites are met.
{ "mcpServers": { "ipfs": { "command": "npx", "args": ["-y", "mcp-ipfs"], "env": { "W3_LOGIN_EMAIL": "[email protected]" } } } }
Build the image first (see Build section) or use the pre-built image alexbakers/mcp-ipfs
.
{ "mcpServers": { "mcp-ipfs": { "command": "docker", "args": [ "run", "-i", "--rm", "-v", "/path/to/your/project:/path/to/your/project", "-e", "W3_LOGIN_EMAIL", "alexbakers/mcp-ipfs" ], "env": { "W3_LOGIN_EMAIL": "[email protected]" } } } }
Several w3
commands require absolute filesystem paths (e.g., w3_up
, w3_delegation_create --output
, w3_proof_add
, w3_can_blob_add
, w3_can_store_add
).
-v
flag (e.g., -v /Users/me/project:/Users/me/project
) and then use the container path (e.g., /Users/me/project/my_file.txt
) in the tool arguments.Clone the repository and install dependencies:
git clone https://github.com/alexbakers/mcp-ipfs.git cd mcp-ipfs npm install
Build the TypeScript code:
npm run build
You can then run the server directly:
# Ensure W3_LOGIN_EMAIL is set in your environment export W3_LOGIN_EMAIL="[email protected]" node dist/index.js
Or publish it (if you have the rights):
npm publish
Build the Docker image:
# Build locally (replace with your username/repo and desired tag) docker build -t alexbakers/mcp-ipfs .
This MCP server is licensed under the MIT License. See the LICENSE file for details.