Edaijiamcp Project

🚀 E-Daijia MCP Service

An MCP (Model Context Protocol) service based on E-Daijia's open API, offering comprehensive features for chauffeur services.

🚀 Quick Start

Environment Configuration

1. Create an environment variable file: Copy the .env.example file to .env:

   cp .env.example .env
   

2. Configure the API key: Set your API key in the .env file:

   APP_KEY=your_app_key_here
   SECRET=your_secret_here
   API_BASE_URL=https://openapi.d.edaijia.cn
   

   ⚠️ Important Note

   The .env file contains sensitive information and has been added to .gitignore, so it will not be committed to the version control system.

Running the Service

python edaijiamcp.py

✨ Features

• Cost Estimation: Estimate chauffeur service costs based on the starting and ending locations.
• Chauffeur Ordering: Create chauffeur orders with automatic token management support.
• Token Management: Intelligent token acquisition, storage, and refresh mechanism.
• Automatic Retry: Automatically refresh the token and retry operations when the token expires.
• Parameter Validation: Comprehensive input parameter validation and error handling.

📦 Installation

This service has the following dependencies:

• mcp: Model Context Protocol library
• requests: HTTP request library
• python-dotenv: Environment variable management
• uuid: Unique identifier generation
• time: Timestamp generation
• json: JSON data processing
• os: File system operations

💻 Usage Examples

Available Tools

1. estimate_cost

Estimate the chauffeur service cost.

• Parameters:
  • start_address: Starting address
  • start_longitude: Starting longitude
  • start_latitude: Starting latitude
  • end_address: Destination address
  • end_longitude: Destination longitude
  • end_latitude: Destination latitude
  • phone: User's mobile phone number (11 digits)
• Return: Estimated cost information, including distance, time, and price.
• Features: Automatically checks and refreshes the token, supports retry on token expiration.

2. call_driver

Place a chauffeur order.

• Parameters:
  • start_address: Starting address
  • start_longitude: Starting longitude
  • start_latitude: Starting latitude
  • end_address: Destination address
  • end_longitude: Destination longitude
  • end_latitude: Destination latitude
  • phone: User's mobile phone number (11 digits)
  • contact_phone: Contact phone number (optional, required for orders placed on behalf of others)
• Return: Order placement result, including the order number and status.
• Features: Automatically generates a unique order number, supports retry on token verification failure.

3. refresh_token

Refresh the user's token.

• Parameters:
  • phone: User's mobile phone number (11 digits)
• Return: Token refresh result and status.
• Features: Manually refreshes the authentication token for the specified mobile phone number.

Usage Process

1. Cost Estimation: Use estimate_cost to provide the starting and ending location information and the mobile phone number to get the estimated price.
2. Confirm Order Placement: Use call_driver to provide the same information to place an order.
3. Token Management: If necessary, use refresh_token to manually refresh the token.

🔧 Technical Details

• Intelligent Retry: Automatically handles token-related errors without manual intervention.
• Parameter Validation: Comprehensive input validation to ensure correct data formats.
• Error Handling: Returns detailed error information for easy problem location.
• Unique Order Number: Generates a unique order identifier based on timestamps and UUIDs.

📚 Documentation

Token Management Mechanism

• Automatic Detection: The system automatically checks if a token for the corresponding mobile phone number exists locally.
• Intelligent Acquisition: If there is no local token, it automatically calls the API to obtain a new token.
• Local Storage: Tokens are automatically saved to the edjserver/tokens/ directory.
• Expiration Handling: Automatically refreshes and retries when the API returns a token expiration error.
• Verification Retry: Automatically refreshes the token and re - executes the operation when token verification fails.

Project Structure

edaijiamcp/
├── edaijiamcp.py          # MCP service main file
├── edjserver/             # E-Daijia API encapsulation
│   ├── EdjApi.py         # Main API interfaces
│   ├── EdjSignUtils.py   # Signature tools
│   ├── EdjSystemParams.py # System parameters
│   └── tokens/           # Token storage directory
├── README.md             # Project documentation
└── pyproject.toml        # Project configuration