Webclaw vs Perenna
A side-by-side look at the Webclaw and Perenna MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Webclaw for other tools and integrations work as a local process; choose Perenna for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Webclaw when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
scrape, crawl, map.
Choose Perenna when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
VEXOR_CONFIG_JSON, VEXOR_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Other Tools and Integrations | Knowledge & Memory |
| Quality signal | 71/100 · Great | 45/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 | VEXOR_CONFIG_JSONVEXOR_API_KEY |
Tools & capabilities
Webclaw tools 10
scrapeExtract one URL as markdown, text, JSON, LLM format, or HTMLcrawlFollow same-origin links and extract discovered pagesmapDiscover URLs without extracting every pagebatchScrape multiple URLs in parallelextractConvert page content into structured datasummarizeSummarize a pagediffCompare page content snapshotsbrandExtract colors, fonts, logos, and metadatasearchSearch the web and scrape resultsresearchMulti-source research workflow
Perenna 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.
Webclaw
{
"mcpServers": {
"0xmassi-webclaw": {
"command": "npx",
"args": [
"-y",
"create-webclaw"
]
}
}
}
Perenna
{
"mcpServers": {
"perenna": {
"command": "uvx",
"args": [
"vexor"
],
"env": {
"VEXOR_CONFIG_JSON": "YOUR_VEXOR_CONFIG_JSON_HERE",
"VEXOR_API_KEY": "YOUR_VEXOR_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Webclaw is categorized under Other Tools and Integrations and uses a local stdio subprocess. Perenna belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Webclaw for other tools and integrations work and Perenna for knowledge & memory.
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.
Webclaw is listed as free. Auth: no auth required. Perenna 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 0xmassi-webclaw and perenna as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Webclaw has a quality signal of 71/100 (Great) with 13 views, 2 installs and 2,373 GitHub stars. Perenna has 45/100 (Fair) with 2 views, 0 installs and 61 GitHub stars.
