Compatible with every major AI agent and IDE
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 VS Code Copilot?
GitHub Copilot Agent mode brings Filebase (Web3 Storage) data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 29 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Filebase (Web3 Storage) in VS Code Copilot
Filebase (Web3 Storage) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Filebase (Web3 Storage) to VS Code Copilot 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 VS Code Copilot
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 VS Code Copilot 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 VS Code Copilot
Every tool call from VS Code Copilot 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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
Slack Bot
10 toolsControl and manage your Slack workspace — audit channels, messages, and users via AI.

Deterministic 50/30/20 Budget Engine
1 toolsTransform your AI into a hyper-precise financial controller. Mathematically enforce the 50/30/20 budgeting rule on pre-categorized expense pipelines to detect exact capital deviations.

Hostfully
10 toolsManage vacation rental properties, leads, and bookings via Hostfully API.

FamilySearch API
6 toolsManage genealogical research — audit persons, pedigrees, and records via AI.
