# Filebase (Web3 Storage) MCP MCP > Filebase (Web3 Storage) provides full control over decentralized storage via IPFS and IPNS. Use this MCP to manage persistent content identifiers, provision network gateways, track usage metrics, and handle keypair generation—all through natural language commands from your AI agent. ## Overview - **Category:** developer-tools - **Price:** Free - **Tags:** ipfs, web3, decentralized-storage, pinning-service, ipns ## Description Connecting Filebase means you're taking the keys to your decentralized infrastructure. Instead of switching between a command line interface or a web dashboard to deal with CIDs, pins, and names, you manage it all directly via conversation. Your agent can generate keypairs for you, publish assets to IPNS, and resolve those names back into usable IPFS paths. Need to track bandwidth? You just ask your AI client to check the bucket usage or list active gateways. This lets you treat complex Web3 infrastructure management like a simple conversational workflow. Since Vinkius hosts this MCP in its catalog, you get access to all these advanced tools—from raw block retrieval using RPC to managing entire gateway lifecycles—all from one place. ## Tools ### platform_create_gateway Creates a new dedicated network gateway endpoint. ### platform_create_name Registers and creates a brand new IPNS name record. ### platform_delete_gateway Removes an existing dedicated network gateway from the platform. ### platform_delete_name Deletes a previously registered IPNS name record. ### platform_get_bucket_usage Retrieves the specific storage usage details for one designated bucket. ### platform_get_gateway Fetches detailed information about a particular dedicated gateway. ### platform_get_gateway_usage Checks the current bandwidth usage statistics for a specific gateway. ### platform_get_name Gets all details related to a specified IPNS name. ### platform_get_usage Retrieves the total storage and overall bandwidth usage across the entire system. ### platform_list_gateways Returns a list of all active, dedicated network gateways configured. ### platform_list_names Lists all currently registered IPNS names in the system. ### platform_update_gateway Modifies settings for an already existing dedicated gateway. ### platform_update_name Changes an IPNS name to point to a new content identifier (CID). ### psa_add_pin Adds a specific CID to the pinning service for guaranteed, long-term availability. ### psa_get_pin Checks the status of a pin using its unique request ID. ### psa_list_pins Lists all currently active pinning requests via the Pinning Service API. ### psa_remove_pin Removes a pin from the service using its request ID. ### psa_replace_pin Replaces an existing pinned object with new content while keeping the same identifier. ### rpc_add Uploads and stores a plain text file directly onto the IPFS network. ### rpc_block_get Retrieves raw data blocks from IPFS using their specific CID. ### rpc_cat Fetches the readable contents of a file given its CID. ### rpc_key_gen Creates and stores a brand new cryptographic keypair in your local keychain. ### rpc_key_list Shows all the keypairs currently stored in your managed keychain. ### rpc_name_publish Registers a given CID to an IPNS name for public resolution. ### rpc_name_resolve Resolves a known IPNS name back into its corresponding, usable IPFS path/CID. ### rpc_pin_add Adds an object's CID to persistent storage using the raw RPC method. ### rpc_pin_ls Lists all objects currently pinned via the raw RPC interface. ### rpc_pin_rm Unpins a content identifier (CID) using the raw RPC method. ### rpc_version Gets the running version number of the IPFS daemon for compatibility checks. ## Prompt Examples **Prompt:** ``` Upload the text 'Hello from Filebase MCP' to IPFS. ``` **Response:** ``` I've uploaded your text to IPFS. The generated CID is `QmXoyp...`. You can now access this content or pin it for long-term storage. ``` **Prompt:** ``` Show me a list of all my pinned objects. ``` **Response:** ``` Fetching your pinned objects... I found 12 active pins. The most recent ones include `Qm...` (Status: pinned) and `bafy...` (Status: pinning). ``` **Prompt:** ``` What is my current storage usage on Filebase? ``` **Response:** ``` Your current usage is 4.2 GB out of your 10 GB limit. You have used 150 MB of bandwidth this month across 3 active buckets. ``` ## Capabilities ### Manage Storage Usage and Metrics Check total storage capacity used across buckets or monitor bandwidth usage for specific gateways. ### Control IPNS Names and Keys Generate cryptographic keypairs, publish content identifiers (CIDs) to an IPNS name, and resolve those names back into live file paths. ### Provision Networking Gateways Create, update, list, or delete dedicated network gateways used to access your decentralized storage. ### Pin Content for Persistence Add, remove, replace, or list content identifiers (CIDs) using the Pinning Service API (PSA) to ensure data remains available long-term. ### Perform Raw IPFS Operations Upload text files directly to IPFS or retrieve raw blocks and file contents by their CID. ## Use Cases ### Auditing a new decentralized project A DevOps engineer needs to know if the initial infrastructure setup is complete. They ask their agent to run platform_list_gateways and then call platform_get_usage to ensure both network access points are provisioned and budgeted correctly. ### Deploying a mutable website A content creator wants a decentralized site. They use rpc_key_gen, then call rpc_name_publish to link the new CID via IPNS, and finally ask the agent to resolve it with rpc_name_resolve so they have the final URL. ### Securing mission-critical data A developer uploads a file using rpc_add. To guarantee it never disappears, they immediately tell their agent to run psa_add_pin on that content identifier (CID). This ensures persistent storage. ### Debugging resource issues The ops team notices high bandwidth usage. They use platform_get_gateway_usage for the primary gateway and then check overall capacity with platform_get_usage to isolate if the issue is localized or global. ## Benefits - You don't have to leave your chat window. Instead of running multiple CLI commands, you tell your agent to list gateways or check usage with platform_list_gateways and platform_get_usage. - The system handles complex key management for you. You can use rpc_key_gen to create a pair and rpc_name_publish to register it without ever touching the command line. - Pinning becomes automatic. When you need content to last forever, you don't just upload it; you call psa_add_pin, ensuring that data remains accessible long after your initial upload expires. - Full infrastructure control means no guessing games. You can use platform_get_gateway and platform_list_gateways together to map out exactly which network endpoints are active on your account. - You get granular visibility into resource consumption. Need to know if you're running out of space? Use platform_get_bucket_usage or platform_get_usage; it’s immediate, actionable data. ## How It Works The bottom line is, it lets your AI client interact with complex Web3 protocols—like IPFS and IPNS—as if they were simple commands in a chat window. 1. First, you subscribe to this MCP on Vinkius and enter your Filebase API Key and Platform Token into your AI client. 2. Next, you tell your agent the specific infrastructure task. For example, 'List all dedicated gateways' or 'Pin CID QmXoyp...'. 3. The tool executes the command against the decentralized network, giving you real-time data like usage metrics, a list of available names, or confirmation that content has been pinned. ## Frequently Asked Questions **How do I list all my current IPNS names using Filebase (Web3 Storage) MCP?** You use platform_list_names. This tool returns a comprehensive inventory of every IPNS name you've registered, letting you see what assets are publicly addressable via the network. **Do I need to run rpc_key_gen before publishing an asset with Filebase (Web3 Storage) MCP?** Yes. You must use rpc_key_gen first; this creates the cryptographic keypair needed to sign and publish content identifiers using rpc_name_publish. **What's the difference between psa_add_pin and rpc_pin_add in Filebase (Web3 Storage) MCP?** PSA is the high-level, dedicated Pinning Service API. RPC is the raw protocol call; use PSA unless you need to interact with the underlying IPFS daemon directly. **How can I check my total storage limit using Filebase (Web3 Storage) MCP?** Run platform_get_usage. This gives a single metric that aggregates both your overall storage and bandwidth usage across all connected resources, so you don't have to guess where the limits are. **How do I manage multiple entry points or check my connection status using `platform_list_gateways`?** You list all dedicated gateways with `platform_list_gateways`. This command provides an overview of every gateway you've set up, allowing you to see their current details and usage metrics. If you find a gateway that needs changes, you can then use `platform_update_gateway` or remove it entirely using `platform_delete_gateway`. **What is the difference between fetching raw data blocks with `rpc_block_get` and reading file contents using `rpc_cat`?** The key difference is the output format. Use `rpc_cat` when you need to read a human-readable text file by its CID. If you use `rpc_block_get`, you're accessing the raw, low-level data blocks of the IPFS network; this is for debugging or advanced technical analysis. **I created an IPNS name pointing to old content; how do I update it without recreating the entire record using `platform_update_name`?** You use `platform_update_name` to redirect your existing IPNS name. This is crucial because it lets you point that established name to a brand new CID, effectively updating its location without needing to delete and re-publish the resource entirely. **If I no longer use an old IPNS name or gateway, how do I safely remove these resources using `platform_delete_name` or `platform_delete_gateway`?** You must explicitly delete abandoned resources. Use `platform_delete_name` to reclaim an unused IPNS entry, and run `platform_delete_gateway` when you're finished with a dedicated connection endpoint. This ensures proper cleanup of your decentralized infrastructure. **How do I pin a specific CID to ensure it stays on the network?** You can use the `rpc_pin_add` tool by providing the CID. This ensures the content is persistently stored on Filebase's IPFS infrastructure. **Can I check my current storage usage and limits?** Yes! Use the `platform_get_usage` tool. It will return your total storage used, bandwidth metrics, and current subscription limits. **How do I publish a CID to a mutable IPNS name?** Use the `rpc_name_publish` tool with the target CID. This maps your content to an IPNS address that stays the same even when the content updates.