πͺ MCP IPFS Server (storacha.network) π°οΈ
@alexbakers
πͺ MCP IPFS Server
Overview
What is πͺ MCP IPFS Server (storacha.network) π°οΈ?
A Node.js server implementing the Model Context Protocol (MCP) for interacting with the storacha.network platform via the w3 command-line interface. It empowers language models and other MCP clients to manage storacha.network spaces, upload/download data, manage delegations, and perform various tasks by wrapping w3 commands.
How to use πͺ MCP IPFS Server (storacha.network) π°οΈ?
Install the @web3-storage/w3cli globally and run w3 login first. Set the W3_LOGIN_EMAIL environment variable to the email used during login. Configure your MCP client to connect using npx (npx -y mcp-ipfs) or Docker (alexbakers/mcp-ipfs) with the required environment variable.
Key features of πͺ MCP IPFS Server (storacha.network) π°οΈ
- Wraps the
w3CLI for native storacha.network integration - Provides MCP tools for authentication, space, and data management
- Supports delegation creation, listing, and revocation
- Offers advanced storage operations via
w3 cancommands - Includes account billing, plan, and usage reporting tools
Use cases of πͺ MCP IPFS Server (storacha.network) π°οΈ
- Upload and download files to/from storacha.network from an AI assistant
- Manage storage spaces and user delegations programmatically
- Generate sharing links (w3s.link) for uploaded content
- Handle keys, tokens, and proofs for decentralized storage workflows
FAQ from πͺ MCP IPFS Server (storacha.network) π°οΈ
What runtime does it require?
Node.js version 22.0.0 or higher, along with the global installation of @web3-storage/w3cli.
How do I provide filesystem paths when using Docker?
Several w3 commands require absolute paths. In Docker, mount the host directory with -v and use the container path in tool arguments.
What authentication is needed?
Users must run w3 login manually first and set the W3_LOGIN_EMAIL environment variable to the same email for the w3_login tool.
Which transports or protocols does it use?
The README does not specify transport details beyond being an MCP server that can connect to any MCP-compatible client.
What limitations exist?
The w3_space_create command must be run manually due to interactive prompts; w3_up and related file commands require absolute filesystem paths.