Webclaw vs Scrivener MCP
A side-by-side look at the Webclaw and Scrivener MCP 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 Scrivener MCP 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 Scrivener MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Other Tools and Integrations | Knowledge & Memory |
| Quality signal | 71/100 · Great | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2,373 | 67 |
| Directory activity | 13 views 2 installs 0 upvotes | 18 views 12 installs 6 upvotes |
| Tools | 10 | Not listed |
| Full listing | View Webclaw | View Scrivener MCP |
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
Scrivener MCP 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"
]
}
}
}
Scrivener MCP
{
"mcpServers": {
"writerslogic-scrivener-mcp": {
"command": "npx",
"args": [
"-y",
"scrivener-setup"
]
}
}
}
Frequently asked questions
Webclaw is categorized under Other Tools and Integrations and uses a local stdio subprocess. Scrivener MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Webclaw for other tools and integrations work and Scrivener MCP 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. Scrivener MCP is listed as free. Auth: no auth required. 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 writerslogic-scrivener-mcp 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. Scrivener MCP has 61/100 (Good) with 18 views, 12 installs and 67 GitHub stars.