Metatool App vs Watchmode
A side-by-side look at the Metatool App and Watchmode MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Metatool App for aggregators work as a local process; choose Watchmode for aggregators as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Metatool App when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Choose Watchmode when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PLATFORM_WATCHMODE_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aggregators | Aggregators |
| Quality signal | 45/100 · Fair | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | PLATFORM_WATCHMODE_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2,720 | 0 |
| Directory activity | 3 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Metatool App | View Watchmode |
Tools & capabilities
Metatool App tools
No tool names declared yet. Check the project README from the listing page.
Watchmode tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Metatool App
{
"mcpServers": {
"metatool-ai-metatool-app": {
"command": "uvx",
"args": [
"mcp-hn"
]
}
}
}
Watchmode
{
"mcpServers": {
"watchmode": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-watchmode"
],
"env": {
"PLATFORM_WATCHMODE_KEY": "YOUR_PLATFORM_WATCHMODE_KEY_HERE"
}
}
}
}
Frequently asked questions
Metatool App is categorized under Aggregators and uses a local stdio subprocess. Watchmode belongs to Aggregators and uses a local stdio subprocess. Pick Metatool App for aggregators work and Watchmode for aggregators.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Metatool App is listed as free. Auth: no auth required. Watchmode has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add metatool-ai-metatool-app and watchmode as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Metatool App has a quality signal of 45/100 (Fair) with 3 views, 0 installs and 2,720 GitHub stars. Watchmode has 43/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.