watermarkbuster-mcp 1.0.0 → 1.0.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +104 -15
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # Watermark Buster MCP
2
2
 
3
- Connect a local MCP client to the hosted Watermark Buster tools. The package is a bridge. It does not run the cleaning engine on your computer.
3
+ Connect an MCP client to the hosted Watermark Buster tools. This package is a local stdio bridge. It does not run the cleaning engine on your computer.
4
4
 
5
5
  ## Requirements
6
6
 
@@ -9,7 +9,37 @@ Connect a local MCP client to the hosted Watermark Buster tools. The package is
9
9
 
10
10
  No account, API token, GPU, Python, or local model is required.
11
11
 
12
- ## Use with `npx`
12
+ ## Run without installing
13
+
14
+ Use `npx` to download and start the current package:
15
+
16
+ ```bash
17
+ npx -y watermarkbuster-mcp
18
+ ```
19
+
20
+ The command waits for MCP messages on standard input. It does not open a user interface or show a prompt. Normally, your MCP client starts this command for you.
21
+
22
+ ## Install the command
23
+
24
+ Install the command on your computer:
25
+
26
+ ```bash
27
+ npm install --global watermarkbuster-mcp
28
+ ```
29
+
30
+ Your MCP client can then start:
31
+
32
+ ```text
33
+ watermarkbuster-mcp
34
+ ```
35
+
36
+ To add the package to one Node.js project instead, run:
37
+
38
+ ```bash
39
+ npm install watermarkbuster-mcp
40
+ ```
41
+
42
+ ## Add the npx bridge to an MCP client
13
43
 
14
44
  Set these values in your MCP client:
15
45
 
@@ -18,7 +48,7 @@ Command: npx
18
48
  Arguments: -y watermarkbuster-mcp
19
49
  ```
20
50
 
21
- For clients that use an `mcpServers` JSON object, the matching form is:
51
+ Clients that use an `mcpServers` JSON object commonly use this form:
22
52
 
23
53
  ```json
24
54
  {
@@ -31,39 +61,98 @@ For clients that use an `mcpServers` JSON object, the matching form is:
31
61
  }
32
62
  ```
33
63
 
34
- The MCP client starts the command. Running it in a normal terminal shows no user interface because it waits for MCP messages on standard input.
64
+ ## Connect directly to the remote server
65
+
66
+ Clients that support remote Streamable HTTP MCP do not need this npm bridge. Connect them directly to:
67
+
68
+ ```text
69
+ https://watermarkbuster.com/mcp
70
+ ```
71
+
72
+ ### Codex
73
+
74
+ Add this to `~/.codex/config.toml`:
75
+
76
+ ```toml
77
+ [mcp_servers.watermark_buster]
78
+ url = "https://watermarkbuster.com/mcp"
79
+ ```
80
+
81
+ Restart Codex, then run `codex mcp list` or use `/mcp` inside Codex.
35
82
 
36
- ## Install first
83
+ ### Claude Code
37
84
 
38
85
  ```bash
39
- npm install --global watermarkbuster-mcp
86
+ claude mcp add --transport http watermark-buster https://watermarkbuster.com/mcp
40
87
  ```
41
88
 
42
- Then set the MCP command to:
89
+ Run `claude mcp list` or use `/mcp` inside Claude Code.
43
90
 
44
- ```text
45
- watermarkbuster-mcp
91
+ ### Gemini CLI
92
+
93
+ ```bash
94
+ gemini mcp add --transport http watermark-buster https://watermarkbuster.com/mcp
95
+ ```
96
+
97
+ Run `gemini mcp list` to confirm the connection.
98
+
99
+ ### Cursor
100
+
101
+ Add this to `.cursor/mcp.json` for one project or `~/.cursor/mcp.json` for all projects:
102
+
103
+ ```json
104
+ {
105
+ "mcpServers": {
106
+ "watermark-buster": {
107
+ "url": "https://watermarkbuster.com/mcp"
108
+ }
109
+ }
110
+ }
111
+ ```
112
+
113
+ Open Cursor's Customize sidebar, select MCP, and confirm that the server is enabled.
114
+
115
+ ### Google Antigravity
116
+
117
+ Add this to `~/.gemini/config/mcp_config.json` for all workspaces or `.agents/mcp_config.json` for one workspace:
118
+
119
+ ```json
120
+ {
121
+ "mcpServers": {
122
+ "watermark-buster": {
123
+ "serverUrl": "https://watermarkbuster.com/mcp"
124
+ }
125
+ }
126
+ }
46
127
  ```
47
128
 
129
+ Save the file, then refresh Installed MCP Servers.
130
+
48
131
  ## Tools
49
132
 
50
133
  The bridge reads the current tool list from the hosted MCP server when it starts. The current tools are:
51
134
 
52
- - `inspect_text`
53
- - `clean_text`
54
- - `clean_file`
55
- - `get_capabilities`
135
+ - `inspect_text` — report supported hidden Unicode without changing the text
136
+ - `clean_text` — remove supported hidden Unicode and exotic spaces
137
+ - `clean_file` — clean a supported file and return the cleaned copy
138
+ - `get_capabilities` — read the current formats, limits, and behavior
139
+
140
+ Example agent requests:
141
+
142
+ - “Inspect this text for hidden Unicode.”
143
+ - “Clean this file and return the cleaned copy.”
144
+ - “Show the current Watermark Buster capabilities.”
56
145
 
57
146
  ## Data flow
58
147
 
59
148
  Tool input is sent to `https://watermarkbuster.com` for processing. The hosted service processes content for the call and does not archive it. Do not use this npm bridge if content must stay on your computer.
60
149
 
61
- For clients that support remote Streamable HTTP MCP, connect directly to `https://watermarkbuster.com/mcp` instead.
62
-
63
150
  ## Connection errors
64
151
 
65
152
  If the hosted service cannot be reached, the command writes `Watermark Buster MCP: <reason>` to standard error and exits with a failure status. Check that `https://watermarkbuster.com/mcp` is reachable, then let the MCP client start the command again.
66
153
 
154
+ For more setup help, see [the full MCP guide](https://watermarkbuster.com/mcp).
155
+
67
156
  ## License
68
157
 
69
158
  MIT
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "watermarkbuster-mcp",
3
- "version": "1.0.0",
3
+ "version": "1.0.1",
4
4
  "description": "Connect local MCP clients to the hosted Watermark Buster tools.",
5
5
  "type": "module",
6
6
  "bin": {