project-boundary vs io.github.codapult/guard
project-boundary is a plugin bundle for AI coding tools published by justi. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.codapult/guard is an MCP server published by codapult. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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 |  project-boundary |  io.github.codapult/guard |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.11.0 Forks (GitHub): 3 Stars (GitHub): 90 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.10.0 Downloads/month (npm): 2 588 Downloads/week (npm): 517 Forks (GitHub): 1 Stars (GitHub): 3 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 | project-boundary | io.github.codapult/guard |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 90 (better) | 3 (worse) |
| Forks (GitHub) (differs) | 3 (better) | 1 (worse) |
| Last release (differs) | Not published | 2026-10-19 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@codapult/guard) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 5 | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/justi/claude-code-project-boundary | github.com/codapult/codapult-guard |
| Changes in the last 7 days (differs) | 0 | 1 |
| 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
project-boundary
Blocks destructive commands outside the project directory. Allows file operations within the project (refactoring, cleanup) but prevents accidental damage outside it.
io.github.codapult/guard
Local-first architecture guardrails and project context for JS/TS AI coding agents.
How to run each
project-boundary As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install project-boundary@claude-communityio.github.codapult/guard As a local MCP server: npm package
claude mcp add --transport stdio guard -- npx -y @codapult/guardCommands 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
Neither one's marketplaces publish the settings it asks for.
What it can do: project-boundary · What it can do: io.github.codapult/guard · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.