wos MCP Server

Created By
Wangsu-Cloud-Storagea year ago
Overview

what is wos MCP Server?

The wos MCP Server is a Model Context Protocol (MCP) server built on Wangsu Cloud products, allowing users to access Wangsu Cloud storage and intelligent multimedia services within the context of AI large model clients.

how to use wos MCP Server?

To use the wos MCP Server, clone the repository, set up a virtual environment, install dependencies, configure environment variables, and then start the server using the provided commands.

key features of wos MCP Server?

  • Access to Wangsu Cloud storage and multimedia services.
  • Supports standard input/output and SSE modes for web applications.
  • Extensible architecture for adding new functionalities.

use cases of wos MCP Server?

  1. Integrating cloud storage services with AI applications.
  2. Facilitating multimedia processing in AI workflows.
  3. Enabling developers to build custom features on top of the MCP server.

FAQ from wos MCP Server?

  • What are the prerequisites for using wos MCP Server?

You need Python 3.12 or higher and the uv package manager.

  • How do I configure the server?

You need to set up environment variables for access keys, region, and bucket information in the .env file.

  • Can I extend the functionality of the wos MCP Server?

Yes! You can create new business packages in the core directory to extend functionalities.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Wangsu-Cloud-Storage
Star
0
Language
Python
License
-
Tags

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