Dwz Mcp
@muleiwu
A short URL management client based on MCP (Model Context Protocol) protocol, providing complete short URL generation, management, and statistics functionality for AI assistants.
概要
What is Dwz Mcp?
Dwz Mcp is a short URL management MCP (Model Context Protocol) server that provides complete short URL generation, management, and statistics functionality for AI assistants. It integrates with the dwz-server backend API.
How to use Dwz Mcp?
Run npx -y @muleiwu/dwz-mcp with the required environment variables REMOTE_BASE_URL (short URL service address) and REMOTE_API_KEY (API key). Optionally install dependencies with npm install, copy .env.example to .env, and start the service with npm start or npm run dev.
Key features of Dwz Mcp
- Short URL creation with custom domains, codes, titles, and descriptions
- Batch create up to 50 short URLs at once
- Search and filter by domain or keyword with pagination
- Detailed click statistics and analytics
- Comprehensive error handling and retry mechanisms
- API authentication based on Bearer Token
Use cases of Dwz Mcp
- AI assistants generating short URLs for user-provided links
- Managing and listing existing short URLs with filters
- Deleting outdated or unused short URLs
- Batch creating multiple short URLs for bulk operations
- Retrieving domain lists and configuration information
FAQ from Dwz Mcp
What backend service does Dwz Mcp require?
Dwz Mcp requires the dwz-server, a high-performance short URL service developed in Go. It can be deployed via Docker using the provided docker-compose.yml.
How do I deploy dwz-server?
Use Docker with the image docker.cnb.cool/mliev/open/dwz-server:latest. An example docker-compose.yml is provided in the README. After starting, the API address is typically http://localhost:8080.
What environment variables are required?
REMOTE_BASE_URL and REMOTE_API_KEY are required. Optional variables include API_VERSION, REQUEST_TIMEOUT, MAX_RETRIES, and LOG_LEVEL.
What is the API response format?
All responses follow a unified JSON format: {"success": true/false, "message": "...", "data": {...}, "meta": {...}} for success, or {"success": false, "error": {"code": "...", "message": "...", "details": {...}}} for errors.
