Dwz Mcp

Created By
muleiwu7 months ago
A short URL management client based on MCP (Model Context Protocol) protocol, providing complete short URL generation, management, and statistics functionality for AI assistants.
Overview

what is Dwz Mcp?

Dwz Mcp is a short URL management client based on the Model Context Protocol (MCP), designed to provide complete short URL generation, management, and statistics functionality for AI assistants.

how to use Dwz Mcp?

To use Dwz Mcp, deploy the dwz-server using Docker, configure the environment variables, and run the MCP client with the necessary commands to create and manage short URLs.

key features of Dwz Mcp?

  • 🔗 Short URL Creation: Supports custom domains, short codes, titles, and descriptions.
  • 📋 Batch Operations: Create multiple short URLs at once to improve efficiency.
  • 🔍 Search & Filter: Domain filtering and keyword search capabilities.
  • 📊 Statistics & Analytics: Detailed click statistics information.
  • 🛡️ Error Handling: Comprehensive error handling and retry mechanisms.
  • 🔒 Security Authentication: API authentication based on Bearer Token.

use cases of Dwz Mcp?

  1. Managing short URLs for marketing campaigns.
  2. Analyzing click statistics for user engagement.
  3. Integrating short URL functionality into AI applications.

FAQ from Dwz Mcp?

  • Can Dwz Mcp handle multiple short URLs at once?

Yes! It supports batch operations for creating multiple short URLs.

  • Is there a specific server requirement for Dwz Mcp?

Yes, it is recommended to deploy the dwz-server using Docker for optimal performance.

  • How do I configure the environment variables?

You can configure the environment variables in the .env file after copying the template provided.

Server Config

{
  "mcpServers": {
    "dwz-mcp": {
      "name": "dwz-mcp",
      "type": "stdio",
      "isActive": true,
      "registryUrl": "",
      "command": "npx",
      "args": [
        "-y",
        "@muleiwu/dwz-mcp"
      ],
      "env": {
        "REMOTE_BASE_URL": "Your short URL service address",
        "REMOTE_API_KEY": "apiKey"
      }
    }
  }
}
Project Info
Created At
7 months ago
Updated At
7 months ago
Author Name
muleiwu
Star
-
Language
-
License
-

Recommend Servers

View All
Crevio

a day ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

19 hours ago