AWS S3 Pre-Signed URL MCP
OpenWorkspace-o1LABSCO SUMMARY
Vendor-maintained coverage of the Huawei Cloud catalogue, split so you only load the service you need.
Running one server per product is the design choice that matters here: an agent working on ECS never sees the WAF tools, which keeps the tool list — and the context it costs — proportional to the job. The credentials are account-level access keys, so scope them at IAM before you point anything at production.
What it is
Huawei Cloud's own collection of MCP servers, one per product: you launch the service you need, such as mcp-server-ecs, and it exposes that service's operations.
What you get
- Compute and storage — Elastic Cloud Server, Bare Metal Server, Auto Scaling, FunctionGraph, Object Storage Service, Elastic Volume Service, Cloud Backup and Recovery
- Networking — Elastic Load Balance, Virtual Private Cloud, Elastic IP, NAT Gateway, VPC Endpoint, Enterprise Router, Direct Connect, Virtual Private Network
- Databases — Relational Database Service, GaussDB, TaurusDB, GeminiDB, Document Database Service, Data Replication Service, Data Admin Service
- Containers — Cloud Container Engine, Cloud Container Instance, SoftWare Repository for Container, Application Service Mesh
- Data and AI — MapReduce Service, Data Warehouse Service, Data Lake Insight, ModelArts, Optical Character Recognition, Speech Interaction Service, Graph Engine Service
- Operations and security — Identity and Access Management, Cloud Eye, Log Tank Service, Cloud Trace Service, Web Application Firewall, Host Security Service, Key Management
- CodeArts across the delivery chain — Req, Build, Check, Deploy, Pipeline, Artifact and CloudTest
Requirements
A Huawei Cloud access key and secret key, set as HUAWEI_ACCESS_KEY and HUAWEI_SECRET_KEY. Python 3.10 or above, and uv for the recommended launch path. Each service starts as its own process — uv run mcp-server-ecs, for example — and takes -t to choose http, sse or stdio and -p to set the port, overriding the sub-project's config.yaml.
Setup effort
Build from source — git clone https://github.com/huaweicloud-samples/iaas-mcp-server.git
USE CASES
01
Managing compute instances from the conversation
Start the ECS server and work with instances in the same thread you are diagnosing in.
02
Handling elastic IPs without opening the console
Launch the EIP server and create or release addresses through the assistant.
03
Doing database operations conversationally
Run the RDS, GaussDB or DAS server and query and administer from the client.
04
Keeping the tool list small
Launch only the service you are working on rather than exposing the whole cloud catalogue at once.
05
Connecting it to a client that only speaks HTTP
Start the service with -t http and a port, then point the client at the endpoint.
BEFORE YOU INSTALL
What to know first
Requires
- HUAWEI_ACCESS_KEY in your environment
- HUAWEI_SECRET_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
This one is built from source rather than installed with a single command.
Server setup
TERMINAL
git clone https://github.com/huaweicloud-samples/iaas-mcp-server.git
cd iaas-mcp-serverSet your access key and secret key as the environment variables HUAWEI_ACCESS_KEY and HUAWEI_SECRET_KEY in this shell, then start the service from the project root. This starts the ECS server; each product has its own mcp-server-<YOUR_SERVICE> command, and its config.yaml defaults to HTTP on port 8888:
TERMINAL
uv run mcp-server-ecsMCP Clients
Cline
CLINE · JSON
{
"mcpServers": {
"mcp_server_ecs": {
"url": "http://localhost:8888/mcp",
"disabled": false,
"type": "streamableHttp",
"autoApprove": []
}
}
}Set your access key and secret key (AK and SK) as the environment variables HUAWEI_ACCESS_KEY and HUAWEI_SECRET_KEY in the shell where you start the server (uv run mcp-server-ecs, from the project root). The Cline configuration only points at http://localhost:8888/mcp.
