Filebase (Web3 Storage) MCP Server for CursorGive Cursor instant access to 29 tools to Platform Create Gateway, Platform Create Name, Platform Delete Gateway, and more

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

GDPR Free for Subscribers

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

Ask AI about this MCP Server for Cursor

Open in ChatGPT Open in Claude Open in Perplexity

The Filebase (Web3 Storage) MCP Server for Cursor is a standout in the Developer Tools category — giving your AI agent 29 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

Classic Setup·json

{
  "mcpServers": {
    "filebase-web3-storage": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Filebase (Web3 Storage) and 4,000+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

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

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.

Cursor's Agent mode turns Filebase (Web3 Storage) into an in-editor superpower. Ask Cursor to generate code using live data from Filebase (Web3 Storage) and it fetches, processes, and writes. all in a single agentic loop. 29 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

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 Cursor 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 Cursor

When Cursor 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

Platform create gateway on Filebase (Web3 Storage)

Create a new dedicated gateway

platform

Platform create name on Filebase (Web3 Storage)

Create a new IPNS name

platform

Platform delete gateway on Filebase (Web3 Storage)

Delete a dedicated gateway

platform

Platform delete name on Filebase (Web3 Storage)

Delete an IPNS name

platform

Platform get bucket usage on Filebase (Web3 Storage)

Get storage usage for a specific bucket

platform

Platform get gateway on Filebase (Web3 Storage)

Get details of a specific dedicated gateway

platform

Platform get gateway usage on Filebase (Web3 Storage)

Get bandwidth usage for a dedicated gateway

platform

Platform get name on Filebase (Web3 Storage)

Get details of a specific IPNS name

platform

Platform get usage on Filebase (Web3 Storage)

Get total storage and bandwidth usage

platform

Platform list gateways on Filebase (Web3 Storage)

List all dedicated gateways

platform

Platform list names on Filebase (Web3 Storage)

List all IPNS names

platform

Platform update gateway on Filebase (Web3 Storage)

Update a dedicated gateway

platform

Platform update name on Filebase (Web3 Storage)

Update an IPNS name to point to a new CID

psa

Psa add pin on Filebase (Web3 Storage)

Add a pin using the Pinning Service API

psa

Psa get pin on Filebase (Web3 Storage)

Get pin status by request ID

psa

Psa list pins on Filebase (Web3 Storage)

List pins using the Pinning Service API

psa

Psa remove pin on Filebase (Web3 Storage)

Remove a pin by request ID

psa

Psa replace pin on Filebase (Web3 Storage)

Replace an existing pin

rpc

Rpc add on Filebase (Web3 Storage)

Add a text file to IPFS

rpc

Rpc block get on Filebase (Web3 Storage)

Retrieve a raw block by CID

rpc

Rpc cat on Filebase (Web3 Storage)

Fetch contents of a file by CID

rpc

Rpc key gen on Filebase (Web3 Storage)

Create a new keypair

rpc

Rpc key list on Filebase (Web3 Storage)

List all keys in the keychain

rpc

Rpc name publish on Filebase (Web3 Storage)

Publish a CID to IPNS

rpc

Rpc name resolve on Filebase (Web3 Storage)

Resolve an IPNS name to an IPFS path

rpc

Rpc pin add on Filebase (Web3 Storage)

Pin a CID to persistent storage

rpc

Rpc pin ls on Filebase (Web3 Storage)

List all pinned objects via RPC

rpc

Rpc pin rm on Filebase (Web3 Storage)

Unpin a CID via RPC

rpc

Rpc version on Filebase (Web3 Storage)

Get the version of the IPFS daemon

Connect Filebase (Web3 Storage) to Cursor via MCP

Follow these steps to wire Filebase (Web3 Storage) into Cursor. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"

Add the server config

Paste the JSON configuration above into the mcp.json file that opens

Save the file

Cursor will automatically detect the new MCP server

Start using Filebase (Web3 Storage)

Open Agent mode in chat and ask: "Using Filebase (Web3 Storage), help me...". 29 tools available

Why Use Cursor with the Filebase (Web3 Storage) MCP Server

Cursor AI Code Editor provides unique advantages when paired with Filebase (Web3 Storage) through the Model Context Protocol.

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

Filebase (Web3 Storage) + Cursor Use Cases

Practical scenarios where Cursor combined with the Filebase (Web3 Storage) MCP Server delivers measurable value.

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

Example Prompts for Filebase (Web3 Storage) in Cursor

Ready-to-use prompts you can give your Cursor 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 Cursor

Common issues when connecting Filebase (Web3 Storage) to Cursor through Vinkius, and how to resolve them.

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

Filebase (Web3 Storage) + Cursor FAQ

Common questions about integrating Filebase (Web3 Storage) MCP Server with Cursor.

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.