| FMRS | 61 / 100 · C | 80 / 100 · B | 76 / 100 · B |
|---|
| Reliability | 9 / 20 | 14 / 20 | 13 / 20 |
|---|
| Security and permissions | 9 / 20 | 16 / 20 | 14 / 20 |
|---|
| Maintenance | 14 / 20 | 17 / 20 | 18 / 20 |
|---|
| Documentation | 16 / 20 | 15 / 20 | 17 / 20 |
|---|
| Setup experience | 13 / 20 | 18 / 20 | 14 / 20 |
|---|
| Best for | - Developers already using the Salesforce CLI and a DX project
- Teams that want an AI coding assistant to operate directly on Salesforce metadata, Apex, and LWC
- Projects migrating Aura to LWC or adopting DevOps Center workflows
| - Developers using fast-moving frameworks/libraries worried about the AI suggesting stale code
- Scenarios wanting zero-config documentation lookup
| - Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
- Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
|
|---|
| Not for | - Users without a local Salesforce CLI setup or any authorized org
- Cases needing only trivial read-only lookups without wanting the context overhead of the broader toolset (can be trimmed via --toolsets, but the default footprint is still sizable)
| - 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)
| - Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
- Environments with strict network isolation for private repos that can't reach the official remote endpoint
|
|---|
| Required permissions | - Requires orgs to be pre-authorized locally via `sf org login web` or equivalent
- Access is scoped per `--orgs`: specific orgs, the default org/Dev Hub, or (use with caution) all authorized orgs
- Several tools have write access — deploying/retrieving metadata, creating or deleting scratch orgs, assigning permission sets, committing DevOps Center work items
| - 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
| - A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
- Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
|
|---|
| Risks and side effects | - `ALLOW_ALL_ORGS` grants the server access to every locally authorized org, which can expose production orgs if misconfigured
- Tools like `deploy_metadata` and `delete_org` make real changes or deletions to orgs — misuse carries data/config risk
- Telemetry is enabled by default; use `--no-telemetry` explicitly if privacy/compliance requires disabling it
- `DEFAULT_TARGET_ORG`/`DEFAULT_TARGET_DEV_HUB` resolve dynamically on every tool call, so switching your local default org changes which org the server can act on
| - 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
| - Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
- In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
|
|---|
| Supported clients | Claude Code, VS Code (Copilot), Cline, Cursor, Trae, Windsurf, Zed | Claude Code, VS Code, Cursor, Cline, Amp | Claude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains, Zed, Amp |
|---|
| Tools | 89 | 2 | 15 |
|---|