R2 Upload MCP Server

Created By
leonhoa year ago
Cloudflare R2 Upload MCP Server
Overview

what is R2 Upload MCP Server?

R2 Upload MCP Server is a Model Context Protocol (MCP) server designed for uploading files to Cloudflare R2 storage.

how to use R2 Upload MCP Server?

To use the server, configure the required environment variables with your Cloudflare R2 credentials, and then run the server to upload files using the provided API.

key features of R2 Upload MCP Server?

  • Automatic MIME type detection for uploaded files
  • Support for custom object keys and content types
  • Returns public URLs for uploaded files
  • Easy configuration through environment variables

use cases of R2 Upload MCP Server?

  1. Uploading images and documents to Cloudflare R2 for storage.
  2. Managing file uploads in web applications.
  3. Creating a custom file storage solution using Cloudflare R2.

FAQ from R2 Upload MCP Server?

  • What is required to run the server?

You need to set up environment variables with your Cloudflare account details and R2 bucket information.

  • Can I use a custom domain for uploaded files?

Yes! You can configure a custom domain for public file URLs by setting the R2_CUSTOM_DOMAIN environment variable.

  • What file types are supported?

The server supports various file types including images, documents, scripts, videos, and audio files.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
leonho
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago