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.GitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS61 / 100 · C76 / 100 · B
Reliability9 / 2013 / 20
Security and permissions9 / 2014 / 20
Maintenance14 / 2018 / 20
Documentation16 / 2017 / 20
Setup experience13 / 2014 / 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
  • 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)
  • 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
  • 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
  • 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 clientsClaude Code, GitHub Copilot, Cline, Cursor, Trae, Windsurf, ZedClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools8915