Releases: advancedcommunities/salesforce-mcp-server
Release list
Release 1.6.6
[1.6.6] - 2026-05-27
Fixed
- Query Tool Error Surfacing:
query_recordsandquery_records_to_filenow return the actual Salesforce CLI error (e.g.INVALID_FIELD,MALFORMED_QUERY, permission denied) instead of the crypticCannot read properties of undefined (reading 'records')- Non-zero CLI status responses are converted to a structured
{ success: false, errorName, message, query }payload withisError: true - Eliminates trial-and-error debugging loops caused by swallowed error messages
- Non-zero CLI status responses are converted to a structured
Release 1.6.5
[1.6.5] - 2026-04-16
Added
- Frontdoor URL Generation: New
generate_frontdoor_urltool for authenticated browser access- Generates a Salesforce frontdoor URL (
{instanceUrl}/secur/frontdoor.jsp?sid={accessToken}&retURL={retURL}) using credentials from the Salesforce CLI - Supports optional
targetOrg(defaults to current default org) andretURL(defaults to/) parameters - Designed for use with browser automation tools such as the Playwright MCP and Chrome DevTools MCP
- Respects
ALLOWED_ORGSpermission settings
- Generates a Salesforce frontdoor URL (
Release 1.6.4
[1.6.4] - 2026-02-19
Added
- Claude Code Skill for Salesforce: New
install_skilltool that installs domain-specific guidance into Claude Code projectsinstall_skill- Installs comprehensive Salesforce MCP Server skill with tool selection guide, workflow patterns, and best practices- Skill includes guidance for all 40 tools, 5 prompts, 5 resources with practical examples and common pitfalls
- Tool count updated from 39 to 40
Fixed
- Tool Call Argument Normalization: Fixed transport-level handling of tool call arguments for improved MCP client compatibility
- Some clients send
undefinedor stringified JSON instead of proper objects for tool arguments - Server now automatically normalizes arguments before validation, ensuring consistent behavior across all clients
- Some clients send
Changed
- Documentation: Updated README.md to replace legacy DXT references with current MCPB (MCP Bundle) format
Release 1.6.3
[1.6.3] - 2026-02-19
Fixed
- Server Startup Performance: Removed eager org enumeration from resource template list callbacks that were blocking the MCP connection during handshake. Resource templates still work on-demand via
{alias}URI parameter and autocomplete provides discoverability without the performance penalty
Changed
- README Badges: Added NPM downloads and GitHub downloads badges to improve visibility of project metrics
Release 1.6.2
[1.6.2] - 2026-02-16
Fixed
- CRUD Tools Input Validation: Fixed
create_record,update_record, anddelete_recordtools to accept both stringified JSON and object input. AddedflexibleInputwrapper using Zod'sz.preprocessto automatically parse stringified JSON when clients send input as strings instead of objects - CRUD Tool Descriptions: Improved descriptions for CRUD tools to explicitly document accepted input format with parameter names and examples
Release 1.6.1
[1.6.1] - 2026-02-16
Fixed
- Icon Loading: Fixed graceful fallback when icon.png is missing, preventing crashes when running via npx where only the build/ folder is included
Release 1.6.0
[1.6.0] - 2026-02-16
Added
-
MCP Resources: Five new resources for browsable org context:
salesforce://permissions- Current server permission settingssalesforce://org/{alias}/metadata- Org metadata summary with available metadata typessalesforce://org/{alias}/objects- List of all standard and custom SObjectssalesforce://org/{alias}/object/{name}- Detailed schema for a specific SObjectsalesforce://org/{alias}/limits- API limits and usage information- Resource URIs support autocomplete for org aliases and object names
-
MCP Prompts: Five new templated workflows for guided Salesforce tasks:
soql_builder- Describe an SObject and interactively build SOQL queriesapex_review- Fetch and perform structured code review of Apex classesorg_health_check- Assess org health with live org datadeploy_checklist- Generate pre-deployment readiness checklistdebug_apex- Fetch and analyze Apex debug logs for errors and performance issues- All prompts respect
ALLOWED_ORGSpermission and support default org fallback
-
MCP Structured Output: Five core tools now return validated structured data via
outputSchema:query_records- Returns{ targetOrg, records }sobject_list- Returns{ targetOrg, sobjects }sobject_describe- Returns detailed SObject schema with fields and relationshipslist_connected_salesforce_orgs- Returns organized org data by typeget_apex_test_results- Returns test summary, individual results, and code coverage
-
MCP Progress Reporting: Long-running tools now report real-time progress:
deploy_start- Reports deployment phases (resolving → validating → deploying)run_apex_tests- Reports test execution progressscanner_run- Reports scanning progressscanner_run_dfa- Reports data flow analysis progressrun_code_analyzer- Reports code analysis progressquery_records_to_file- Reports export progress
-
MCP Elicitation: Destructive operations now request user confirmation:
delete_record- Confirms before permanently deleting recordspackage_uninstall- Confirms before uninstalling packageslogout- Confirms before logging out of orgsdeploy_start- Confirms before deployments (skipped for dry-runs)- Gracefully degrades on clients without elicitation support
-
MCP Completions: Argument auto-completion for prompts and resources:
- Prompt arguments auto-complete with connected org aliases
soql_builderauto-completes SObject names from target org- Resource URI variables auto-complete org aliases and object names
- All completions respect
ALLOWED_ORGSpermission
-
MCP Logging: Structured logging with named loggers and severity levels:
- Logger names:
salesforce,cli,permissions - Log levels:
debug,info,warning,error,critical - All tool execution and CLI commands logged with appropriate levels
- Clients can set minimum log level via
logging/setLevel
- Logger names:
-
MCP Implementation Metadata: Enhanced server identity and branding:
- Server title: "Salesforce MCP Server" with human-readable display
- Embedded base64-encoded server icon (PNG) for client UI display
- Improved server description with version and capabilities
-
MCP Registry Support: Registry publication and verification:
mcpNamein package.json for MCP registry verification (io.github.advancedcommunities/salesforce-mcp-server)server.jsonfor MCP registry publishing with full server metadata- Published to official MCP registry at mcp.run
-
Tool Annotation System: All 39 tools migrated to modern
registerTool()with ToolAnnotations:- Improved type safety and consistency
- Better IDE support and documentation generation
- Easier maintenance of tool metadata
Changed
-
TypeScript Configuration: Updated to ES2023/NodeNext for improved compatibility
- Resolves module resolution issues
- Better type checking with latest TypeScript features
-
Dependencies: Updated core dependencies:
- @modelcontextprotocol/sdk: Updated to ^1.26.0 with full MCP spec support
- zod: Updated to ^4.3.6 for improved schema validation
-
Packaging Format: Migrated from DXT to MCPB format:
- Better distribution and installation experience
- Official MCP bundle format for broader client support
Release 1.5.6
[1.5.6] - 2026-02-09
Added
- Default Org Fallback: All 24 tools that interact with a Salesforce org now accept
targetOrgas optional — when omitted, the server resolves the default org from SF CLI (sf config get target-org) - New
resolveTargetOrgutility (src/utils/resolveTargetOrg.ts): Centralized default org resolution with 30-second caching to avoid repeated subprocess calls - New tools for default org management:
get_default_org- View the current default target orgset_default_org- Change the default target orgclear_default_org- Unset the default target org
- Org visibility in responses: Every tool response now includes
targetOrgso users always see which org was used, especially when the default fallback is applied get_server_permissionsenhanced: Now shows the configured default org in its output
Changed
- CLAUDE.md Restructured: Converted legacy "Development Memories" section into native Claude Code instructions
- Renamed "Development Memories" to "Workflow Rules" with clear, actionable directives
- Moved code-related rules (JSON formatting, permission checks) into "Important Implementation Notes"
- Integrated tool registration reminder into "Adding New Tools" steps
- Consolidated documentation update reminders into single workflow rule
- Added parallel task execution instruction for improved development efficiency
Release 1.5.5
[1.5.5] - 2025-10-26
Fixed
- Salesforce CLI Path Resolution on Windows: Fixed issue where
sfcommand in PATH was being incorrectly quoted on Windows- The
deploy_starttool and all other SF CLI commands now work correctly when SF CLI is in the system PATH - Only quote SF CLI paths when they contain spaces (indicating full path like "C:\Program Files\sf\bin\sf.cmd")
- Don't quote plain command names (like "sf") that should be resolved from PATH
- Fixes "Command failed: 'sf' is not recognized" errors on Windows
- Applied fix to both
executeSfCommandandexecuteSfCommandRawfunctions in sfCommand.ts
- The
Release 1.5.4
[1.5.4] - 2025-10-22
Fixed
- Salesforce CLI Error Handling: Fixed
executeSfCommandto properly parse and return JSON error responses from Salesforce CLI- When SF CLI commands fail with
--jsonflag, errors are now properly captured from stdout - Error details (name, message, exitCode, context, stack) are now correctly returned to MCP clients
- Fixes issue where deployment errors like "No source-backed components present in the package" were not visible
- Maintains backward compatibility with existing error handling
- When SF CLI commands fail with