mcpDrive

Created By
Brayan-22a year ago
This repository contains a project to implement mcp server in spring for google drive
Overview

what is mcpDrive?

mcpDrive is a project that implements an MCP (Multi-Channel Protocol) server in Spring framework specifically for Google Drive integration.

how to use mcpDrive?

To use mcpDrive, clone the repository from GitHub, set up the Spring environment, and configure the server to connect with Google Drive API.

key features of mcpDrive?

  • Integration with Google Drive for file management
  • Built using Spring framework for robust performance
  • Supports multi-channel communication for enhanced functionality

use cases of mcpDrive?

  1. Managing files on Google Drive through a custom server.
  2. Implementing multi-channel protocols for data transfer.
  3. Developing applications that require Google Drive integration.

FAQ from mcpDrive?

  • What programming language is used in mcpDrive?

mcpDrive is developed in Java using the Spring framework.

  • Is mcpDrive open source?

Yes! mcpDrive is licensed under the GPL-3.0 license and is open for contributions.

  • How can I contribute to mcpDrive?

You can contribute by forking the repository, making changes, and submitting a pull request.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Brayan-22
Star
0
Language
Java
License
GPL-3.0 license

Recommend Servers

View All
Payai X402 Tools

6 hours 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.

a day ago