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
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago