2,500+ MCP servers ready to use
Vinkius

Backblaze B2 MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Backblaze B2 and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "backblaze-b2": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Backblaze B2
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 Backblaze B2 MCP Server

Connect your Backblaze B2 account to any AI agent and manage your cloud storage architecture directly through natural conversation.

GitHub Copilot Agent mode brings Backblaze B2 data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

O que você pode fazer

  • Buckets — Create, delete, update privacy (allPrivate/allPublic), and list globally mapped storage buckets
  • File Management — Hide files (soft delete), remove explicit file versions (hard delete), and list surface names
  • Health Validation — List unfinished large file chunks to find failed multipart uploads
  • File Intelligence — Retrieve granular file details, sizes, hashes (SHA1), and content types natively

Como funciona

1. Subscribe to this server
2. Enter your Backblaze B2 Application Key ID and Key
3. Start architecting storage and debugging files from Claude, Cursor, or any MCP-compatible client

Your AI agent now has the power to orchestrate secure and cost-effective object storage without leaving your editor.

Para quem é?

  • DevOps Engineers — rapidly verify bucket states, clean up abandoned file versions, and debug failed multipart streams
  • Backend Developers — create public and private storage domains directly from development spaces
  • System Administrators — audit object footprint securely and perform granular file integrity checks

The Backblaze B2 MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Backblaze B2 to VS Code Copilot via MCP

Follow these steps to integrate the Backblaze B2 MCP Server with VS Code Copilot.

01

Create MCP config

Create a .vscode/mcp.json file in your project root

02

Add the server config

Paste the JSON configuration above

03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

04

Start using Backblaze B2

Ask Copilot: "Using Backblaze B2, help me...". 10 tools available

Why Use VS Code Copilot with the Backblaze B2 MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Backblaze B2 through the Model Context Protocol.

01

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

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Backblaze B2 + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Backblaze B2 MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Backblaze B2 MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Backblaze B2 to VS Code Copilot via MCP:

01

authorize_account

Uncovers the dynamically assigned apiUrl (e.g. api003.backblazeb2.com) natively orchestrating regional data ingress specifically assigned to your billing account. Verify and extract Backblaze global session routing endpoints

02

create_bucket

Bootstraps essential structures before assigning automated backup syncs overriding file lock retention bounds. Provision a fresh logical Storage Bucket partition

03

delete_bucket

Fails intentionally via 400 Bad Request if standard files or hidden object versions persist nested inside. Ensure all lifecycle rules completed purging prior to command. Irreversibly delete an entirely empty Backblaze Storage Bucket

04

delete_file_version

Instantly removes the storage footprint avoiding long-term retention hoarding. Irreversibly vaporize specific absolute chunk data from disk arrays

05

get_file_info

Obtain granular checksum and headers associated with one precise B2 File

06

hide_file

Does not actually delete binary payload, merely injects a null-marker shadowing the actual file ensuring b2_list_file_names ignores it, enforcing safe soft deletion logic. Mark an active B2 file as hidden leaving data for lifecycle sweep

07

list_buckets

Crucial to resolve immutable String Bucket IDs prerequisite to executing downstream CRUD operations strictly inside native borders. Retrieve the exact Storage Buckets existing globally on the B2 Account

08

list_file_names

Examines precise .pdf, .mp4 file locations avoiding hidden shadowed states produced by lifecycle overwrite semantics. Paginate primary surface-level object metadata from a specific Bucket

09

list_unfinished_large_files

Crucial for verifying broken API pipelines originating from external S3 clients failing CompleteMultipartUpload. Scan B2 nodes for stalled Multipart Upload chunk aggregates

10

update_bucket

Use only for static asset endpoints. Mutate global ACL privacy settings for a bounded Bucket

Example Prompts for Backblaze B2 in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Backblaze B2 immediately.

01

"What buckets do we have enabled in Backblaze B2 right now?"

02

"Create a new private bucket named 'ai-crawler-logs-2026' and make it private."

03

"Get the file details and SHA1 for the object 'index.html' in the public bucket."

Troubleshooting Backblaze B2 MCP Server with VS Code Copilot

Common issues when connecting Backblaze B2 to VS Code Copilot through the Vinkius, and how to resolve them.

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Backblaze B2 + VS Code Copilot FAQ

Common questions about integrating Backblaze B2 MCP Server with VS Code Copilot.

01

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.
02

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.
03

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.
04

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.

Connect Backblaze B2 to VS Code Copilot

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.