Bring Ipfs
to CrewAI
Learn how to connect Filebase (Web3 Storage) to CrewAI 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 SubscribersCompatible with every major AI agent and IDE
Gemini
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)
Create a new dedicated gateway
Create a new IPNS name
Delete a dedicated gateway
Delete an IPNS name
Get storage usage for a specific bucket
Get details of a specific dedicated gateway
Get bandwidth usage for a dedicated gateway
Get details of a specific IPNS name
Get total storage and bandwidth usage
List all dedicated gateways
List all IPNS names
Update a dedicated gateway
Update an IPNS name to point to a new CID
Add a pin using the Pinning Service API
Get pin status by request ID
List pins using the Pinning Service API
Remove a pin by request ID
Replace an existing pin
Add a text file to IPFS
Retrieve a raw block by CID
Fetch contents of a file by CID
Create a new keypair
List all keys in the keychain
Publish a CID to IPNS
Resolve an IPNS name to an IPFS path
Pin a CID to persistent storage
List all pinned objects via RPC
Unpin a CID via RPC
Get the version of the IPFS daemon
Why CrewAI?
When paired with CrewAI, Filebase (Web3 Storage) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Filebase (Web3 Storage) tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Filebase (Web3 Storage) in CrewAI
Filebase (Web3 Storage) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Filebase (Web3 Storage) to CrewAI 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.
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 |
Why teams choose Vinkius for Filebase (Web3 Storage) in CrewAI
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 CrewAI 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.
* 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
How Vinkius secures
Filebase (Web3 Storage) for CrewAI
Every tool call from CrewAI to the Filebase (Web3 Storage) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
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 CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.
Explore More MCP Servers
View all →
Weiban Assistant
10 toolsCustomer relationship management for WeCom — manage leads, customers, and group chats via AI.
Swiftype
10 toolsConnect your AI to Elastic Swiftype. Query your search engines, manage documents, and retrieve deep analytical insights natively from the terminal.
LaunchDarkly
9 toolsManage LaunchDarkly feature flags, environments, assignments and deployments smoothly through conversational AI.
Apptoto
8 toolsManage appointments and messaging with Apptoto — track events, contacts, and bookings via AI.