@salesforce/mcp-provider-code-analyzer

Name: @salesforce/mcp-provider-code-analyzer Review
Item: @salesforce/mcp-provider-code-analyzer
Rating: 3.9
Author: Aaron Matthews

Connector Development Solid

Works inClaude Code Claude Cowork Claude Chat

Solid Scanned — metadata only

Integrates Salesforce Code Analyzer into MCP servers, enabling automated code quality and security scanning within Salesforce ecosystems.

(For Internal Use Only) Provides MCP Tools for Salesforce Code Analyzer to a MCP Server

Ask Claude to analyze your Apex code for potential bugs and security vulnerabilities.
Generate a report of code quality issues found across your Salesforce codebase.
Find performance problems and best practice violations in Lightning components automatically.

445 starsApache-2.0 (commercial OK)Free

Why it matters

Integrates Salesforce Code Analyzer into MCP servers, enabling automated code quality and security scanning within Salesforce ecosystems. Reduces manual review cycles and catches compliance violations before deployment.

Best for

Salesforce development teams and enterprise consultants implementing continuous code quality gates on Apex and Lightning components.

Works in

Claude Code Claude Cowork Claude Chat

Source

https://www.npmjs.com/package/@salesforce/mcp-provider-code-...

By salesforce-releases

How to Get It

Option 1: Claude Desktop AppOpen the Customize panel in the sidebar → browse connectors → search and add. Works in Claude Code, Claude Cowork, and Claude Chat.

Option 2: Paste into Claude CodeCopy the command below and paste it into a Claude Code conversation. Claude will run it for you.

Command

npx -y @salesforce/mcp-provider-code-analyzer

Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.

Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.

First thing to try

Once it’s connected, paste this into Claude:

Analyze my Apex code for potential bugs and security vulnerabilities

CostFree

Trust Signals Auto-scanned

Stars445Contributors35Last updated2026-07-25LicenseApache-2.0 (OK for commercial use)Weekly downloads44,597Known CVEsNone foundSources: GitHub Advisory Database + OSV.dev · Scanned 2026-07-25 · scanner v1

Data & Access

Data processingPrompts sent to Anthropic API. Enterprise/Team plans exclude training.

Community Pulse New

No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.

Reviewer notes

Auto-scanned review. These are observations, not a security certification.

Scored from trust signals (evidence-eval-v1): 445 GitHub stars; 35 contributors; last commit 0d ago; license Apache-2.0.

Things to check

Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.

How to evaluate tools before deploying →

Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.

Evaluation Scores

Evaluation

Ease of Use

3/5

Versatility

4/5

Reliability

5/5

Security

4/5

Overall score3.90 / 5.00 SolidEvaluatedJul 2026

Scored from trust signals (evidence-eval-v1): 445 GitHub stars; 35 contributors; last commit 0d ago; license Apache-2.0.

← Back to the Claude Observatory