io.github.Digital-Defiance/mcp-process vs io.github.Writbase/writbase
io.github.Digital-Defiance/mcp-process is an MCP server published by Digital-Defiance. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.Writbase/writbase is an MCP server published by Writbase. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.Digital-Defiance/mcp-process |  io.github.Writbase/writbase |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.1 Downloads/month (npm): 290 Downloads/week (npm): 58 Forks (GitHub): 1 Stars (GitHub): 3 Not marked · First seen |
Listed Version: 0.1.3 Downloads/month (npm): 138 Downloads/week (npm): 15 Forks (GitHub): 0 Stars (GitHub): 11 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | io.github.Digital-Defiance/mcp-process | io.github.Writbase/writbase |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 3 (worse) | 11 (better) |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@ai-capabilities-suite/mcp-process) | On your machine (writbase) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/digital-defiance/ai-capabilities-suite | github.com/writbase/writbase |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
io.github.Digital-Defiance/mcp-process
Process management and monitoring for AI agents with strict security boundaries
io.github.Writbase/writbase
MCP-native task management for AI agent fleets with scoped permissions and provenance.
How to run each
io.github.Digital-Defiance/mcp-process As a local MCP server: npm package
claude mcp add --transport stdio mcp-process -- npx -y @ai-capabilities-suite/mcp-processio.github.Writbase/writbase
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: WRITBASE_AGENT_KEY (secret), WRITBASE_URL
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of io.github.Digital-Defiance/mcp-process publish no settings it asks for, so we do not compare settings.
What it can do: io.github.Digital-Defiance/mcp-process · What it can do: io.github.Writbase/writbase · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.