Watermark MCP Server

Created By
mang0colaa year ago
Overview

what is Watermark MCP Server?

Watermark MCP Server is a simple Model Context Protocol (MCP) server designed to add text or image watermarks to pictures.

how to use Watermark MCP Server?

To use the Watermark MCP Server, clone the repository from GitHub, set up a virtual environment, and install the required dependencies. Then, configure the server in your MCP client with the appropriate command and arguments.

key features of Watermark MCP Server?

  • Add text watermarks to images with customizable options (font, size, color, transparency).
  • Add image watermarks to pictures with adjustable transparency and position.
  • Easy integration with MCP clients like Claude and CherryStudio.

use cases of Watermark MCP Server?

  1. Adding branding to images for marketing purposes.
  2. Protecting digital artwork by overlaying watermarks.
  3. Customizing images for personal or professional use with personalized watermarks.

FAQ from Watermark MCP Server?

  • Can I use any font for text watermarks?

Yes, you can specify the path to any font file you wish to use.

  • Is there a limit to the size of the watermark image?

No, but ensure that the watermark image is appropriately sized for the best visual results.

  • How do I run the server?

Use the provided command in your MCP client configuration to run the server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mang0cola
Star
0
Language
Python
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago