Cloudflare R2 Remote MCP Worker
XxYouDeaDPunKxX/cloudflare-r2-remote-mcp-worker
Acesse buckets R2 do Cloudflare via MCP em Workers com OAuth
Ver no GitHubServidor MCP remoto que expõe operações de objetos do Cloudflare R2 através de um endpoint Worker. Permite leitura, escrita, cópia e exclusão de arquivos em buckets R2, com suporte a autenticação GitHub OAuth e ferramentas opcionais de URLs pré-assinadas.
Instalação
npx convez-ai XxYouDeaDPunKxX/cloudflare-r2-remote-mcp-worker1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Integrar R2 com Claude/ChatGPT para manipulação remota de arquivos
- Gerenciar objetos em buckets R2 através de assistentes IA
- Exposer operações de storage S3-compatível como ferramentas MCP
Veredito

Solução técnica sólida para quem já trabalha com Cloudflare Workers e R2. Requer configuração não-trivial (OAuth, KV namespaces, secrets), mas oferece integração robusta entre IA e storage em edge computing.
README
A tradução para o português deste README ainda está na fila.
🪣 Cloudflare R2 Remote MCP Worker
Remote MCP server for Cloudflare R2 on Cloudflare Workers.
🧭 What This Is
This Worker exposes R2 object operations through a remote MCP endpoint:
ChatGPT / MCP client
-> GitHub OAuth
-> Cloudflare Worker /mcp
-> R2 bucket
The main surface is object-level access to one bound R2 bucket. Account-level tools are optional and read-only. Presigned URL tools are optional and use R2 S3 credentials.
This is not full Cloudflare R2 account administration. Mutating account operations such as bucket creation, CORS updates, lifecycle updates, domain changes, and notification changes are intentionally not exposed as MCP tools.
🧩 What It Exposes
| Surface | Used for | Credentials |
|---|---|---|
| Worker R2 binding | Object list/head/get/put/delete/copy/move/rename in the bound bucket. | Cloudflare Worker R2 binding |
| Cloudflare API | Optional read-only bucket/admin visibility. | Cloudflare API token |
| S3-compatible API | Optional presigned GET/PUT URLs. | R2 access key and secret |
Default enabled tools:
- object tools
- base64 upload/download tools
- GitHub OAuth protection when
AUTH_MODE=github
Optional tools:
- read-only account/admin tools with
ENABLE_ACCOUNT_TOOLS=true - presigned URL tools with
ENABLE_PRESIGN_TOOLS=true
📦 Required Pieces
- Node.js 20 or newer
- Wrangler 4
- Cloudflare account
- R2 bucket
- Cloudflare Worker
- GitHub OAuth App for public deployments
- MCP client, for example ChatGPT custom MCP connector or MCP Inspector
🛠️ Setup Order
1. Install
npm install
npx wrangler login
2. Create Buckets
npx wrangler r2 bucket create your-bucket-name
npx wrangler r2 bucket create your-preview-bucket-name
3. Configure Worker
cp wrangler.example.jsonc wrangler.jsonc
Edit:
namer2_buckets[0].bucket_namer2_buckets[0].preview_bucket_namevars.R2_BUCKET_NAMEvars.AUTH_MODEvars.ALLOWED_GITHUB_LOGINS
Do not commit wrangler.jsonc.
4. Configure Local Dev Variables
cp .dev.vars.example .dev.vars
.dev.vars.example uses AUTH_MODE=none for local development.
Public deployments should use:
AUTH_MODE=github
Do not commit .dev.vars.
5. Configure OAuth State
npx wrangler kv namespace create OAUTH_KV
Add the generated namespace ID to wrangler.jsonc.
6. Configure GitHub OAuth
Create a GitHub OAuth App.
Callback URL:
https://<worker-name>.<account-subdomain>.workers.dev/callback
Set secrets:
npx wrangler secret put GITHUB_CLIENT_ID -c wrangler.jsonc
npx wrangler secret put GITHUB_CLIENT_SECRET -c wrangler.jsonc
npx wrangler secret put COOKIE_ENCRYPTION_KEY -c wrangler.jsonc
GitHub OAuth verifies the login allowed to access the MCP endpoint. It does not grant access to GitHub repositories.
7. Deploy
npm run deploy
MCP endpoint:
https://<worker-name>.<account-subdomain>.workers.dev/mcp
Health endpoint:
https://<worker-name>.<account-subdomain>.workers.dev/healthz
8. Connect ChatGPT
Add a custom MCP connector:
URL = https://<worker-name>.<account-subdomain>.workers.dev/mcp
Auth = OAuth
Approve through GitHub with a login listed in ALLOWED_GITHUB_LOGINS, then refresh/list tools.
9. Verify
npm run type-check
npm run smoke
Then verify:
/healthzreturnsok: true- MCP
tools/listreturns object tools - ChatGPT or MCP Inspector can see
r2_object_list
See Verify.
🧪 Local Development
Run:
npm run dev
Local endpoints:
http://localhost:8787/healthz
http://localhost:8787/mcp
Local authless development is controlled by:
AUTH_MODE=none
Do not expose AUTH_MODE=none on a public URL unless another access layer protects the Worker.
🔐 Security Defaults
- Public auth mode defaults to GitHub OAuth when
AUTH_MODEis omitted. - Account/admin tools are disabled by default.
- Account/admin tools are read-only when enabled.
- Presigned URL tools are disabled by default.
- Destructive object tools require
confirm: true. - Batch delete, move, and rename support
dryRun: true. R2_ROOT_PREFIXcan restrict object operations to one prefix.
📚 Documentation
📄 License
MIT. See LICENSE.
🤖 AI-assisted development
This project was developed with AI assistance.
The project, documentation, and repository materials were shaped through human-directed work supported by AI tools during drafting, structuring, review, and refinement.
AI assistance does not make the project automatically correct, complete, or suitable for every use case. Read it, test it, and adapt it to your own context.