Bring Ipfs
to LangChain
Learn how to connect Filebase (Web3 Storage) to LangChain 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 LangChain?
LangChain's ecosystem of 500+ components combines seamlessly with Filebase (Web3 Storage) through native MCP adapters. Connect 29 tools via Vinkius and use ReAct agents, Plan-and-Execute strategies, or custom agent architectures. with LangSmith tracing giving full visibility into every tool call, latency, and token cost.
- —
The largest ecosystem of integrations, chains, and agents. combine Filebase (Web3 Storage) MCP tools with 500+ LangChain components
- —
Agent architecture supports ReAct, Plan-and-Execute, and custom strategies with full MCP tool access at every step
- —
LangSmith tracing gives you complete visibility into tool calls, latencies, and token usage for production debugging
- —
Memory and conversation persistence let agents maintain context across Filebase (Web3 Storage) queries for multi-turn workflows
Filebase (Web3 Storage) in LangChain
Filebase (Web3 Storage) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Filebase (Web3 Storage) to LangChain 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 LangChain
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 LangChain 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 LangChain
Every tool call from LangChain 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 LangChain connect to MCP servers?
Use langchain-mcp-adapters to create an MCP client. LangChain discovers all tools and wraps them as native LangChain tools compatible with any agent type.
Which LangChain agent types work with MCP?
All agent types including ReAct, OpenAI Functions, and custom agents work with MCP tools. The tools appear as standard LangChain tools after the adapter wraps them.
Can I trace MCP tool calls in LangSmith?
Yes. All MCP tool invocations appear as traced steps in LangSmith, showing input parameters, response payloads, latency, and token usage.
MultiServerMCPClient not found
Install: pip install langchain-mcp-adapters
Explore More MCP Servers
View all →
Mercado Livre Orders
7 toolsSearch sales, manage shipments, track packages, and handle cancellations on Mercado Livre.
Deterministic URL Engine
3 toolsEquip your AI with flawless URL deconstruction. Deterministically parse URIs, extract deep query strings, and inject tracking parameters without concatenation errors.
LinkedIn Ads
6 toolsAccess marketing analytics, campaigns, and reporting via the LinkedIn Ads REST API.
Code Climate
8 toolsManage code quality and engineering metrics via Code Climate — track repository grades, monitor snapshots, and audit test coverage directly from any AI agent.