Qiniu MCP Server

What qiniu/qiniu-mcp-server MCP server does

qiniu/qiniu-mcp-server MCP server connects an MCP client to several Qiniu Cloud product areas. Its storage capabilities include listing available buckets, listing objects within a bucket, uploading local files or supplied content, reading file contents, and generating download links. Storage access is configured for selected buckets through environment variables.

The server also exposes a limited set of image operations, including resizing an image and applying rounded corners. CDN functions can refresh or prefetch a file by URL. Live service functions cover creating live-space buckets and streams, listing live spaces and streams, binding push and playback domains, generating stream addresses, and retrieving live usage.

How it works

The default transport is standard input/output, which makes the server suitable for desktop and editor clients that launch local MCP processes. An SSE transport can also be started with a port for web application scenarios. The README documents use with Cline, Cursor, and Claude, including a Cline configuration that starts the package with uvx.

An AI client sends natural-language requests through MCP, while the server performs the corresponding Qiniu operation using the configured credentials. Examples include asking for all buckets, reading an object, changing an image to a specified width with rounded corners, refreshing a CDN URL, creating a live stream, or retrieving push and playback URLs.

Setup and configuration

qiniu/qiniu-mcp-server MCP server requires Python 3.12 or later and uv. The documented package command is uvx qiniu-mcp-server. For a local checkout, the repository can be installed in editable mode with uv pip install -e ., then launched with uv --directory . run qiniu-mcp-server.

Storage configuration uses QINIU_ACCESS_KEY and QINIU_SECRET_KEY for authentication, QINIU_REGION_NAME for the Qiniu region, QINIU_ENDPOINT_URL for the service endpoint, and QINIU_BUCKETS for a comma-separated bucket allowlist. The README recommends configuring no more than 20 buckets. Live-only usage can authenticate either with the access and secret key pair or with QINIU_LIVE_API_KEY obtained from the Qiniu live console.

When a client cannot locate uvx, its configuration may need the absolute path to that executable. The repository also includes an environment template that can be copied to .env during development.

Tools and capabilities

• List Qiniu buckets and objects.
• Upload local files or provided content.
• Read stored file content and create download links.
• Resize images and apply rounded corners.
• Refresh or prefetch files through CDN URLs.
• Create and inspect live spaces and streams.
• Bind push and playback domains and retrieve live addresses.
• Query live usage for a recent time range.

Limitations and notes

The documented storage setup depends on Qiniu region, endpoint, and bucket configuration; this is not a general-purpose storage abstraction. Live operations have a separate API-key option, but the README does not describe permissions, quotas, supported image formats, or error behavior. The SSE launch example is provided for web applications, while stdio is the default mode. Qiniu service charges and account requirements are not specified in the repository material.