# Filebase (Web3 Storage) MCP for AI Agents AI Agent Connect

> Filebase (Web3 Storage) MCP lets you manage decentralized storage on IPFS through your AI agent. You can upload files, manage IPNS names, handle pinning, and track your storage usage without leaving your chat window. It's the fastest way to manage Web3 assets using natural language.

## Overview
- **Category:** developer-tools
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_OPv3snjtznHNAQHV1vuWt9PMh8t0GNlwIPiwQnJT/ai-agent-connect
- **Tags:** ipfs, web3, decentralized-storage, pinning-service, ipns

## Description

You can handle your decentralized storage without leaving your chat window. Instead of jumping between a terminal and a web dashboard, you just tell your agent what needs to happen. This Connector connects your Filebase account to your AI client so you can manage IPFS files, handle pinning, and monitor your usage in one place. It's part of the Vinkius catalog, making it easy to add to your existing setup. You can generate keys, resolve names, and track your gateway bandwidth through simple conversation. It turns complex Web3 infrastructure into a few quick commands.

## Tools

### platform_create_name
Create a new IPNS name for your content. This lets you give your files a permanent, mutable address on the network.

### platform_delete_gateway
Delete a dedicated gateway you no longer need. This helps you clean up your infrastructure.

### platform_delete_name
Delete an IPNS name you no longer use. This keeps your list of mutable names clean.

### platform_get_bucket_usage
Check how much storage a specific bucket is using. It helps you stay within your storage limits easily.

### platform_get_gateway
Get the details of a specific dedicated gateway. Use this to see the configuration and status of your connections.

### platform_get_gateway_usage
Check the bandwidth usage for a dedicated gateway. This is useful for monitoring your data flow.

### platform_get_name
Get the details of a specific IPNS name. Use this to see where your mutable name is currently pointing.

### platform_get_usage
Get your total storage and bandwidth usage across the platform. This gives you a high-level view of your account metrics.

### platform_list_gateways
List all your dedicated gateways in one go. This helps you see every active connection you have.

### platform_list_names
List all your IPNS names. This is the fastest way to see every mutable address you own.

### platform_update_gateway
Update a dedicated gateway's settings. Use this to modify your connection parameters without deleting the gateway.

### platform_update_name
Update an IPNS name to point to a new CID. This is how you update your decentralized website content.

### psa_add_pin
Add a pin using the Pinning Service API. This ensures your content stays accessible on the network.

### psa_get_pin
Get the status of a specific pin by its request ID. Use this to check if your content is successfully pinned.

### psa_list_pins
List all your pins using the Pinning Service API. This gives you a clear view of your persistent storage.

### psa_remove_pin
Remove a pin by its request ID. Use this to stop your agent from keeping specific content pinned.

### psa_replace_pin
Replace an existing pin with a new one. This is useful for swapping content while maintaining the same pin request.

### rpc_block_get
Retrieve a raw block by its CID. This is for advanced users who need to see the underlying data.

### rpc_cat
Fetch the contents of a file by its CID. This lets your agent read the actual data stored on IPFS.

### rpc_key_gen
Create a new keypair for your IPNS names. This is the first step in managing mutable addresses.

### rpc_key_list
List all the keys in your keychain. Use this to manage your access to different IPNS names.

### rpc_name_publish
Publish a CID to IPNS. This makes your content reachable via a mutable name.

### rpc_name_resolve
Resolve an IPNS name to its current IPFS path. Use this to find where a name currently points.

### rpc_pin_add
Pin a CID to persistent storage using the RPC. This keeps your data available for the long term.

### rpc_pin_ls
List all pinned objects via the RPC. This is a direct way to see your persistent storage status.

### rpc_pin_rm
Unpin a CID via the RPC. Use this to remove content from your persistent storage.

### rpc_version
Get the current version of your IPFS daemon. This helps you check your local node's software status.

### platform_create_gateway
Create a new dedicated gateway for your traffic. Use this to expand your network reach.

### rpc_add
Add a new text file to IPFS. This is the quickest way to put new data on the decentralized network.

## Prompt Examples

**Prompt:** 
```
I just uploaded a new version of my site. Can you update my IPNS name to the new CID?
```

**Response:** 
```
I've updated your IPNS name. It now points to `QmXoyp...` and is ready for your users to see.
```

**Prompt:** 
```
How much storage do I have left in my main bucket?
```

**Response:** 
```
You're currently using 4.2 GB out of your 10 GB limit. That leaves you with 5.8 GB available.
```

**Prompt:** 
```
List all my active pins so I can see what's still on the network.
```

**Response:** 
```
I found 12 active pins. Here are the most recent ones:

| CID | Status |
| --- | --- |
| QmXoyp... | Pinned |
| bafy... | Pinning |
```

## Capabilities

### Pin content to persistent storage
Use the Pinning Service API to keep your files accessible on the network indefinitely.

### Manage IPNS names
Create, update, and resolve IPNS names to point to specific IPFS paths for mutable websites.

### Fetch IPFS content
Retrieve text files or raw blocks by their CID directly through your agent.

### Monitor infrastructure
Track your total storage, bandwidth usage, and dedicated gateway metrics in real-time.

### Manage dedicated gateways
Create, update, or delete dedicated gateways to handle your specific traffic needs.

## Use Cases

### Updating a decentralized website
A developer wants to point an IPNS name to a new site version. They ask the agent to use platform_update_name to swap the CID.

### Checking storage limits
A project lead wants to know if they're over budget. They ask the agent to run platform_get_bucket_usage for their main bucket.

### Automating content pinning
A creator uploads a batch of images. They ask the agent to use psa_add_pin for every new CID to ensure they stay online.

### Deploying a new gateway
A dev needs more bandwidth for a dApp. They ask the agent to use platform_create_gateway to set up a new dedicated connection.

## Benefits

- Keep your data persistent without opening a terminal by using rpc_pin_add to manage your content.
- Update your decentralized website content instantly by using platform_update_name to point to new CIDs.
- Monitor your infrastructure easily with platform_list_gateways to see every active connection.
- Keep a close eye on your costs with platform_get_usage to see your total storage and bandwidth.
- Simplify content retrieval with rpc_cat so your agent can read file contents directly from the network.

## How It Works

The bottom line is you get a natural language interface for complex Web3 storage operations.

1. Provide your Filebase API Key and Platform Token to the Vinkius dashboard.
2. Open your AI client and tell your agent to perform an action like pinning a CID.
3. The agent executes the request and gives you back the status or content immediately.

## Frequently Asked Questions

**What can I do with the Filebase (Web3 Storage) MCP?**
You can manage IPFS files, handle content pinning, and manage IPNS names. You can also monitor your storage and gateway usage through a natural conversation with your agent.

**Can I use this to manage my decentralized website?**
Yes. By using IPNS name tools, you can point your mutable names to different IPFS paths, making it easy to update your website content without changing the URL.

**How do I see my storage usage with Filebase (Web3 Storage) MCP?**
Just ask your agent to check your storage usage. It can report on your total account metrics or check the specific usage for individual buckets.

**Can I automate my content pinning?**
Yes. Your agent can use the Pinning Service API to ensure your content stays accessible on the network without you needing to run manual commands.

**Is the Filebase (Web3 Storage) MCP good for Web3 developers?**
It is ideal for developers who want to skip the CLI. It lets you perform common Web3 storage tasks like resolving names and pinning content directly from your workspace.

**How does this help with my bandwidth limits?**
The Connector can list your dedicated gateways and report on their specific bandwidth usage, helping you monitor your traffic and stay within your plan limits.

**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.