Oss Mcp

Created By
1yhya year ago
Overview

What is OSS MCP?

OSS MCP is a server based on the Model Context Protocol (MCP) that allows users to upload files directly to Alibaba Cloud OSS. It enables large language models to seamlessly integrate with cloud storage services.

How to use OSS MCP?

To use OSS MCP, install it via npm or from the source code, configure your Alibaba Cloud OSS parameters, and run the server using the provided command line options.

Key features of OSS MCP?

  • Supports multiple Alibaba Cloud OSS configurations
  • Allows specifying upload directories
  • Simple and user-friendly interface

Use cases of OSS MCP?

  1. Integrating with Playwright MCP for web resource uploads.
  2. Uploading images from Figma directly to OSS.
  3. Automating data backup processes to OSS.
  4. Managing multiple OSS accounts for easy switching.

FAQ from OSS MCP?

  • Can OSS MCP handle multiple OSS accounts?

Yes! OSS MCP allows you to configure and switch between multiple OSS accounts easily.

  • Is OSS MCP free to use?

Yes! OSS MCP is open-source and free to use.

  • How do I install OSS MCP?

You can install OSS MCP using npm or by cloning the repository from GitHub.

Server Config

{
  "mcpServers": {
    "oss-mcp": {
      "command": "npx",
      "args": [
        "oss-mcp",
        "--oss-config='{\"default\":{\"region\":\"oss-cn-shenzhen\",\"accessKeyId\":\"YOUR_KEY\",\"accessKeySecret\":\"YOUR_SECRET\",\"bucket\":\"YOUR_BUCKET\",\"endpoint\":\"oss-cn-shenzhen.aliyuncs.com\"}}'",
        "--stdio"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
1yhy
Star
-
Language
-
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.

32 minutes ago