Gemini Watermark Remover

Created By
Yezery3 months ago
MCP server for removing Gemini watermarks
Overview

Gemini Watermark Remove MCP Server

MCP server for removing Gemini AI watermarks from generated images.

Local Stdio Mode

Claude Desktop

{
  "mcpServers": {
    "gemini-watermark-remove": {
      "command": "npx",
      "args": ["-y", "gemini-watermark-remover-mcp"]
    }
  }
}

OpenCode

{
  "mcp": {
    "gemini-watermark-remove": {
      "command": ["npx", "-y", "gemini-watermark-remover-mcp"],
      "type": "local",
      "enabled": true
    }
  }
}

Development

Prerequisites

  • Node.js >= 22
  • npm

Installation

# Clone or download the project
cd gemini-watermark-remover-mcp

# Install dependencies
npm install

# Build the project
npm run build

Running

Development mode (hot reload):

npm run dev

Production mode:

npm start
# or
node dist/index.js

Local Development Debug Config

For debugging after modifying source code, you can use the locally built version:

Claude Desktop:

{
  "mcpServers": {
    "gemini-watermark-remove": {
      "command": "node",
      "args": ["/path/to/gemini-watermark-remover-mcp/dist/index.js"]
    }
  }
}

MCP Tool Usage

gemini_remove_watermark

Removes the Gemini AI watermark from generated images.

Parameters:

ParameterTypeRequiredDefaultDescription
input_pathstringYes-Input image path (PNG, JPG, WEBP)
output_pathstringYes-Output image path
response_formatstringNomarkdownOutput format: markdown or json
jpeg_qualitynumberNo95JPEG quality (1-100)
webp_qualitynumberNo80WEBP quality (1-100)
png_compression_levelnumberNo6PNG compression level (0-9)

License

This project is licensed under the MIT License

Acknowledgments

This project is based on journey-ad/gemini-watermark-remover.

Thanks for the original implementation!

Server Config

{
  "mcpServers": {
    "gemini-watermark-remove": {
      "command": "npx",
      "args": [
        "-y",
        "gemini-watermark-remover-mcp"
      ]
    }
  }
}
Project Info
Created At
3 months ago
Updated At
3 months ago
Author Name
Yezery
Star
-
Language
-
License
-
Category

Recommend Servers

View All
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)

2 days ago