| FMRS | 61 / 100 · C | 80 / 100 · B | 79 / 100 · B |
|---|
| Reliability | 10 / 20 | 14 / 20 | 12 / 20 |
|---|
| Security and permissions | 10 / 20 | 16 / 20 | 16 / 20 |
|---|
| Maintenance | 14 / 20 | 17 / 20 | 18 / 20 |
|---|
| Documentation | 15 / 20 | 15 / 20 | 18 / 20 |
|---|
| Setup experience | 12 / 20 | 18 / 20 | 15 / 20 |
|---|
| Best for | - Teams that need agent workflows under deterministic admission and policy constraints
- Scenarios requiring worst-case pricing before execution and per-node cost attribution after
- Compliance or investigation workflows needing one replayable audit trace where the dashboard and the audit trail are the same file
- Organizations that want a human to press a button before execution starts, for example from Slack
- Developers who want deterministic, reproducible demos and tests on any checkout via `--scripted`
| - Developers using fast-moving frameworks/libraries worried about the AI suggesting stale code
- Scenarios wanting zero-config documentation lookup
| - Developers auditing NPM dependencies within AI workflows
- Teams performing supply chain security assessments
- Users of Claude Desktop, Cursor, or VS Code
|
|---|
| Not for | - Those who only need an interactive single-agent loop without pre-execution authorization
- Anyone looking for a general personal AI assistant gateway or a tool configured by allowlists
- Users expecting node arguments to be fully validated: admission authorises a node's kind, arguments are checked only where the kind declares an args_schema, and a schema bounds their shape, not what a factory lets them reach
- Scenarios requiring the HTTP API to use a durable session layer, or the tool plane to be governed by policy documents instead of CLI flags
- Users who need agent nodes on the Claude CLI backend to be fully governed: by default they run under an allowlist mapped from the node's own tools, but enforcement there is Claude Code's, and the explicit bypass tier has no checks at all
| - Looking up internal/private codebase documentation (Context7 targets publicly published open-source libraries)
- Cases needing very high coverage of obscure, niche libraries (coverage depends on what Context7's platform has indexed)
| - Projects outside the NPM ecosystem (e.g., pure Python/Go)
- Environments without network access to deps.dev, OSV.dev, and the npm registry
- Scenarios requiring maintenance by an official upstream vendor
|
|---|
| Required permissions | - The default backend drives the claude CLI on your PATH (a Claude subscription, no API key)
- Node bodies come from the registry, never from a proposal; the registry is the source of the kinds a planner may propose
- Policy decides what the planner is able to propose: a denied edge changes the shape of the graph rather than producing a refusal to retry
- The MCP gate binds the MCP surface, not the host: an agent with its own file tools in the run directory could forge the approval decision, and the trust boundary is the working directory
- run_command children are unconfined
- ContainerExecutor is the real boundary; the in-process sandbox is defense in depth
| - Usable without an API key (subject to a free-tier rate limit); CONTEXT7_API_KEY is an optional credential for higher quota
- Read-only documentation lookup — no code execution or local filesystem access involved
| - Network access to the NPM registry and external services (deps.dev, OSV.dev, OpenSSF, npms.io, GitHub)
- Read access to workspace lockfiles (pnpm-lock.yaml, package-lock., yarn.lock) for cache invalidation
|
|---|
| Risks and side effects | - Admission authorises a node's kind; arguments are validated only where the kind declares an args_schema, and a schema bounds their shape rather than what a factory lets them reach
- The in-process sandbox is defense in depth, run_command children are unconfined, and ContainerExecutor is the real boundary when explicitly used
- The HTTP API does not yet use the durable session layer
- On the Claude CLI backend an agent node is delegated, not governed: by default it runs under an allowlist mapped from the node's own tools, but enforcement is Claude Code's, and the bypass tier has no checks at all
- Policy documents govern planning while the tool plane still reads CLI flags
- The MCP gate binds the MCP surface, not the host: an agent with its own file tools in the run directory could forge the approval decision; the trust boundary is the working directory, as it is for the Slack workspace
| - The free tier has limited quota — high-frequency use may hit rate limits
- Documentation content comes from Context7's platform index, so its accuracy and freshness depend on that platform's crawl cadence
| - Third-party READMEs and changelogs are untrusted external content; they are wrapped in tags with _meta flags but should still be handled cautiously
- Depends on availability and accuracy of external services
- Batch requests are capped at 25 packages to prevent registry enumeration; larger sets require batching
- Third-party open source project, not officially maintained by NPM or Anthropic
|
|---|
| Supported clients | | Claude Code, VS Code, Cursor, Cline, Amp | Claude Desktop, VS Code, Cursor, Smithery.ai |
|---|
| Tools | 0 | 2 | 19 |
|---|