M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionSalesforce DX MCP ServerOfficial Salesforce DX toolset that lets LLMs read and operate on your authorized Salesforce orgs.NPM Sentinel MCP ServerAI-powered NPM package analysis MCP server
FMRS61 / 100 · C79 / 100 · B
Reliability9 / 2012 / 20
Security and permissions9 / 2016 / 20
Maintenance14 / 2018 / 20
Documentation16 / 2018 / 20
Setup experience13 / 2015 / 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 auditing NPM dependencies within AI workflows
  • Teams performing supply chain security assessments
  • Users of Claude Desktop, Cursor, or VS Code
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)
  • 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
  • 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
  • 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
  • `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
  • 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 clientsClaude Code, GitHub Copilot, Cline, Cursor, Trae, Windsurf, ZedClaude Desktop, VS Code, Cursor
Tools8919