WenElevating.MapMcpServer

WenElevating.MapMcpServer is a MVC-based MCP service that integrates the Gaode (Amap) Map API to provide a set of location and routing features. Before starting, ensure you have a Gaode Map API key and set it in the environment variable GaoDeMapKey. The server is intended to be started via the MCP mechanism by running the configured command, which in this case uses dotnet to run the project. Once running, the MCP framework will expose a set of supported amap APIs through the MCP interface, including geolocation, weather for a city, geocoding, routing (pedestrian, bus, driving, cycling), distance measurement, and keyword search. To use these capabilities, clients interact with the MCP server named map and the corresponding tool endpoints that the MCP service wires up from the Gaode Map API integration. The README example demonstrates the server being started by invoking dotnet run with a specific project, enabling the tool to respond to requests via the MCP context.

Prerequisites:

• .NET SDK installed on your machine.
• A GaoDe (Gaode) Map API key.
• Access to a suitable project path referenced as the --project argument (in this example, 'project position').

Step-by-step:

1. Set your Gaode API key in the environment:
   • On Windows: set GaoDeMapKey=your_api_key in System Environment Variables.
   • On macOS/Linux: export GaoDeMapKey=your_api_key in your shell profile.
2. Create or update the MCP configuration file (e.g., mcp_config.json) with the content provided in the mcp_config section, ensuring the key name matches GaoDeMapKey and the project path matches your solution: { "mcpServers": { "map": { "command": "dotnet", "args": [ "run", "--project", "project position", "--no-build" ], "env": { "GaoDeMapKey": "Your GaoDe API key" } } } }
3. Place the configuration file where your MCP runner expects it (per your MCP setup guidance).
4. Start the MCP server using the configured command, for example by launching the command shown in the mcp_config (dotnet run --project "project position" --no-build).
5. Verify the server is reachable through the MCP host and begin issuing requests to the supported amap APIs (location, weather, geocoding, pedestrian/bus/driving/cycling routes, distance, keyword search).

Tips and common issues:

• Ensure the GaoDeMapKey environment variable is set before starting the service; without it, API calls will fail.
• The example shows a specific --project path ("project position"); replace this with your actual project path or solution structure.
• If you update the API key or environment variables, restart the MCP server to apply changes.
• The supported amap APIs include IP geolocation, city weather, geocoding, pedestrian/bus/driving/cycling route planning, distance measurement, and keyword search. Ensure you have appropriate permissions and quota for the Gaode Map API.
• If the server fails to start, check that the .NET project builds successfully with --no-build or remove it if you want a full build first. Ensure the MCP runner has network access to Gaode services.
• Port conflicts or firewall rules may prevent the MCP endpoint from being reachable; verify network connectivity for the host running the server.