华为云 MCP server：本地通用网关（stdio / Streamable HTTP 多会话），openapi 模式 8 工具直连华为云全量 OpenAPI，data 模式 2 工具（DataFusion 只读 SQL 分析与转换落盘）
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"huaweicloud-open-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
<div align="center"> <img src="logo.png" alt="Huawei Cloud Open MCP" width="240"/> <p><sub>English | <a href="README.zh-CN.md">中文</a></sub></p> <p> <a href="https://pypi.org/project/huaweicloud-open-mcp/"> <img src="https://img.shields.io/pypi/v/huaweicloud-open-mcp?include_prereleases=1" alt="PyPI"> </a> </p> </div> # Huawei Cloud Open MCP **Open Connect. Explore What's Next.** One open, local [Model Context Protocol](https://modelcontextprotocol.io) server connects code agents to Huawei Cloud in natural language. It works with opencode, Codex, Cursor, or any other MCP-capable client. There are no per-service wrappers. The agent explores the full catalog (300+ products, 17,000+ APIs) step by step, narrows down to one concrete API call, then executes it with a locally signed request. This is a personal, local deployment. The gateway runs entirely on your machine, and your AK/SK never leave it. Two composable modes, selected with `--mode` (comma-separated, e.g. `openapi,data`): - `openapi` (default) talks to Huawei Cloud OpenAPI. - `data` runs read-only SQL analytics and transformations over inline/local data with DataFusion, pure local compute that needs no credentials and is not governed by the safety policy. A typical `openapi,data` workflow pulls a large dataset with `execute_api`, saves it to a file, then aggregates it with `query_data` or reshapes it into a new dataset with `transform_data`. Only the aggregated results or artifact metadata enter the model context. The gateway serves stdio by default, the form your code agent launches. `--transport http` adds Streamable HTTP for multi-client deployments; see [HTTP transport](#http-transport-multi-session). ## How it works - **Progressive workflow.** The agent explores step by step: `search_apis` (entity-graph cross-product search when the intent doesn't name a product) → `list_products → get_product → list_apis → get_api → (get_api_examples) → execute_api`, narrowing 17,000+ APIs …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.