netpascal-mcp-tools
# netpascal-mcp-tools
MCP (Model Context Protocol) server providing tools for web automation and utilities.
## MCP Server Configuration
This MCP server can be run directly from GitHub without publishing to npm using `npx`.
### Generic Configuration (Command Array)
```json
"mcp": {
"netpascal": {
"type": "local",
"command": ["npx", "-y", "github:PascalNoisette/mcp-tools"],
"env": {
"CAMOFOX_URL": "http://youcamofox",
"CAMOFOX_API_KEY": "yourkey"
}
}
}
```
## Tools
### netpascal_camofox_save_screenshot
Take a screenshot of a Camofox browser tab and save it directly to a local file. Better than a simple camofox_screenshot to write to file directly and save tokens.
| Variable | Description | Example |
|--------------------|-----------------------|--------------------|
| `CAMOFOX_URL` | Camofox server URL | `http://youcamofox`|
| `CAMOFOX_API_KEY` | Camofox API key | `yourkey` |
Require a Camofox stackTDQS
Scored across 2 tools
The two tools have completely unrelated purposes: one is a simple greeting utility, the other is a browser screenshot capture. No overlap or ambiguity between them.
Naming shows no consistent pattern: 'greet' uses a bare verb, while 'camofox_save_screenshot' uses a prefix plus verb_noun with camelCase. The inconsistent verbosity and casing make the set feel disjointed.
With only two tools, the server feels extremely thin. One is trivial ('greet') and the other seems more domain-specific (Camofox), leaving no coherent purpose or breadth. A useful server would typically have more tools to justify its existence.
The tool set is severely incomplete. There is no discernible domain coverage: 'greet' is a one-off, and 'camofox_save_screenshot' covers only a single action in an undefined context, lacking any related operations like listing tabs, capturing to buffer, or managing files.