MCP server that enables AI assistants to manage Tampermonkey userscripts via the Tampermonkey Editors browser extension, including listing, reading, creating, updating, and deleting scripts
Installation and connection instructions are shown only when supported by retained package, repository, or endpoint evidence.
Version 0.0.5 declares 1 executable entrypoint.
npm install --save-exact tampermonkey-mcp@0.0.5npx -y -p tampermonkey-mcp@0.0.5 tampermonkey-mcp{
"mcpServers": {
"tampermonkey-mcp": {
"command": "npx",
"args": [
"-y",
"-p",
"tampermonkey-mcp@0.0.5",
"tampermonkey-mcp"
]
}
}
}| Canonical slug | tampermonkey-mcp-dd9ad1fe | Deployment | Local Only |
|---|---|---|---|
| Canonical package | npm:tampermonkey-mcp | Repository | Tampermonkey/tampermonkey-mcp |
| First published | — | Latest release | — |
| Last security verification | Aug 20, 2026 | Classification confidence | 90% |
| Publication | Published | Official distribution | Yes |
| Channel | Identifier | Current version | Versions | Source |
|---|---|---|---|---|
| npm | tampermonkey-mcp | 0.0.5 | 5 | Repository |
| Package | Version | Published / observed | Inventory | Security scan |
|---|---|---|---|---|
| npmtampermonkey-mcp | 0.0.5Current | Sep 5, 2026 | 6 toolsSucceeded · 0 resources · 0 prompts | Failed |
Independently scan the exact version your agents use, receive alerts when its risk changes, and investigate every finding with retained version evidence.
| Provenance | artifact_hash_verified | Signature | — |
|---|---|---|---|
| MCP SDK | @modelcontextprotocol/sdk | Artifact SHA-256 | 55ec5265b88a0079f8ad60f70971546168da01f35d6e9a6dac2218f7b87dad90 |
| Scanner | mcp-proof-engine 0.1.0 | Scan completed | Aug 20, 2026 |
| Security rating | 41 / 100 | Methodology | version-rating-1.0 |
[ "tampermonkey-mcp" ]
[ "security_policy_not_observed" ]
| Tool | Category | Annotations | Risk |
|---|---|---|---|
tampermonkey_delete
Delete a userscript by path.
**Input:**
- `path`: The script or resource path (<script-uuid>/source, <script-uuid>/storage or <script-uuid>/<external-resource-url>)
**Output:**
- `success`: true if script was deleted successfully
- `error`: Error object if deletion failed (e.g., script not found)
Input schema{
"$schema": "http://json-schema.org/draft-07/schema#",
"type": "object",
"properties": {
"path": {
"type": "string",
"description": "The script or resource path (<script-uuid>/source, <script-uuid>/storage or <script-uuid>/<external-resource-url>)"
}
},
"required": [
"path"
]
} | — | — | |
tampermonkey_get
Get the content of a specific userscript.
**Input:**
- `path`: The script path (from list operation)
- `ifNotModifiedSince` (optional): Unix timestamp - only return if script was modified after this time
**Output:**
- `value`: The script source code
- `lastModified`: Unix timestamp of last modification
- `error`: Error object if script not found or concurrent edit detected
Input schema{
"$schema": "http://json-schema.org/draft-07/schema#",
"type": "object",
"properties": {
"path": {
"type": "string",
"description": "The script or resource path (<script-uuid>/source, <script-uuid>/storage or <script-uuid>/<external-resource-url>"
},
"ifNotModifiedSince": {
"description": "Unix timestamp - only return if script was modified after this time",
"type": "number"
}
},
"required": [
"path"
]
} | — | — | |
tampermonkey_get_connection_code
REQUIRED FIRST STEP: Get the connection code to connect Tampermonkey Editors to the MCP server.
**How it works:**
The MCP server creates a WebSocket server that waits for Tampermonkey Editors to connect.
You must call this tool FIRST to start the WebSocket server and get a connection code.
Then enter the code in the Tampermonkey Editors extension - it will connect TO the MCP server.
**Steps:**
1. Call this tool to get the connection code
2. Open Tampermonkey Editors extension in your browser
3. Enter the code in the extension popup
4. The extension connects to the MCP server's WebSocket
5. After connection, you can use tampermonkey_list, tampermonkey_get, tampermonkey_patch, tampermonkey_put, tampermonkey_delete
**Output:**
- `code`: The connection code to enter in Tampermonkey Editors
Input schema{
"$schema": "http://json-schema.org/draft-07/schema#",
"type": "object",
"properties": {}
} | — | — | |
tampermonkey_list
List all userscripts available in Tampermonkey.
**Input:**
- `pattern` (optional): Filter scripts by name pattern
- `includePattern` (optional): Filter scripts by include URL pattern
**Output:**
Array of userscript metadata including:
- `name`: Script name
- `namespace`: Script namespace
- `path`: Script path (used for get/patch operations)
- `requires`: List of @require dependencies
- `storage`: Storage path (if any)
Input schema{
"$schema": "http://json-schema.org/draft-07/schema#",
"type": "object",
"properties": {
"pattern": {
"description": "Filter scripts by name pattern",
"type": "string"
},
"includePattern": {
"description": "Filter scripts by include URL pattern",
"type": "array",
"items": {
"type": "string"
}
}
}
} | — | — | |
tampermonkey_patch
Update the content of a userscript.
**Input:**
- `path`: The script or resource path (from list operation)
- `value`: The new script content
- `lastModified` (optional): Unix timestamp for optimistic locking
**Output:**
- `success`: true if patch was applied successfully
- `error`: Error object if patch failed (e.g., concurrent edit conflict)
Input schema{
"$schema": "http://json-schema.org/draft-07/schema#",
"type": "object",
"properties": {
"path": {
"type": "string",
"description": "The script path (e.g., \"<script-uuid>/source\")"
},
"value": {
"type": "string",
"description": "The new script content"
},
"lastModified": {
"description": "Unix timestamp for optimistic locking",
"type": "number"
}
},
"required": [
"path",
"value"
]
} | — | — | |
tampermonkey_put
Create a new userscript.
**Input:**
- `value`: The script source code content
- `lastModified` (optional): Unix timestamp for optimistic locking
**Output:**
- `success`: true if script was created successfully
- `path/name`: The path and name of the new script
- `error`: Error object if creation failed (e.g., script already exists, concurrent edit conflict)
Input schema{
"$schema": "http://json-schema.org/draft-07/schema#",
"type": "object",
"properties": {
"value": {
"type": "string",
"description": "The script source code content"
},
"lastModified": {
"description": "Unix timestamp for optimistic locking",
"type": "number"
}
},
"required": [
"value"
]
} | — | — |
| Endpoint | Transport | Authentication | Health | Observed |
|---|---|---|---|---|
| No verified remote endpoint is linked. | ||||
Install the selected package version with: npm install --save-exact tampermonkey-mcp@0.0.5
tampermonkey-mcp Server exposed 6 tools during independent protocol observation, including tampermonkey_delete, tampermonkey_get, tampermonkey_get_connection_code, tampermonkey_list, tampermonkey_patch, tampermonkey_put.
Our scanner tested version 0.0.5 without proving a finding in the methods exercised. This is not a guarantee that every deployment is secure.
Curated product and capability guides containing this catalog record.