Filebase (Web3 Storage) MCP Server for CrewAIGive CrewAI instant access to 29 tools to Platform Create Gateway, Platform Create Name, Platform Delete Gateway, and more
GDPR Free for SubscribersConnect your CrewAI agents to Filebase (Web3 Storage) through Vinkius, pass the Edge URL in the `mcps` parameter and every Filebase (Web3 Storage) tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.
Ask AI about this MCP Server for CrewAI
The Filebase (Web3 Storage) MCP Server for CrewAI is a standout in the Developer Tools category — giving your AI agent 29 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
Geminifrom crewai import Agent, Task, Crew
agent = Agent(
role="Filebase (Web3 Storage) Specialist",
goal="Help users interact with Filebase (Web3 Storage) effectively",
backstory=(
"You are an expert at leveraging Filebase (Web3 Storage) tools "
"for automation and data analysis."
),
# Your Vinkius token. get it at cloud.vinkius.com
mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)
task = Task(
description=(
"Explore all available tools in Filebase (Web3 Storage) "
"and summarize their capabilities."
),
agent=agent,
expected_output=(
"A detailed summary of 29 available tools "
"and what they can do."
),
)
crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
* 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
About 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.
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.
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.
The Filebase (Web3 Storage) MCP Server exposes 29 tools through the Vinkius. Connect it to CrewAI in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
All 29 Filebase (Web3 Storage) tools available for CrewAI
When CrewAI connects to Filebase (Web3 Storage) through Vinkius, your AI agent gets direct access to every tool listed below — spanning ipfs, web3, decentralized-storage, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.
Platform create gateway on Filebase (Web3 Storage)
Create a new dedicated gateway
Platform create name on Filebase (Web3 Storage)
Create a new IPNS name
Platform delete gateway on Filebase (Web3 Storage)
Delete a dedicated gateway
Platform delete name on Filebase (Web3 Storage)
Delete an IPNS name
Platform get bucket usage on Filebase (Web3 Storage)
Get storage usage for a specific bucket
Platform get gateway on Filebase (Web3 Storage)
Get details of a specific dedicated gateway
Platform get gateway usage on Filebase (Web3 Storage)
Get bandwidth usage for a dedicated gateway
Platform get name on Filebase (Web3 Storage)
Get details of a specific IPNS name
Platform get usage on Filebase (Web3 Storage)
Get total storage and bandwidth usage
Platform list gateways on Filebase (Web3 Storage)
List all dedicated gateways
Platform list names on Filebase (Web3 Storage)
List all IPNS names
Platform update gateway on Filebase (Web3 Storage)
Update a dedicated gateway
Platform update name on Filebase (Web3 Storage)
Update an IPNS name to point to a new CID
Psa add pin on Filebase (Web3 Storage)
Add a pin using the Pinning Service API
Psa get pin on Filebase (Web3 Storage)
Get pin status by request ID
Psa list pins on Filebase (Web3 Storage)
List pins using the Pinning Service API
Psa remove pin on Filebase (Web3 Storage)
Remove a pin by request ID
Psa replace pin on Filebase (Web3 Storage)
Replace an existing pin
Rpc add on Filebase (Web3 Storage)
Add a text file to IPFS
Rpc block get on Filebase (Web3 Storage)
Retrieve a raw block by CID
Rpc cat on Filebase (Web3 Storage)
Fetch contents of a file by CID
Rpc key gen on Filebase (Web3 Storage)
Create a new keypair
Rpc key list on Filebase (Web3 Storage)
List all keys in the keychain
Rpc name publish on Filebase (Web3 Storage)
Publish a CID to IPNS
Rpc name resolve on Filebase (Web3 Storage)
Resolve an IPNS name to an IPFS path
Rpc pin add on Filebase (Web3 Storage)
Pin a CID to persistent storage
Rpc pin ls on Filebase (Web3 Storage)
List all pinned objects via RPC
Rpc pin rm on Filebase (Web3 Storage)
Unpin a CID via RPC
Rpc version on Filebase (Web3 Storage)
Get the version of the IPFS daemon
Connect Filebase (Web3 Storage) to CrewAI via MCP
Follow these steps to wire Filebase (Web3 Storage) into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.
Install CrewAI
pip install crewaiReplace the token
[YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.comCustomize the agent
role, goal, and backstory to fit your use caseRun the crew
python crew.py. CrewAI auto-discovers 29 tools from Filebase (Web3 Storage)Why Use CrewAI with the Filebase (Web3 Storage) MCP Server
CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Filebase (Web3 Storage) through the Model Context Protocol.
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 `mcps` parameter 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) + CrewAI Use Cases
Practical scenarios where CrewAI combined with the Filebase (Web3 Storage) MCP Server delivers measurable value.
Automated multi-step research: a reconnaissance agent queries Filebase (Web3 Storage) for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff
Scheduled intelligence reports: set up a crew that periodically queries Filebase (Web3 Storage), analyzes trends over time, and generates executive briefings in markdown or PDF format
Multi-source enrichment pipelines: chain Filebase (Web3 Storage) tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow
Compliance and audit automation: a compliance agent queries Filebase (Web3 Storage) against predefined policy rules, generates deviation reports, and routes findings to the appropriate team
Example Prompts for Filebase (Web3 Storage) in CrewAI
Ready-to-use prompts you can give your CrewAI agent to start working with Filebase (Web3 Storage) immediately.
"Upload the text 'Hello from Filebase MCP' to IPFS."
"Show me a list of all my pinned objects."
"What is my current storage usage on Filebase?"
Troubleshooting Filebase (Web3 Storage) MCP Server with CrewAI
Common issues when connecting Filebase (Web3 Storage) to CrewAI through Vinkius, and how to resolve them.
MCP tools not discovered
Agent not using tools
Timeout errors
Rate limiting or 429 errors
Filebase (Web3 Storage) + CrewAI FAQ
Common questions about integrating Filebase (Web3 Storage) MCP Server with CrewAI.
How does CrewAI discover and connect to MCP tools?
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?
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?
Can CrewAI agents call multiple MCP tools in parallel?
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)?
crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.Explore More MCP Servers
View all →
Strava Social
10 toolsExplore Strava activities feed, kudos, comments, clubs, and discover new segments.
Clio
8 toolsManage legal practice and matters via Clio — track cases, monitor contacts, and manage firm tasks directly from any AI agent.
LaunchDarkly
9 toolsManage LaunchDarkly feature flags, environments, assignments and deployments smoothly through conversational AI.
Azure Blob Container
4 toolsThis MCP does exactly one thing: it manages files in a single Azure Blob Container. That's its only function, and nothing else. Incredible for giving your AI secure file storage.