Spring Boot AI Cloudflare R2 MCP Server

Created By
lskuna year ago
Spring Boot AI Cloudflare R2 MCP Server - 一个基于Spring Boot和Spring AI的Cloudflare R2对象存储MCP服务器实现
Overview

What is Spring Boot AI Cloudflare R2 MCP Server?

Spring Boot AI Cloudflare R2 MCP Server is a Model Context Protocol (MCP) server implementation based on Spring Boot and Spring AI, providing integration with Cloudflare R2 object storage service.

How to use Spring Boot AI Cloudflare R2 MCP Server?

To use the server, clone the repository, set up your Cloudflare R2 credentials as environment variables, build the project using Maven, and run integration tests to ensure everything is working correctly.

Key features of Spring Boot AI Cloudflare R2 MCP Server?

  • Complete Cloudflare R2 object storage operation support
  • Integration with Spring AI's MCP server
  • Support for various file types (text, binary, etc.)
  • Comprehensive test coverage
  • Easy configuration and deployment

Use cases of Spring Boot AI Cloudflare R2 MCP Server?

  1. Managing object storage in Cloudflare R2
  2. Integrating with applications that require file storage and retrieval
  3. Performing operations like uploading, downloading, and managing metadata of objects in R2

FAQ from Spring Boot AI Cloudflare R2 MCP Server?

  • What are the prerequisites for using this server?

You need JDK 17 or above, Maven 3.6 or above, and a Cloudflare R2 account with credentials.

  • How do I configure the server?

Modify the application.properties file with your R2 credentials.

  • Is there support for different file types?

Yes, the server supports various file types including text and binary.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
lskun
Star
1
Language
Java
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago