mcp-alapi-cn

This MCP server provides access to ALAPI's extensive API resources through the Model Context Protocol (MCP). It enables MCP-compatible clients (such as Claude Desktop, Claude Code, Cursor, Continue, Cline, and other MCP-enabled tools) to invoke a wide range of ALAPI services via a standardized MCP interface, including IP lookup, weather data, hot lists, business information, logistics tracking, and more. The server leverages ALAPI's OpenAPI specifications to automatically load available APIs and exposes them in a uniform MCP response format with centralized error handling. To use it, configure your MCP client to point at the server and ensure you supply the necessary authentication token when required.

Usage typically involves installing the MCP server (via Smithery or a prebuilt binary) and then configuring your MCP client with the server details. Once connected, you can call ALAPI endpoints by name through the MCP protocol, enabling seamless integration of dozens of APIs into your AI workflows without modifying code for each individual API.

Prerequisites:

• Node.js installed (for npx-based installation)
• Access to the internet to fetch packages
• An ALAPI access token (ALAPI_TOKEN) for authenticated endpoints

Installation steps (via Smithery host approach):

1. Install Smithery CLI and the MCP ALAPI CN server:

npx -y @smithery/cli install @ALAPI-SDK/mcp-alapi-cn --client claude

2. Set the required environment variable (token) when launching the server or configuring the client:

export ALAPI_TOKEN=YOUR_ALAPI_TOKEN

3. Run or configure the MCP client to connect to the installed server as per your client’s MCP setup instructions. If you’re using a remote deployment, follow the CloudBase MCP hosting steps as described in the README.

Alternative (prebuilt binaries):

• Visit the Releases page and download the appropriate binary for your OS (Windows, macOS, Linux).
• Place the binary somewhere accessible and run it in your MCP client configuration, ensuring ALAPI_TOKEN is provided in the environment.

# Example (Linux/macOS):
chmod +x mcp-alapi-cn-linux
export ALAPI_TOKEN=YOUR_ALAPI_TOKEN
./mcp-alapi-cn-linux

Tips and common issues:

• Ensure ALAPI_TOKEN is set in the environment where the MCP server runs, otherwise API calls may fail due to missing authentication.
• If you plan to run this server in a container or cloud environment, persist the ALAPI_TOKEN securely (e.g., environment secrets) and avoid hard-coding it.
• The server automatically loads ALAPI OpenAPI specifications, but if you notice missing APIs, verify network access to ALAPI and ensure you are using a compatible MCP client version.
• When using remote hosting or cloud services, refer to the MCP client documentation for the exact JSON snippet to register the ALAPI MCP server in your client configuration.
• The provided npm package name for this server is used with the Smithery flow; if you prefer direct binary usage, the binary approach is also supported as described in installation steps.