AutoGenFramework

Filebase (Web3 Storage) MCP Server

Bring Ipfs
to AutoGen

Name: Filebase (Web3 Storage) MCP Server
Price: 29 USD
Availability: InStock
Rating: 4.9 (1 reviews)
Author: Vinkius

Learn how to connect Filebase (Web3 Storage) to AutoGen and start using 29 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

GDPR Free for Subscribers

Platform Create GatewayPlatform Create NamePlatform Delete GatewayPlatform Delete NamePlatform Get Bucket UsagePlatform Get GatewayPlatform Get Gateway UsagePlatform Get NamePlatform Get UsagePlatform List GatewaysPlatform List NamesPlatform Update GatewayPlatform Update NamePsa Add PinPsa Get PinPsa List PinsPsa Remove PinPsa Replace PinRpc AddRpc Block GetRpc CatRpc Key GenRpc Key ListRpc Name PublishRpc Name ResolveRpc Pin AddRpc Pin LsRpc Pin RmRpc Version

Unlock for AI Agents

Ask AI about this MCP Server ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

What is the Filebase (Web3 Storage) MCP Server?

Connect your Filebase account to any AI agent and take full control of your decentralized Web3 storage workflows through natural conversation.

What you can do

IPFS Operations — Add text files, fetch content by CID, and manage raw blocks directly on the IPFS network using the RPC API.
Pinning Management — Use the Pinning Service API (PSA) or RPC to pin, list, and remove content identifiers (CIDs) for persistent storage.
IPNS & Keys — Generate keypairs, publish CIDs to IPNS, and resolve names to IPFS paths for mutable decentralized websites.
Usage & Infrastructure — Monitor storage usage, manage dedicated gateways, and track bucket metrics across the platform.

How it works

Subscribe to this server
Enter your Filebase API Key and Platform Token
Start managing your Web3 assets from Claude, Cursor, or any MCP-compatible client

Who is this for?

Web3 Developers — interact with IPFS and IPNS directly from your coding environment without switching to CLI or web dashboards.
DevOps Engineers — automate pinning and storage monitoring as part of your infrastructure workflows.
Content Creators — manage decentralized assets and metadata for NFTs or dApps using simple natural language commands.

Built-in capabilities (29)

platform_create_gateway

Create a new dedicated gateway

platform_create_name

Create a new IPNS name

platform_delete_gateway

Delete a dedicated gateway

platform_delete_name

Delete an IPNS name

platform_get_bucket_usage

Get storage usage for a specific bucket

platform_get_gateway

Get details of a specific dedicated gateway

platform_get_gateway_usage

Get bandwidth usage for a dedicated gateway

platform_get_name

Get details of a specific IPNS name

platform_get_usage

Get total storage and bandwidth usage

platform_list_gateways

List all dedicated gateways

platform_list_names

List all IPNS names

platform_update_gateway

Update a dedicated gateway

platform_update_name

Update an IPNS name to point to a new CID

psa_add_pin

Add a pin using the Pinning Service API

psa_get_pin

Get pin status by request ID

psa_list_pins

List pins using the Pinning Service API

psa_remove_pin

Remove a pin by request ID

psa_replace_pin

Replace an existing pin

rpc_add

Add a text file to IPFS

rpc_block_get

Retrieve a raw block by CID

rpc_cat

Fetch contents of a file by CID

rpc_key_gen

Create a new keypair

rpc_key_list

List all keys in the keychain

rpc_name_publish

Publish a CID to IPNS

rpc_name_resolve

Resolve an IPNS name to an IPFS path

rpc_pin_add

Pin a CID to persistent storage

rpc_pin_ls

List all pinned objects via RPC

rpc_pin_rm

Unpin a CID via RPC

rpc_version

Get the version of the IPFS daemon

Why AutoGen?

AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use Filebase (Web3 Storage) tools. Connect 29 tools through Vinkius and assign role-based access. a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.

—
Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use Filebase (Web3 Storage) tools to solve complex tasks
—
Role-based architecture lets you assign Filebase (Web3 Storage) tool access to specific agents. a data analyst queries while a reviewer validates
—
Human-in-the-loop support: agents can pause for human approval before executing sensitive Filebase (Web3 Storage) tool calls
—
Code execution sandbox: AutoGen agents can write and run code that processes Filebase (Web3 Storage) tool responses in an isolated environment

See it in action

Filebase (Web3 Storage) in AutoGen

AI Agent→Vinkius

High Security·Kill Switch·Plug and Play

Why Vinkius

Filebase (Web3 Storage) and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Filebase (Web3 Storage) to AutoGen through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready

<40msCold start

60%Token savings

	Raw MCP	Vinkius
Server catalog	Find and host yourself	4,000+ managed
Infrastructure	Self-hosted	Sandboxed V8 isolates
Credential handling	Plaintext in config	Vault + runtime injection
Data loss prevention	None	Configurable DLP policies
Kill switch	None	Global instant shutdown
Financial circuit breakers	None	Per-server limits + alerts
Audit trail	None	Ed25519 signed logs
SIEM log streaming	None	Splunk, Datadog, Webhook
Honeytokens	None	Canary alerts on leak
Custom domains	Not applicable	DNS challenge verified
GDPR compliance	Manual effort	Automated purge + export

Unlock for AI Agents View step-by-step setup guide for AutoGen →

Enterprise Security

Why teams choose Vinkius for Filebase (Web3 Storage) in AutoGen

The Filebase (Web3 Storage) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 29 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in AutoGen only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Unlock for AI Agents View full Filebase (Web3 Storage) details →

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures
Filebase (Web3 Storage) for AutoGen

Every tool call from AutoGen to the Filebase (Web3 Storage) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start

Ed25519Signed audit chain

60%Token savings

FAQ

Frequently asked questions

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.

How does AutoGen connect to MCP servers?

Create an MCP tool adapter and assign it to one or more agents in the group chat. AutoGen agents can then call Filebase (Web3 Storage) tools during their conversation turns.

Can different agents have different MCP tool access?

Yes. AutoGen's role-based architecture lets you assign specific MCP tools to specific agents, so a querying agent has different capabilities than a reviewing agent.