The breadth is the argument: weather, logistics, company registry data and content moderation would normally mean separate accounts, separate keys and separate integrations. Because the tools are generated from ALAPI's OpenAPI spec, the set tracks the platform rather than the repository — and the loading is selective, so you can expose only the APIs a given assistant should have. It is China-oriented data throughout.
An MCP server over ALAPI, a Chinese aggregator of everyday utility APIs. It loads ALAPI's OpenAPI specification automatically, so the tools appear without you writing any per-endpoint configuration, and you can expose all of them or only the ones you name. Responses and errors are normalised into one shape across every underlying service.
- IP geolocation for IPv4 and IPv6
- Chinese domestic weather with warnings, indices and air quality
- Today's hot lists across Douyin, Toutiao, Zhihu, 36Kr, Baidu and Weibo in one call
- Text moderation for compliance checking, which the project calls out as a fit for AI-generated content
- URL shortening, and QR and barcode recognition including several codes in one image
- Company records looked up by name or unified social credit code
- Express and logistics tracking across ZTO, STO, SF, J&T, Best and YTO
- Exchange rates and conversion across 170+ countries and regions, plus live gold prices
- Historical events for a given date, and horoscope readings by sign and period
An ALAPI account token in `ALAPI_TOKEN` — that single credential covers every API in the set. There is no standalone CLI configuration; it is designed to be launched by an MCP client. Three installation routes: a prebuilt binary from Releases for Windows, macOS or Linux (the recommended path, no dependencies), a Smithery one-liner for Claude Desktop, or a one-click deploy to Tencent CloudBase for remote SSE access.
One command plus a key — npx -y @smithery/cli install @ALAPI-SDK/mcp-alapi-cn --client claude, then supply credentials