awesome -cn
A collection of MCP servers for mainland China services. 支持 MCP 的国内服务一览。
claude mcp add --transport stdio leslieleung-awesome-mcp-server-cn node path/to/server.js \ --env MCP_SERVER_NAME="Awesome MCP Server CN - placeholder" \ --env MCP_REGISTRY_URL="https://example.com/mcp-registry"
How to use
Awesome MCP Server CN aggregates MCP implementations for common domestic services. It is intended to provide a centralized API surface to fetch MCP-compatible data such as maps, weather, and other localized endpoints. After starting the server, you can query the MCP endpoints described in its API surface to retrieve service-specific data (e.g., geolocation helpers, weather data, and regional service proxies) in a consistent MCP protocol format. The available endpoints mirror the domestic services listed in the project, and you can integrate them into your applications with standard MCP requests and responses. If you are building client apps, you can rely on the MCP schema to parse responses uniformly across supported services, and you can extend the server by adding additional service implementations following the MCP conventions used by this repository.
How to install
Prerequisites:
- Node.js (LTS version) or a compatible runtime for the chosen deployment method
- Git to clone the repository (if you intend to customize)
- Access to the internet to install dependencies
Installation steps:
-
Clone the repository (or download the source): git clone https://github.com/leslieleung-awesome-mcp-server-cn.git cd leslieleung-awesome-mcp-server-cn
-
Install dependencies: npm install
-
Configure environment variables (example):
- Create a .env file or export variables in your shell MCP_SERVER_NAME=Awesome MCP Server CN MCP_REGISTRY_URL=https://example.com/mcp-registry
-
Start the server: npm start
-
Verify the server is running by hitting the MCP endpoint (e.g., http://localhost:3000/mcp/status) and check the logs for any startup messages.
Note: If the project uses a different launch script or additional build steps, follow the repository-specific README or build scripts accordingly.
Additional notes
Tips and caveats:
- The server is designed to cover domestic services; if a service is not yet implemented, you may need to add a new MCP module following the existing project structure.
- Ensure your environment provides network access to the upstream services the MCP server proxies.
- Monitor logs for any rate limiting or API changes from upstream services, especially for widely used Chinese services.
- If you run into port conflicts, adjust the server port in your configuration or environment variables.
- Security: limit access to the MCP endpoints in production and consider adding authentication if exposing to public networks.
- Environment variables can be extended to control per-service behavior, timeouts, and caching policies.