Content
# What is SSE?
Server-Sent Events (SSE) is a technology based on the HTTP protocol that allows servers to push data to clients in a one-way, real-time manner. In SSE mode, developers can establish a persistent connection with the server by creating an EventSource object on the client side. The server continuously sends data streams through this connection without the need for the client to repeatedly send requests.
## Product Features
- **Easy to Use**: Suitable for ordinary users based on MCP (SSE) mode, no need to deploy local services, and can be easily used by configuring a URL.
- **Automatic Upgrades**: We will continue to iterate and update without requiring any additional actions from users.
- **Easier for Large Models to Understand**: We have semantically transformed the original JSON results, making it easier for large models to comprehend the content.
- **Zero Operational Cost**: Utilizing a fully managed cloud service architecture, users do not need to worry about server maintenance, resource scaling, and other underlying operational issues.
- **Protocol Compatibility**: Supports SSE long connections, adapting to the technical needs of different business scenarios.
Visit the **Quick Access** documentation to learn how to connect to the MCP Server SSE service.
## Capability Introduction
1. **Geocoding**
Converts detailed structured addresses into latitude and longitude coordinates.
Input: `address` (location information), `city` (city information, optional)
Output: `location` (latitude and longitude)
2. **Reverse Geocoding**
Converts a Gaode latitude and longitude coordinate into administrative district address information.
Input: `location` (latitude and longitude)
Output: `addressComponent` (location information, including province, city, district, etc.)
3. **IP Location**
Locates the position of an IP address based on the user-provided IP.
Input: `IP`
Output: `province` (province), `city` (city), `adcode` (city code)
4. **Weather Query**
Queries the weather for a specified city based on the city name or standard adcode.
Input: `city` (city name or city adcode)
Output: `forecasts` (forecast weather)
5. **Biking Route Planning**
Used to plan biking commuting solutions, considering factors such as overpasses, one-way streets, and road closures. Supports biking route planning up to 500km.
Input: `origin` (starting latitude and longitude), `destination` (ending latitude and longitude)
Output: `distance` (planned distance), `duration` (planned time), `steps` (planning step information)
6. **Walking Route Planning**
Can plan walking commuting solutions within 100km based on input starting and ending latitude and longitude coordinates, and return the commuting plan data.
Input: `origin` (starting latitude and longitude), `destination` (ending latitude and longitude)
Output: `origin` (starting information), `destination` (ending information), `paths` (planning details)
7. **Driving Route Planning**
Plans commuting solutions for small cars based on user-provided starting and ending latitude and longitude coordinates, and returns the commuting plan data.
Input: `origin` (starting latitude and longitude), `destination` (ending latitude and longitude)
Output: `origin` (starting information), `destination` (ending information), `paths` (planning details)
8. **Public Transport Route Planning**
Plans commuting solutions that integrate various public transport modes (train, bus, subway) based on user-provided starting and ending latitude and longitude coordinates, and returns the commuting plan data. In cross-city scenarios, both starting and ending cities must be provided.
Input: `origin` (starting latitude and longitude), `destination` (ending latitude and longitude), `city` (starting city), `cityd` (ending city)
Output: `origin` (starting information), `destination` (ending information), `distance` (planned distance), `transits` (planning details)
9. **Distance Measurement**
Measures the distance between two latitude and longitude coordinates.
Input: `origin` (starting latitude and longitude), `destination` (ending latitude and longitude)
Output: `origin_id` (starting information), `dest_id` (ending information), `distance` (planned distance), `duration` (time)
10. **Keyword Search**
Searches for relevant POI (Point of Interest) information based on user-provided keywords.
Input: `keywords` (search keywords), `city` (query city, optional)
Output: `suggestion` (search suggestions), `pois` (list of location information)
11. **Nearby Search**
Searches for POI information within a radius based on user-provided keywords and coordinates.
Input: `keywords` (search keywords), `location` (central point latitude and longitude), `radius` (search radius, optional)
Output: `pois` (list of location information)
12. **Detail Search**
Queries detailed information of a POI ID obtained from keyword search or nearby search.
Input: `id` (POI ID obtained from keyword search or nearby search)
Output: Location details, `location` (latitude and longitude), `address`, `business_area`, `city`, `type` (location type), etc.
