@salesforce/mcp 0.26.5 → 0.26.7

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +206 -169
  2. package/npm-shrinkwrap.json +147 -60
  3. package/package.json +3 -3
package/README.md CHANGED
@@ -7,16 +7,16 @@ MCP Server for Interacting with Salesforce Orgs
7
7
  ## Feedback
8
8
 
9
9
  Report bugs and issues [here](https://github.com/forcedotcom/mcp/issues).
10
- For feature requests and other related topics, start a Discussion [here](https://github.com/forcedotcom/mcp/discussions).
10
+ For feature requests and other related topics, start a Discussion [here](https://github.com/forcedotcom/mcp/discussions).
11
11
 
12
12
  ## Documentation
13
13
 
14
- For complete documentation about the Salesforce DX MCP Server, see [this section](https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_mcp.htm) in the _Salesforce DX Developer Guide_. The docs include:
14
+ For general documentation about the Salesforce DX MCP Server, see [this section](https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_mcp.htm) in the _Salesforce DX Developer Guide_. The docs include:
15
15
 
16
- * Comprehensive overview, including details about the security features.
17
- * Quick start guide.
18
- * Multiple examples of configuring the server in your MCP client.
19
- * Sample prompts for invoking the core DX MCP tools.
16
+ - Comprehensive overview, including details about the security features.
17
+ - Quick start guide.
18
+ - Multiple examples of configuring the server in your MCP client.
19
+ - Sample prompts for invoking the core DX MCP tools.
20
20
 
21
21
  [Here are the release notes.](https://github.com/forcedotcom/mcp/tree/main/releasenotes)
22
22
 
@@ -29,45 +29,47 @@ The Salesforce DX MCP Server is a specialized Model Context Protocol (MCP) imple
29
29
 
30
30
  ## Configure the DX MCP Server
31
31
 
32
- Configure the Salesforce DX MCP Server for your MCP client by updating its associated MCP JSON file; each client is slightly different, so check your MCP client documentation for details. See [MCP Client Configurations](./README.md#mcp-client-configurations) for more examples.
32
+ Configure the Salesforce DX MCP Server for your MCP client by updating its associated MCP JSON file; each client is slightly different, so check your MCP client documentation for details. See [MCP Client Configurations](#mcp-client-configurations) for more examples.
33
33
 
34
34
  Here's an example for VS Code with Copilot in which you create and update a `.vscode/mcp.json` file in your project:
35
35
 
36
- ```
36
+ ```json
37
37
  {
38
- "servers": {
39
- "Salesforce DX": {
40
- "command": "npx",
41
- "args": ["-y", "@salesforce/mcp",
42
- "--orgs", "DEFAULT_TARGET_ORG",
43
- "--toolsets", "orgs,metadata,data,users",
44
- "--tools", "run_apex_test",
45
- "--allow-non-ga-tools"]
46
- }
47
- }
38
+ "servers": {
39
+ "Salesforce DX": {
40
+ "command": "npx",
41
+ "args": ["-y", "@salesforce/mcp",
42
+ "--orgs", "DEFAULT_TARGET_ORG",
43
+ "--toolsets", "orgs,metadata,data,users",
44
+ "--tools", "run_apex_test",
45
+ "--allow-non-ga-tools"]
46
+ }
47
+ }
48
48
  }
49
49
  ```
50
50
 
51
- The `args` format shown in the preceding example is the same for all MCP clients; it's how you customize the DX MCP Server for your particular environment.
51
+ The `args` format shown in the preceding example is the same for all MCP clients; it's how you customize the DX MCP Server for your particular environment.
52
52
 
53
53
  **Notes**:
54
- - The `"-y", "@salesforce/mcp"` part tells `npx` to automatically install the `@salesforce/mcp` package instead of asking permission. Don't change this.
54
+
55
+ - The `"-y", "@salesforce/mcp"` part tells `npx` to automatically install the `@salesforce/mcp` package instead of asking permission. Don't change this.
55
56
  - For possible flags that you can pass to the `args` option, and the possible values that you can pass to the `--orgs`, `--toolsets`, and `--tools` flags, see these sections:
56
- - [Available Flags for the `args` Option](./README.md#available-flags-for-the-args-option)
57
- - [Configure Orgs](./README.md#configure-orgs)
58
- - [Configure Toolsets](./README.md#configure-toolsets)
59
- - [Configure Tools](./README.md#configure-tools)
57
+ - [Available Flags for the `args` Option](#available-flags-for-the-args-option)
58
+ - [Configure Orgs](#configure-orgs)
59
+ - [Configure Toolsets](#configure-toolsets)
60
+ - [Configure Tools](#configure-tools)
60
61
  - When writing the `args` option, surround both the flag names and their values in double quotes, and separate all flags and values with commas. Some flags are Boolean and don't take a value.
61
- - The preceding example shows three flags that take a string value (`--orgs`, `--toolsets`, and `--tools`) and one Boolean flag (`--allow-non-ga-tools`). This configuration starts a DX MCP Server that enables all the MCP tools in the `orgs`, `metadata`, `data`, and `users` toolsets and a specific tool called `run_apex_tests`. It also enables tools in these configured toolsets that aren't yet generally available.
62
+ - The preceding example shows three flags that take a string value (`--orgs`, `--toolsets`, and `--tools`) and one Boolean flag (`--allow-non-ga-tools`). This configuration starts a DX MCP Server that enables all the MCP tools in the `orgs`, `metadata`, `data`, and `users` toolsets and a specific tool called `run_apex_tests`. It also enables tools in these configured toolsets that aren't yet generally available.
62
63
 
63
- ## MCP Client Configurations
64
+ ## MCP Client Configurations
64
65
 
65
- Here are examples of configuring the Salesforce DX MCP Server in various MCP clients.
66
+ Here are examples of configuring the Salesforce DX MCP Server in various MCP clients.
66
67
 
67
68
  ### Claude Code
68
69
 
69
70
  To configure [Claude Code](https://www.claude.com/product/claude-code) to work with Salesforce DX MCP Server, add this snippet to the `.mcp.json` file in your project:
70
- ```
71
+
72
+ ```json
71
73
  {
72
74
  "mcpServers": {
73
75
  "Salesforce DX": {
@@ -76,43 +78,45 @@ To configure [Claude Code](https://www.claude.com/product/claude-code) to work w
76
78
  "--orgs", "DEFAULT_TARGET_ORG",
77
79
  "--toolsets", "orgs,metadata,data,users",
78
80
  "--tools", "run_apex_test",
79
- "--allow-non-ga-tools" ]
81
+ "--allow-non-ga-tools"]
80
82
  }
81
83
  }
82
84
  }
83
85
  ```
84
- ### Cursor
85
86
 
86
- To configure [Cursor](https://cursor.com/docs/context/mcp) to work with Salesforce DX MCP Server, add this snippet to your Cursor `mcp.json` file:
87
+ ### Cline
88
+
89
+ To configure [Cline](https://docs.cline.bot/mcp/mcp-overview) to work with Salesforce DX MCP Server, add this snippet to your Cline `cline_mcp_settings.json` file:
87
90
 
88
91
  ```json
89
92
  {
90
93
  "mcpServers": {
91
94
  "Salesforce DX": {
92
95
  "command": "npx",
93
- "args": ["-y", "@salesforce/mcp@latest",
94
- "--orgs", "DEFAULT_TARGET_ORG",
95
- "--toolsets", "orgs,metadata,data,users",
96
- "--tools", "run_apex_test",
97
- "--allow-non-ga-tools" ]
96
+ "args": ["-y", "@salesforce/mcp@latest",
97
+ "--orgs", "DEFAULT_TARGET_ORG",
98
+ "--toolsets", "orgs,metadata,data,users",
99
+ "--tools", "run_apex_test",
100
+ "--allow-non-ga-tools"]
98
101
  }
99
102
  }
100
103
  }
101
104
  ```
102
105
 
103
- ### Cline
106
+ ### Cursor
107
+
108
+ To configure [Cursor](https://cursor.com/docs/context/mcp) to work with Salesforce DX MCP Server, add this snippet to your Cursor `mcp.json` file:
104
109
 
105
- To configure [Cline](https://docs.cline.bot/mcp/mcp-overview) to work with Salesforce DX MCP Server, add this snippet to your Cline `cline_mcp_settings.json` file:
106
110
  ```json
107
111
  {
108
112
  "mcpServers": {
109
113
  "Salesforce DX": {
110
114
  "command": "npx",
111
- "args": ["-y", "@salesforce/mcp@latest",
112
- "--orgs", "DEFAULT_TARGET_ORG",
113
- "--toolsets", "orgs,metadata,data,users",
114
- "--tools", "run_apex_test",
115
- "--allow-non-ga-tools" ]
115
+ "args": ["-y", "@salesforce/mcp@latest",
116
+ "--orgs", "DEFAULT_TARGET_ORG",
117
+ "--toolsets", "orgs,metadata,data,users",
118
+ "--tools", "run_apex_test",
119
+ "--allow-non-ga-tools"]
116
120
  }
117
121
  }
118
122
  }
@@ -122,23 +126,23 @@ To configure [Cline](https://docs.cline.bot/mcp/mcp-overview) to work with Sales
122
126
 
123
127
  For these other clients, refer to their documentation for adding MCP servers and follow the same pattern as in the preceding examples to configure the Salesforce DX MCP Server:
124
128
 
129
+ - [Trae](https://docs.trae.ai/ide/model-context-protocol?_lang=en)
125
130
  - [Windsurf](https://docs.windsurf.com/windsurf/cascade/mcp)
126
131
  - [Zed](https://github.com/zed-industries/zed)
127
- - [Trae](https://docs.trae.ai/ide/model-context-protocol?_lang=en)
128
132
 
129
133
  ## Available Flags for the "args" Option
130
134
 
131
- These are the flags that you can pass to the `args` option.
135
+ These are the flags that you can pass to the `args` option.
132
136
 
133
- | Flag Name | Description | Required? |Notes |
134
- | -----------------| -------| ------- | ----- |
135
- | `--orgs` | One or more orgs that you've locally authorized. | Yes | You must specify at least one org. <br/> <br/>See [Configure Orgs](./README.md#configure-orgs) for the values you can pass to this flag. |
136
- | `--toolsets` | Sets of tools, based on functionality, that you want to enable. | No | Set to "all" to enable every tool in every toolset. <br/> <br/>See [Configure Toolsets](./README.md#configure-toolsets) for the values you can pass to this flag.|
137
- | `--tools` | Individual tool names that you want to enable. | No | You can use this flag in combination with the `--toolsets` flag. For example, you can enable all tools in one toolset, and just one tool in a different toolset. |
138
- | `--no-telemetry` | Boolean flag to disable telemetry, the automatic collection of data for monitoring and analysis. | No | Telemetry is enabled by default, so specify this flag to disable it. |
139
- | `--debug` | Boolean flag that requests that the DX MCP Server print debug logs. | No | Debug mode is disabled by default. <br/> <br/>**NOTE:** Not all MCP clients expose MCP logs, so this flag might not work for all IDEs. |
140
- | `--allow-non-ga-tools` | Boolean flag to allow the DX MCP Server to use both the generally available (GA) and NON-GA tools that are in the toolsets or tools you specify. | No | By default, the DX MCP server uses only the tools marked GA. |
141
- | `--dynamic-tools` | (experimental) Boolean flag that enables dynamic tool discovery and loading. When specified, the DX MCP server starts with a minimal set of core tools and loads new tools as needed. | No| This flag is useful for reducing the initial context size and improving LLM performance. Dynamic tool discovery is disabled by default.<br/> <br/>**NOTE:** This feature works in VSCode and Cline but may not work in other environments.|
137
+ | Flag Name | Description | Required? | Notes |
138
+ | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
139
+ | `--allow-non-ga-tools` | Boolean flag to allow the DX MCP Server to use both the generally available (GA) and NON-GA tools that are in the toolsets or tools you specify. | No | By default, the DX MCP server uses only the tools marked GA. |
140
+ | `--debug` | Boolean flag that requests that the DX MCP Server print debug logs. | No | Debug mode is disabled by default. <br/> <br/>**NOTE:** Not all MCP clients expose MCP logs, so this flag might not work for all IDEs. |
141
+ | `--dynamic-tools` | (experimental) Boolean flag that enables dynamic tool discovery and loading. When specified, the DX MCP server starts with a minimal set of core tools and loads new tools as needed. | No | This flag is useful for reducing the initial context size and improving LLM performance. Dynamic tool discovery is disabled by default.<br/> <br/>**NOTE:** This feature works in VSCode and Cline but may not work in other environments. |
142
+ | `--no-telemetry` | Boolean flag to disable telemetry, the automatic collection of data for monitoring and analysis. | No | Telemetry is enabled by default, so specify this flag to disable it. |
143
+ | `--orgs` | One or more orgs that you've locally authorized. | Yes | You must specify at least one org. <br/> <br/>See [Configure Orgs](#configure-orgs) for the values you can pass to this flag. |
144
+ | `--tools` | Individual tool names that you want to enable. | No | You can use this flag in combination with the `--toolsets` flag. For example, you can enable all tools in one toolset, and just one tool in a different toolset. |
145
+ | `--toolsets` | Sets of tools, based on functionality, that you want to enable. | No | Set to "all" to enable every tool in every toolset. <br/> <br/>See [Configure Toolsets](#configure-toolsets) for the values you can pass to this flag. |
142
146
 
143
147
  ## Configure Orgs
144
148
 
@@ -148,36 +152,38 @@ You must explicitly [authorize the orgs](https://developer.salesforce.com/docs/a
148
152
 
149
153
  These are the available values for the `--orgs` flag:
150
154
 
151
- | --orgs Value | Description |
152
- | -------- | ---------- |
153
- | `DEFAULT_TARGET_ORG` | Allow access to your default org. If you've set a local default org in your DX project, the MCP server uses it. If not, the server uses a globally-set default org.|
154
- | `DEFAULT_TARGET_DEV_HUB` | Allow access to your default Dev Hub org. If you've set a local default Dev Hub org in your DX project, the MCP server uses it. If not, the server uses a globally-set default Dev Hub org.|
155
- | `ALLOW_ALL_ORGS` | Allow access to all authorized orgs. Use this value with caution.|
156
- | `<username or alias>` | Allow access to a specific org by specifying its username or alias.|
155
+ | --orgs Value | Description |
156
+ | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
157
+ | `ALLOW_ALL_ORGS` | Allow access to all authorized orgs. Use this value with caution. |
158
+ | `DEFAULT_TARGET_DEV_HUB` | Allow access to your default Dev Hub org. If you've set a local default Dev Hub org in your DX project, the MCP server uses it. If not, the server uses a globally-set default Dev Hub org. |
159
+ | `DEFAULT_TARGET_ORG` | Allow access to your default org. If you've set a local default org in your DX project, the MCP server uses it. If not, the server uses a globally-set default org. |
160
+ | `<username or alias>` | Allow access to a specific org by specifying its username or alias. |
157
161
 
158
162
  ## Configure Toolsets
159
163
 
160
- The Salesforce DX MCP Server supports **toolsets** - a way to selectively enable different groups of MCP tools based on your needs. This allows you to run the MCP server with only the tools you require, which in turn reduces the context.
164
+ The Salesforce DX MCP Server supports **toolsets**—a way to selectively enable different groups of MCP tools based on your needs. This allows you to run the MCP server with only the tools you require, which in turn reduces the LLM context.
161
165
 
162
- Use the `--toolsets` flag to specify the toolsets when you configure the Salesforce DX MCP Server. Separate multiple toolsets with commas.
166
+ Use the `--toolsets` flag to specify the toolsets when you configure the Salesforce DX MCP Server. Separate multiple toolsets with commas.
163
167
 
164
168
  These are the available toolsets.
165
169
 
166
- | Toolset| Description|
167
- | ----- | ----- |
168
- | `all` | Enables all available tools from all toolsets. Use caution, this will load over 60 tools. |
169
- | `aura-experts` | [Tools which provides Aura component analysis, blueprinting, and migration expertise.](README.md#aura-experts-toolset)|
170
- | `code-analysis` | [Tools for static analysis of your code using Salesforce Code Analyzer](README.md#code-analysis-toolset)|
171
- | `data` | [Tools to manage the data in your org, such as listing all accounts.](README.md#data-toolset)|
172
- | `enrichment` | [Tools to enrich metadata for components in your org.](README.md#enrichment-toolset)|
173
- | `lwc-experts` | [Tools to assist with LWC development, testing, optimization, and best practices.](README.md#lwc-experts-toolset)|
174
- | `metadata` | [Tools to deploy and retrieve metadata to and from your org and your DX project.](README.md#metadata-toolset)|
175
- | `mobile` | [Tools for mobile development and capabilities.](README.md#mobile-toolset)|
176
- | `mobile-core` | [A subset of mobile tools focused on essential mobile capabilities.](README.md#mobile-core-toolset)|
177
- | `orgs` | [Tools to manage your authorized orgs.](README.md#orgs-toolset)|
178
- | `scale-products` | [Tools for detecting and fixing Apex performance antipatterns.](README.md#scale-products-toolset)|
179
- | `testing` | [Tools to test your code and features](README.md#testing-toolset)|
180
- | `users` | [Tools to manage org users, such as assigning a permission set.](README.md#users-toolset)|
170
+ | Toolset | Description | See Tool List |
171
+ | ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- |
172
+ | `all` | Enables all available tools from all toolsets. <br>We recommend that you configure only the toolsets you’re going to use, rather than all of them with this value. The DX MCP Server includes over 60 MCP tools, so enabling them all in your MCP client can overwhelm the LLM context. | N/A |
173
+ | `aura-experts` | Tools that provide Aura component analysis, blueprinting, and migration expertise.. | [Link](#aura-experts-toolset) |
174
+ | `code-analysis` | Tools for static analysis of your code using Salesforce Code Analyzer. | [Link](#code-analysis-toolset) |
175
+ | `core` | Core set of DX MCP tools. This toolset is always enabled. | [Link](#core-toolset-always-enabled) |
176
+ | `data` | Tools to manage the data in your org, such as listing all accounts. | [Link](#data-toolset) |
177
+ | `devops` | Tools to securely and autonomously read, manage, and operate DevOps Center resources. | [Link](#devops-center-toolset) |
178
+ | `enrich_metadata`| Tools to Enrich metadata components in your DX project. | [Link](#enrichment-toolset) |
179
+ | `lwc-experts` | Tools to assist with Lightning Web Component (LWC) development, testing, optimization, and best practices. | [Link](#lightning-web-components-lwc-experts-toolset) |
180
+ | `metadata` | Tools to deploy and retrieve metadata to and from your org and your DX project. | [Link](#metadata-toolset) |
181
+ | `mobile` | Tools for mobile development and capabilities. | [Link](#mobile-toolset) |
182
+ | `mobile-core` | A subset of tools from the `mobile` toolset focused on essential mobile capabilities. | [Link](#mobile-core-toolset) |
183
+ | `orgs` | Tools to manage your authorized orgs. | [Link](#orgs-toolset) |
184
+ | `scale-products` | Tools for detecting and fixing Apex performance. | [Link](#scale-products-toolset) |
185
+ | `testing` | Tools to test your code and features. | [Link](#testing-toolset) |
186
+ | `users` | Tools to manage org users, such as assigning a permission set. | [Link](#users-toolset) |
181
187
 
182
188
  ## Configure Tools
183
189
 
@@ -185,136 +191,167 @@ The Salesforce DX MCP Server also supports registering individual **tools**. Thi
185
191
 
186
192
  Use the `--tools` flag to enable specific tools when you configure the Salesforce DX MCP Server. Separate multiple tools with commas. The `--tools` flag is optional.
187
193
 
188
- The following sections list all the tools that are included in a specific toolset. The tools marked NON-GA are not yet generally available, specify the `--allow-non-ga-tools` flag to use them.
189
-
190
- ### Core Toolset (always enabled)
191
-
192
- - `get_username` - Determines the appropriate username or alias for Salesforce operations, handling both default orgs and Dev Hubs.
193
- - `resume_tool_operation` - Resumes a long-running operation that wasn't completed by another tool.
194
-
195
- ### Orgs Toolset
194
+ The following sections list all the tools that are included in a specific toolset.
196
195
 
197
- - `list_all_orgs` - Lists all configured Salesforce orgs, with optional connection status checking.
198
- - `create_org_snapshot` - (NON-GA) Create a scratch org snapshot.
199
- - `create_scratch_org` - (NON-GA) Create a scratch org.
200
- - `delete_org` - (NON-GA) Delete a locally-authorized Salesforce scratch org or sandbox.
201
- - `open_org` - (NON-GA) Open an org in a browser.
196
+ > [!NOTE]
197
+ > The tools marked NON-GA are not yet generally available. Specify the `--allow-non-ga-tools` flag to use them.
202
198
 
203
- **NOTE:** The tools marked NON-GA are not yet generally available, specify the `--allow-non-ga-tools` flag to use them.
199
+ ### Aura Experts Toolset
204
200
 
205
- ### Data Toolset
201
+ For complete documentation, see [Use the Aura-to-LWC Migration Tools](https://developer.salesforce.com/docs/platform/lwc/guide/mcp-aura.html) in the _Lightning Web Components Developer Guide_.
206
202
 
207
- - `run_soql_query` - Runs a SOQL query against a Salesforce org.
203
+ - `create_aura_blueprint_draft` (GA) - Creates a comprehensive Product Requirements Document (PRD) blueprint for Aura component migration. Analyzes Aura component files and generates framework-agnostic specifications suitable for LWC migration, including business requirements, technical patterns, and migration guidelines.
204
+ - `enhance_aura_blueprint_draft` (GA) - Enhances an existing draft PRD with expert analysis and unknown resolution. Takes a draft blueprint and applies specialized Aura expert knowledge to resolve dependencies, add technical insights, and improve the migration specifications for better LWC implementation guidance.
205
+ - `orchestrate_aura_migration` (GA) - Orchestrates the complete Aura to LWC migration workflow. Provides end-to-end guidance for the entire migration process, from initial analysis through final implementation, including best practices, tooling recommendations, and quality assurance steps.
206
+ - `transition_prd_to_lwc` (GA) - Provides migration bridge guidance for creating LWC components from Aura specifications. Takes the enhanced PRD and generates specific implementation guidance, platform service mappings, and step-by-step instructions for building the equivalent LWC component.
208
207
 
209
- ### Users Toolset
208
+ ### Code Analysis Toolset
210
209
 
211
- - `assign_permission_set` - Assigns a permission set to the user or on behalf of another user.
210
+ For complete documentation, see [Use MCP Tools to Analyze Your Code ](https://developer.salesforce.com/docs/platform/salesforce-code-analyzer/guide/mcp.html) in the _Salesforce Code Analyzer Developer Guide_.
212
211
 
213
- ### Metadata Toolset
212
+ - `describe_code_analyzer_rule` (GA) - A tool for getting the description of a Code Analyzer rule.
213
+ - `list_code_analyzer_rules` (GA) - A tool for selecting Code Analyzer rules based on a number of criteria.
214
+ - `query_code_analyzer_results` (GA) - Queries a Code Analyzer results JSON file and returns filtered violations. Supports filters such as severity, category/tag, engine, rule, and file name, plus top-N and sorting. Use this after running `run_code_analyzer` to read the generated results file. After completion, this tool will summarize and explain the filtered results to the user.
215
+ - `run_code_analyzer` (GA) - A tool for performing static analysis against code. This tool can validate that code conforms to best practices, check for security vulnerabilities, and identify possible performance issues. It returns a JSON containing the absolute path to a results file if such a file was created and a string indicating the overall success or failure of the operation.
214
216
 
215
- - `deploy_metadata` - Deploys metadata from your DX project to an org.
216
- - `retrieve_metadata` - Retrieves metadata from your org to your DX project.
217
+ ### Core Toolset (always enabled)
217
218
 
218
- ### Testing Toolset
219
+ For sample prompts that invoke the core DX MCP tools, see [Use the Core Salesforce DX MCP Tools](https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_mcp_use_core_tools.htm) in the _Salesforce DX Developer Guide_.
219
220
 
220
- - `run_agent_test` - Executes agent tests in your org.
221
- - `run_apex_test` - Executes apex tests in your org.
221
+ - `get_username` (GA) - Determines the appropriate username or alias for Salesforce operations, handling both default orgs and Dev Hubs.
222
+ - `resume_tool_operation` (GA) - Resumes a long-running operation that wasn't completed by another tool.
222
223
 
223
- ### Mobile Toolset
224
+ ### Data Toolset
224
225
 
225
- - `create_mobile_lwc_app_review` - Provides TypeScript API documentation for Salesforce LWC App Review Service, offering expert guidance for implementing app review features in Lightning Web Components.
226
- - `create_mobile_lwc_ar_space_capture` - Provides TypeScript API documentation for Salesforce L WC AR Space Capture, offering expert guidance for implementing AR space capture features in Lightning Web Components.
227
- - `create_mobile_lwc_barcode_scanner` - Provides TypeScript API documentation for Salesforce LWC Barcode Scanner, offering expert guidance for implementing barcode scanning features in Lightning Web Components.
228
- - `create_mobile_lwc_biometrics` - Provides TypeScript API documentation for Salesforce LWC Biometrics Service, offering expert guidance for implementing biometric authentication features in Lightning Web Components.
229
- - `create_mobile_lwc_calendar` - Provides TypeScript API documentation for Salesforce LWC Calendar Service, offering expert guidance for implementing calendar integration features in Lightning Web Components.
230
- - `create_mobile_lwc_contacts` - Provides TypeScript API documentation for Salesforce LWC Contacts Service, offering expert guidance for implementing contacts management features in Lightning Web Components.
231
- - `create_mobile_lwc_document_scanner` - Provides TypeScript API documentation for Salesforce LWC Document Scanner, offering expert guidance for implementing document scanning features in Lightning Web Components.
232
- - `create_mobile_lwc_geofencing` - Provides TypeScript API documentation for Salesforce LWC Geofencing Service, offering expert guidance for implementing geofencing features in Lightning Web Components.
233
- - `create_mobile_lwc_location` - Provides TypeScript API documentation for Salesforce LWC Location Service, offering expert guidance for implementing location services in Lightning Web Components.
234
- - `create_mobile_lwc_nfc` - Provides TypeScript API documentation for Salesforce LWC NFC Service, offering expert guidance for implementing NFC features in Lightning Web Components.
235
- - `create_mobile_lwc_payments` - Provides TypeScript API documentation for Salesforce LWC Payments Service, offering expert guidance for implementing payment processing features in Lightning Web Components.
236
- - `get_mobile_lwc_offline_analysis` - Analyzes Lightning Web Components for mobile-specific issues and provides detailed recommendations for mobile offline compatibility and performance improvements.
237
- - `get_mobile_lwc_offline_guidance` - Provides structured review instructions to detect and remediate mobile offline code violations in Lightning Web Components for Salesforce Mobile Apps.
226
+ For sample prompts that invoke the core DX MCP tools, see [Use the Core Salesforce DX MCP Tools](https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_mcp_use_core_tools.htm) in the _Salesforce DX Developer Guide_.
238
227
 
239
- ### Mobile-core Toolset
228
+ - `run_soql_query` (GA) - Runs a SOQL query against a Salesforce org.
240
229
 
241
- - `create_mobile_lwc_barcode_scanner` - Provides TypeScript API documentation for Salesforce LWC Barcode Scanner, offering expert guidance for implementing barcode scanning features in Lightning Web Components.
242
- - `create_mobile_lwc_biometrics` - Provides TypeScript API documentation for Salesforce LWC Biometrics Service, offering expert guidance for implementing biometric authentication features in Lightning Web Components.
243
- - `create_mobile_lwc_location` - Provides TypeScript API documentation for Salesforce LWC Location Service, offering expert guidance for implementing location services in Lightning Web Components.
244
- - `get_mobile_lwc_offline_analysis` - Analyzes Lightning Web Components for mobile-specific issues and provides detailed recommendations for mobile offline compatibility and performance improvements.
245
- - `get_mobile_lwc_offline_guidance` - Provides structured review instructions to detect and remediate mobile offline code violations in Lightning Web Components for Salesforce Mobile Apps.
230
+ ### DevOps Center Toolset
246
231
 
247
- ### Aura Experts Toolset
232
+ For complete documentation, see [Merge Conflict Resolution with DevOps Center MCP Tools (Managed Package)](https://help.salesforce.com/s/articleView?id=platform.devops_center_mcp_intro.htm&type=5) in Salesforce Help.
248
233
 
249
- - `create_aura_blueprint_draft` - (GA)
250
- Creates a comprehensive Product Requirements Document (PRD) blueprint for Aura component migration. Analyzes Aura component files and generates framework-agnostic specifications suitable for LWC migration, including business requirements, technical patterns, and migration guidelines.
234
+ - `check_devops_center_commit_status` (NON-GA) - Check the current status of a work item committed to DevOps Center.
235
+ - `checkout_devops_center_work_item` (NON-GA) - Checks out the branch associated with a selected work item by name.
236
+ - `commit_devops_center_work_item` (NON-GA) - Commit SFDX project changes and register the commit SHA in DevOps Center.
237
+ - `create_devops_center_pull_request` (NON-GA) - Commit local changes to a DevOps Center work item’s feature branch.
238
+ - `detect_devops_center_merge_conflict` (GA) - Detects merge conflicts for a selected work item or in a given source branch.
239
+ - `list_devops_center_projects` (NON-GA) - List all DevOps Center projects in a specific org.
240
+ - `list_devops_center_work_items` (NON-GA) - List all the work items for a specific DevOps Center project.
241
+ - `promote_devops_center_work_item` (NON-GA) - Promote an approved work item to the next stage in the DevOps Center pipeline.
242
+ - `resolve_devops_center_merge_conflict` (GA) - Apply a selected resolution method to a merge conflict.
251
243
 
252
- - `enhance_aura_blueprint_draft` - (GA)
253
- Enhances an existing draft PRD with expert analysis and unknown resolution. Takes a draft blueprint and applies specialized Aura expert knowledge to resolve dependencies, add technical insights, and improve the migration specifications for better LWC implementation guidance.
244
+ ### Enrichment Toolset
254
245
 
255
- - `transition_prd_to_lwc` - (GA)
256
- Provides migration bridge guidance for creating LWC components from Aura specifications. Takes the enhanced PRD and generates specific implementation guidance, platform service mappings, and step-by-step instructions for building the equivalent LWC component.
246
+ - `enrich_metadata` (NON-GA) - Enrich metadata from your org in your DX project.
257
247
 
258
- - `orchestrate_aura_migration` - (GA)
259
- Orchestrates the complete Aura to LWC migration workflow. Provides end-to-end guidance for the entire migration process, from initial analysis through final implementation, including best practices, tooling recommendations, and quality assurance steps.
248
+ ### Lightning Web Components (LWC) Experts Toolset
260
249
 
261
- ### Lwc Experts Toolset
250
+ For complete documentation, see [Use DX MCP Tools for LWC](https://developer.salesforce.com/docs/platform/lwc/guide/mcp-intro.html) in the _Lightning Web Components Developer Guide_.
262
251
 
263
252
  #### Component Development
264
253
 
265
- - `create_lwc_component_from_prd` - (GA) Creates complete LWC components from PRD specifications with proper structure and best practices
266
- - `create_lwc_jest_tests` - (GA) Generates comprehensive Jest test suites for LWC components with coverage and mocking
267
- - `review_lwc_jest_tests` - (GA) Reviews and validates Jest test implementations for LWC components
254
+ - `create_lwc_component_from_prd` (GA) - Creates complete LWC components from PRD specifications with proper structure. and best practices
255
+ - `create_lwc_jest_tests` (GA) - Generates Jest test suites for LWC components with coverage and mocking.
256
+ - `review_lwc_jest_tests` (GA) - Reviews and validates Jest test implementations for LWC components.
268
257
 
269
258
  #### Development Guidelines
270
259
 
271
- - `guide_lwc_accessibility` - (GA) Provides accessibility guidelines and testing instructions for LWC components
272
- - `guide_lwc_best_practices` - (GA) Offers LWC development best practices and coding standards guidance
273
- - `guide_lwc_development` - (GA) Comprehensive LWC development workflow and implementation guidelines
274
- - `guide_lwc_rtl_support` - (GA) Right-to-Left internationalization support and RTL development guidance
275
- - `guide_lwc_slds2_uplift_linter_fixes` - (NON-GA) Analyzes the given LWC code along with the slds-linter output to fix issues using the SLDS2 knowledge
276
- - `guide_lwc_security` - (GA) Comprehensive security analysis in accordance with Product Security Guidelines and Lightning Web Security Guidelines
277
- - `guide_design_general` - (GA) Comprehensive SLDS guidelines and best practices for Lightning Web Components with accessibility, responsive design, and component usage patterns
278
- - `guide_utam_generation` - (NON-GA) Provides UTAM Page Object generation guidelines and best practices.
279
- - `create_lightning_type` - (GA) Provides guidance for creating Custom Lightning Types (CLT) for Salesforce applications,
280
- * Einstein Agent actions, Lightning Web Components, and Lightning Platform integrations.
260
+ - `create_lightning_type` (GA) - Provides guidance for creating Custom Lightning Types (CLT) for Salesforce applications, agent actions, Lightning web components, and Lightning Platform integrations.
261
+ - `guide_lwc_accessibility` (GA) - Provides accessibility guidelines and testing instructions for LWC components.
262
+ - `guide_lwc_best_practices` (GA) - Offers LWC development best practices and coding standards guidance.
263
+ - `guide_lwc_development` (GA) - Provides LWC development workflow and implementation guidelines.
264
+ - `guide_lwc_rtl_support` (GA) - Provides Right-to-Left (RTL) internationalization support and RTL development guidance.
265
+ - `guide_lwc_slds2_uplift_linter_fixes` (NON-GA) - Analyzes the given LWC code along with the slds-linter output to fix issues using Salesforce Lightning Design System 2 (SLDS 2) guidelines.
266
+ - `guide_lwc_security` (GA) - Provides security analysis in accordance with product security guidelines and Lightning Web Security guidelines.
267
+ - `guide_design_general` (GA) - Provides SLDS guidelines and best practices for Lightning Web Components with accessibility, responsive design, and component usage patterns.
268
+ - `guide_utam_generation` (NON-GA) - Provides UI Test Automation Model (UTAM) Page Object generation guidelines and best practices.
269
+
270
+ #### Lightning Data Service (LDS) Tools
271
+
272
+ - `create_lds_graphql_mutation_query` (GA) - Provides guidance for creating GraphQL mutation queries.
273
+ - `create_lds_graphql_read_query` (GA) - Create GraphQL read queries for LDS.
274
+ - `explore_lds_graphql_schema` (GA) - Explore GraphQL schema structure for LDS.
275
+ - `explore_lds_uiapi` (GA) - Explores and documents Lightning Design System UI API capabilities.
276
+ - `guide_lds_data_consistency` (GA) - Provides data consistency patterns and best practices for LDS components.
277
+ - `guide_lds_development` (GA) - Provides LDS development guidelines and component integration.
278
+ - `guide_lds_graphql` (GA) - Provides LDS GraphQL usage patterns and guidelines.
279
+ - `guide_lds_referential_integrity` (GA) - Provides referential integrity patterns for LDS data management.
280
+ - `orchestrate_lds_data_requirements` (GA) - Provides step-by-step guidance for analyzing and clarifying LDS data requirements to produce PRD-ready specifications.
281
+
282
+ #### Migration & Integration Tools
283
+
284
+ - `guide_figma_to_lwc_conversion` (GA) - Converts Figma designs to LWC component specifications.
285
+ - `run_lwc_accessibility_jest_tests` (GA) - Provides accessibility testing utilities and Jest integration for LWC components.
286
+ - `verify_aura_migration_completeness` (GA) - Provides Aura to LWC migration completeness checklist and validation.
281
287
 
282
288
  #### Workflow Tools
283
289
 
284
- - `orchestrate_lwc_component_creation` - (GA) Step-by-step component creation workflow guidance
285
- - `orchestrate_lwc_component_optimization` - (GA) Performance optimization and best practices for LWC components
286
- - `orchestrate_lwc_component_testing` - (GA) Comprehensive testing workflow and test generation guidance
287
- - `orchestrate_lwc_slds2_uplift` - (NON-GA) Migration guidance for upgrading to SLDS2 design system
290
+ - `orchestrate_lwc_component_creation` (GA) - Provides guidance for the entire Aura-to-LWC migration process.
291
+ - `orchestrate_lwc_component_optimization` (GA) - Provides performance optimization and best practices for LWC components.
292
+ - `orchestrate_lwc_component_testing` (GA) - Provides comprehensive testing workflow and test generation guidance.
293
+ - `orchestrate_lwc_slds2_uplift` (NON-GA) - Provides migration guidance for upgrading to SLDS 2.
288
294
 
289
- #### LDS (Lightning Data Service) Tools
295
+ ### Metadata Toolset
290
296
 
291
- - `explore_lds_uiapi` - (GA) Explores and documents Lightning Data Service UI API capabilities
292
- - `guide_lds_data_consistency` - (GA) Data consistency patterns and best practices for LDS components
293
- - `guide_lds_development` - (GA) LDS development guidelines and component integration
294
- - `guide_lds_referential_integrity` - (GA) Referential integrity patterns for LDS data management
295
- - `orchestrate_lds_data_requirements` - (GA) Step-by-step guidance for analyzing and clarifying LDS data requirements to produce PRD-ready specifications.
296
- - `create_lds_graphql_read_query` - (GA) Create GraphQL read queries for LDS
297
- - `explore_lds_graphql_schema` - (GA) Explore GraphQL schema structure for Salesforce LDS
298
- - `guide_lds_graphql` - (GA) LDS GraphQL usage patterns and guidelines
299
- - `create_lds_graphql_mutation_query` - (GA) Comprehensive guidance text for creating GraphQL mutation queries.
297
+ For sample prompts that invoke the core DX MCP tools, see [Use the Core Salesforce DX MCP Tools](https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_mcp_use_core_tools.htm) in the _Salesforce DX Developer Guide_.
300
298
 
301
- #### Migration & Integration Tools
299
+ - `deploy_metadata` (GA) - Deploys metadata from your DX project to an org.
300
+ - `retrieve_metadata` (GA) - Retrieves metadata from your org to your DX project.
301
+
302
+ ### Mobile Toolset
303
+
304
+ For complete documentation, see [Use the mobile Toolset](https://developer.salesforce.com/docs/atlas.en-us.mobile_offline.meta/mobile_offline/dx_mobile_mcp_toolset_mobile.htm) in the _Mobile and Offline Developer Guide_.
305
+
306
+ - `create_mobile_lwc_app_review` (GA) - Provides TypeScript API documentation for Salesforce LWC App Review Service, offering expert guidance for implementing app review features in LWC components.
307
+ - `create_mobile_lwc_ar_space_capture` (GA) - Provides TypeScript API documentation for Salesforce LWC AR Space Capture, offering expert guidance for implementing AR space capture features in LWC components.
308
+ - `create_mobile_lwc_barcode_scanner` (GA) - Provides TypeScript API documentation for Salesforce LWC Barcode Scanner, offering expert guidance for implementing barcode scanning features in LWC components.
309
+ - `create_mobile_lwc_biometrics` (GA) - Provides TypeScript API documentation for Salesforce LWC Biometrics Service, offering expert guidance for implementing biometric authentication features in LWC components.
310
+ - `create_mobile_lwc_calendar` (GA) - Provides TypeScript API documentation for Salesforce LWC Calendar Service, offering expert guidance for implementing calendar integration features in LWC components.
311
+ - `create_mobile_lwc_contacts` (GA) - Provides TypeScript API documentation for Salesforce LWC Contacts Service, offering expert guidance for implementing contacts management features in LWC components.
312
+ - `create_mobile_lwc_document_scanner` (GA) - Provides TypeScript API documentation for Salesforce LWC Document Scanner, offering expert guidance for implementing document scanning features in LWC components.
313
+ - `create_mobile_lwc_geofencing` (GA) - Provides TypeScript API documentation for Salesforce LWC Geofencing Service, offering expert guidance for implementing geofencing features in LWC components.
314
+ - `create_mobile_lwc_location` (GA) - Provides TypeScript API documentation for Salesforce LWC Location Service, offering expert guidance for implementing location services in LWC components.
315
+ - `create_mobile_lwc_nfc` (GA) - Provides TypeScript API documentation for Salesforce LWC NFC Service, offering expert guidance for implementing NFC features in LWC components.
316
+ - `create_mobile_lwc_payments` - Provides TypeScript API documentation for Salesforce LWC Payments Service, offering expert guidance for implementing payment processing features in LWC components.
317
+ - `get_mobile_lwc_offline_analysis` (GA) - Analyzes LWC components for mobile-specific issues and provides detailed recommendations for mobile offline compatibility and performance improvements.
318
+ - `get_mobile_lwc_offline_guidance` (GA) - Provides structured review instructions to detect and remediate mobile offline code violations in LWC components for Salesforce mobile apps.
319
+
320
+ ### Mobile-core Toolset
321
+
322
+ For complete documentation, see [Use the mobile-core Toolset](https://developer.salesforce.com/docs/atlas.en-us.mobile_offline.meta/mobile_offline/dx_mobile_mcp_toolset_core.htm) in the _Mobile and Offline Developer Guide_.
323
+
324
+ - `create_mobile_lwc_barcode_scanner` (GA) - Provides TypeScript API documentation for Salesforce LWC Barcode Scanner, offering expert guidance for implementing barcode scanning features in LWC components.
325
+ - `create_mobile_lwc_biometrics` (GA) - Provides TypeScript API documentation for Salesforce LWC Biometrics Service, offering expert guidance for implementing biometric authentication features in LWC components.
326
+ - `create_mobile_lwc_location` (GA) - Provides TypeScript API documentation for Salesforce LWC Location Service, offering expert guidance for implementing location services in LWC components.
327
+ - `get_mobile_lwc_offline_analysis` (GA) - Analyzes LWC components for mobile-specific issues and provides detailed recommendations for mobile offline compatibility and performance improvements.
328
+ - `get_mobile_lwc_offline_guidance` (GA) - Provides structured review instructions to detect and remediate mobile offline code violations in LWC components for Salesforce mobile apps.
302
329
 
303
- - `verify_aura_migration_completeness` - (GA) Aura to LWC migration completeness checklist and validation
304
- - `guide_figma_to_lwc_conversion` - (GA) Converts Figma designs to LWC component specifications
305
- - `run_lwc_accessibility_jest_tests` - (GA) Accessibility testing utilities and Jest integration for LWC components
330
+ ### Orgs Toolset
306
331
 
307
- ### Code-Analysis Toolset
332
+ For sample prompts that invoke the core DX MCP tools, see [Use the Core Salesforce DX MCP Tools](https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_mcp_use_core_tools.htm) in the _Salesforce DX Developer Guide_.
308
333
 
309
- - `run_code_analyzer` - (NON-GA) Performs a static analysis of your code using Salesforce Code Analyzer. Includes validating that the code conforms to best practices, checking for security vulnerabilities, and identifying possible performance issues.
310
- - `describe_code_analyzer_rule` - (NON-GA) Gets the description of a Salesforce Code Analyzer rule, including the engine it belongs to, its severity, and associated tags.
334
+ - `create_org_snapshot` (NON-GA) - Create a scratch org snapshot.
335
+ - `create_scratch_org` (NON-GA) - Create a scratch org.
336
+ - `delete_org` (NON-GA) - Delete a locally-authorized Salesforce scratch org or sandbox.
337
+ - `list_all_orgs` (GA) - List all configured Salesforce orgs, with optional connection status checking.
338
+ - `open_org` (NON-GA) - Open an org in a browser.
311
339
 
312
340
  ### Scale Products Toolset
313
341
 
314
- - `scan_apex_class_for_antipatterns` - (NON-GA) Analyzes Apex class files for performance antipatterns and provides recommendations for fixing them. Currently detects: (1) Schema.getGlobalDescribe() usage with optimized alternatives, (2) SOQL queries without WHERE or LIMIT clauses, (3) SOQL queries with unused fields (with fix generation). Distinguishes between different severity levels (e.g., usage in loops vs. ordinary usage). Requires an absolute path to the Apex class file.
342
+ For complete documentation, see the [README](./packages/mcp-provider-scale-products/README.md) in the `mcp-provider-scale-products` subdirectory.
315
343
 
316
- ### Enrichment Toolset
344
+ - `scan_apex_class_for_antipatterns` - (GA) Analyzes Apex class files for performance antipatterns and provides recommendations for fixing them.
345
+
346
+ ### Testing Toolset
347
+
348
+ For sample prompts that invoke the core DX MCP tools, see [Use the Core Salesforce DX MCP Tools](https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_mcp_use_core_tools.htm) in the _Salesforce DX Developer Guide_.
349
+
350
+ - `run_agent_test` (GA) - Executes agent tests in your org.
351
+ - `run_apex_test` (GA) - Executes Apex tests in your org.
352
+
353
+ ### Users Toolset
317
354
 
318
- - `enrich_metadata` - (NON-GA) Enrich metadata from your org in your DX project.
355
+ For sample prompts that invoke the core DX MCP tools, see [Use the Core Salesforce DX MCP Tools](https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_mcp_use_core_tools.htm) in the _Salesforce DX Developer Guide_.
319
356
 
320
- </details>
357
+ - `assign_permission_set` (GA) - Assigns a permission set to the user or on behalf of another user.
@@ -1,12 +1,12 @@
1
1
  {
2
2
  "name": "@salesforce/mcp",
3
- "version": "0.26.5",
3
+ "version": "0.26.7",
4
4
  "lockfileVersion": 3,
5
5
  "requires": true,
6
6
  "packages": {
7
7
  "": {
8
8
  "name": "@salesforce/mcp",
9
- "version": "0.26.5",
9
+ "version": "0.26.7",
10
10
  "license": "Apache-2.0",
11
11
  "dependencies": {
12
12
  "@modelcontextprotocol/sdk": "^1.18.0",
@@ -18,8 +18,8 @@
18
18
  "@salesforce/mcp-provider-api": "0.5.0",
19
19
  "@salesforce/mcp-provider-aura-experts": "0.3.6",
20
20
  "@salesforce/mcp-provider-code-analyzer": "0.5.2",
21
- "@salesforce/mcp-provider-devops": "0.1.9",
22
- "@salesforce/mcp-provider-dx-core": "0.7.0",
21
+ "@salesforce/mcp-provider-devops": "0.2.0",
22
+ "@salesforce/mcp-provider-dx-core": "0.8.0",
23
23
  "@salesforce/mcp-provider-lwc-experts": "0.6.5",
24
24
  "@salesforce/mcp-provider-metadata-enrichment": "0.0.4",
25
25
  "@salesforce/mcp-provider-mobile-web": "0.2.2",
@@ -313,9 +313,9 @@
313
313
  }
314
314
  },
315
315
  "node_modules/@aws-sdk/client-cloudfront": {
316
- "version": "3.993.0",
317
- "resolved": "https://registry.npmjs.org/@aws-sdk/client-cloudfront/-/client-cloudfront-3.993.0.tgz",
318
- "integrity": "sha512-8jCdRFDWJSyeAtAMuynUPy+3Bz9aRaunxhUluxCK9aLCadj9J19mvxsMHvdumObeYam4NYVi2GYVs8GFZ0ET1g==",
316
+ "version": "3.994.0",
317
+ "resolved": "https://registry.npmjs.org/@aws-sdk/client-cloudfront/-/client-cloudfront-3.994.0.tgz",
318
+ "integrity": "sha512-43NqYL+JjPY38qVc1rjVQna3FNEO484AkQXAqBJByI7PIzURtrtSWv42PstI99t/GnGlZFikf72y+iclvz32pQ==",
319
319
  "dev": true,
320
320
  "license": "Apache-2.0",
321
321
  "dependencies": {
@@ -329,7 +329,7 @@
329
329
  "@aws-sdk/middleware-user-agent": "^3.972.11",
330
330
  "@aws-sdk/region-config-resolver": "^3.972.3",
331
331
  "@aws-sdk/types": "^3.973.1",
332
- "@aws-sdk/util-endpoints": "3.993.0",
332
+ "@aws-sdk/util-endpoints": "3.994.0",
333
333
  "@aws-sdk/util-user-agent-browser": "^3.972.3",
334
334
  "@aws-sdk/util-user-agent-node": "^3.972.9",
335
335
  "@smithy/config-resolver": "^4.4.6",
@@ -366,9 +366,9 @@
366
366
  }
367
367
  },
368
368
  "node_modules/@aws-sdk/client-s3": {
369
- "version": "3.993.0",
370
- "resolved": "https://registry.npmjs.org/@aws-sdk/client-s3/-/client-s3-3.993.0.tgz",
371
- "integrity": "sha512-0slCxdbo9O3rfzqD7/PsBOrZ6vcwFzPAvGeUu5NZApI5WyjEfMLLi2T9QW8R9N9TQeUfiUQiHkg/NV0LPS61/g==",
369
+ "version": "3.994.0",
370
+ "resolved": "https://registry.npmjs.org/@aws-sdk/client-s3/-/client-s3-3.994.0.tgz",
371
+ "integrity": "sha512-zIVQt/XfE2zTFrcPEf8R+KRaRD1++XHMPRhxXM2kVA6NA6Aq/cFCUyYOYYwSbWLF/XeToaX1auYGn3IoZKruPQ==",
372
372
  "dev": true,
373
373
  "license": "Apache-2.0",
374
374
  "dependencies": {
@@ -388,9 +388,9 @@
388
388
  "@aws-sdk/middleware-ssec": "^3.972.3",
389
389
  "@aws-sdk/middleware-user-agent": "^3.972.11",
390
390
  "@aws-sdk/region-config-resolver": "^3.972.3",
391
- "@aws-sdk/signature-v4-multi-region": "3.993.0",
391
+ "@aws-sdk/signature-v4-multi-region": "3.994.0",
392
392
  "@aws-sdk/types": "^3.973.1",
393
- "@aws-sdk/util-endpoints": "3.993.0",
393
+ "@aws-sdk/util-endpoints": "3.994.0",
394
394
  "@aws-sdk/util-user-agent-browser": "^3.972.3",
395
395
  "@aws-sdk/util-user-agent-node": "^3.972.9",
396
396
  "@smithy/config-resolver": "^4.4.6",
@@ -482,6 +482,23 @@
482
482
  "node": ">=20.0.0"
483
483
  }
484
484
  },
485
+ "node_modules/@aws-sdk/client-sso/node_modules/@aws-sdk/util-endpoints": {
486
+ "version": "3.993.0",
487
+ "resolved": "https://registry.npmjs.org/@aws-sdk/util-endpoints/-/util-endpoints-3.993.0.tgz",
488
+ "integrity": "sha512-j6vioBeRZ4eHX4SWGvGPpwGg/xSOcK7f1GL0VM+rdf3ZFTIsUEhCFmD78B+5r2PgztcECSzEfvHQX01k8dPQPw==",
489
+ "dev": true,
490
+ "license": "Apache-2.0",
491
+ "dependencies": {
492
+ "@aws-sdk/types": "^3.973.1",
493
+ "@smithy/types": "^4.12.0",
494
+ "@smithy/url-parser": "^4.2.8",
495
+ "@smithy/util-endpoints": "^3.2.8",
496
+ "tslib": "^2.6.2"
497
+ },
498
+ "engines": {
499
+ "node": ">=20.0.0"
500
+ }
501
+ },
485
502
  "node_modules/@aws-sdk/core": {
486
503
  "version": "3.973.11",
487
504
  "resolved": "https://registry.npmjs.org/@aws-sdk/core/-/core-3.973.11.tgz",
@@ -871,6 +888,23 @@
871
888
  "node": ">=20.0.0"
872
889
  }
873
890
  },
891
+ "node_modules/@aws-sdk/middleware-user-agent/node_modules/@aws-sdk/util-endpoints": {
892
+ "version": "3.993.0",
893
+ "resolved": "https://registry.npmjs.org/@aws-sdk/util-endpoints/-/util-endpoints-3.993.0.tgz",
894
+ "integrity": "sha512-j6vioBeRZ4eHX4SWGvGPpwGg/xSOcK7f1GL0VM+rdf3ZFTIsUEhCFmD78B+5r2PgztcECSzEfvHQX01k8dPQPw==",
895
+ "dev": true,
896
+ "license": "Apache-2.0",
897
+ "dependencies": {
898
+ "@aws-sdk/types": "^3.973.1",
899
+ "@smithy/types": "^4.12.0",
900
+ "@smithy/url-parser": "^4.2.8",
901
+ "@smithy/util-endpoints": "^3.2.8",
902
+ "tslib": "^2.6.2"
903
+ },
904
+ "engines": {
905
+ "node": ">=20.0.0"
906
+ }
907
+ },
874
908
  "node_modules/@aws-sdk/nested-clients": {
875
909
  "version": "3.993.0",
876
910
  "resolved": "https://registry.npmjs.org/@aws-sdk/nested-clients/-/nested-clients-3.993.0.tgz",
@@ -921,6 +955,23 @@
921
955
  "node": ">=20.0.0"
922
956
  }
923
957
  },
958
+ "node_modules/@aws-sdk/nested-clients/node_modules/@aws-sdk/util-endpoints": {
959
+ "version": "3.993.0",
960
+ "resolved": "https://registry.npmjs.org/@aws-sdk/util-endpoints/-/util-endpoints-3.993.0.tgz",
961
+ "integrity": "sha512-j6vioBeRZ4eHX4SWGvGPpwGg/xSOcK7f1GL0VM+rdf3ZFTIsUEhCFmD78B+5r2PgztcECSzEfvHQX01k8dPQPw==",
962
+ "dev": true,
963
+ "license": "Apache-2.0",
964
+ "dependencies": {
965
+ "@aws-sdk/types": "^3.973.1",
966
+ "@smithy/types": "^4.12.0",
967
+ "@smithy/url-parser": "^4.2.8",
968
+ "@smithy/util-endpoints": "^3.2.8",
969
+ "tslib": "^2.6.2"
970
+ },
971
+ "engines": {
972
+ "node": ">=20.0.0"
973
+ }
974
+ },
924
975
  "node_modules/@aws-sdk/region-config-resolver": {
925
976
  "version": "3.972.3",
926
977
  "resolved": "https://registry.npmjs.org/@aws-sdk/region-config-resolver/-/region-config-resolver-3.972.3.tgz",
@@ -939,9 +990,9 @@
939
990
  }
940
991
  },
941
992
  "node_modules/@aws-sdk/signature-v4-multi-region": {
942
- "version": "3.993.0",
943
- "resolved": "https://registry.npmjs.org/@aws-sdk/signature-v4-multi-region/-/signature-v4-multi-region-3.993.0.tgz",
944
- "integrity": "sha512-6l20k27TJdqTozJOm+s20/1XDey3aj+yaeIdbtqXuYNhQiWHajvYThcI1sHx2I1W4NelZTOmYEF+dj1mya01eg==",
993
+ "version": "3.994.0",
994
+ "resolved": "https://registry.npmjs.org/@aws-sdk/signature-v4-multi-region/-/signature-v4-multi-region-3.994.0.tgz",
995
+ "integrity": "sha512-8y04Lv497KKd7f2TVlm2RaKQaNfnY17ZH8d3m+7sW/3R3BhZvHgWQZyqTb/vcN2ERz1YAnWx6woJyB3ZNFvakw==",
945
996
  "dev": true,
946
997
  "license": "Apache-2.0",
947
998
  "dependencies": {
@@ -1003,9 +1054,9 @@
1003
1054
  }
1004
1055
  },
1005
1056
  "node_modules/@aws-sdk/util-endpoints": {
1006
- "version": "3.993.0",
1007
- "resolved": "https://registry.npmjs.org/@aws-sdk/util-endpoints/-/util-endpoints-3.993.0.tgz",
1008
- "integrity": "sha512-j6vioBeRZ4eHX4SWGvGPpwGg/xSOcK7f1GL0VM+rdf3ZFTIsUEhCFmD78B+5r2PgztcECSzEfvHQX01k8dPQPw==",
1057
+ "version": "3.994.0",
1058
+ "resolved": "https://registry.npmjs.org/@aws-sdk/util-endpoints/-/util-endpoints-3.994.0.tgz",
1059
+ "integrity": "sha512-L2obUBw4ACMMd1F/SG5LdfPyZ0xJNs9Maifwr3w0uWO+4YvHmk9FfRskfSfE/SLZ9S387oSZ+1xiP7BfVCP/Og==",
1009
1060
  "dev": true,
1010
1061
  "license": "Apache-2.0",
1011
1062
  "dependencies": {
@@ -6472,15 +6523,15 @@
6472
6523
  }
6473
6524
  },
6474
6525
  "node_modules/@salesforce/mcp-provider-devops": {
6475
- "version": "0.1.9",
6476
- "resolved": "https://registry.npmjs.org/@salesforce/mcp-provider-devops/-/mcp-provider-devops-0.1.9.tgz",
6477
- "integrity": "sha512-tWI3TS+QX0UC6jyQlQ3jXKqeti5v+wfsd2y757W+k5IkA+QWZ0MkOe1JjGB9uE6jDj00/5hAEvDhxm2gOhJXvA==",
6526
+ "version": "0.2.0",
6527
+ "resolved": "https://registry.npmjs.org/@salesforce/mcp-provider-devops/-/mcp-provider-devops-0.2.0.tgz",
6528
+ "integrity": "sha512-wEdDTrTEMqdmezPCCaHBx6HgXqUn70YTIasRD1lpY5RDYQtDsbKblVSHd6xCMCL6Pjsd5CoqfJgEuSDrbVh1Kg==",
6478
6529
  "license": "Apache-2.0",
6479
6530
  "dependencies": {
6480
6531
  "@modelcontextprotocol/sdk": "^1.18.0",
6481
- "@salesforce/core": "^8.17.0",
6482
- "@salesforce/mcp-provider-api": "^0.4.0",
6483
- "@salesforce/source-deploy-retrieve": "^12.22.13",
6532
+ "@salesforce/core": "^8.24.3",
6533
+ "@salesforce/mcp-provider-api": "^0.4.1",
6534
+ "@salesforce/source-deploy-retrieve": "^12.31.7",
6484
6535
  "@salesforce/ts-types": "^2.0.12",
6485
6536
  "axios": "^1.10.0",
6486
6537
  "zod": "^3.25.76"
@@ -6501,9 +6552,9 @@
6501
6552
  }
6502
6553
  },
6503
6554
  "node_modules/@salesforce/mcp-provider-dx-core": {
6504
- "version": "0.7.0",
6505
- "resolved": "https://registry.npmjs.org/@salesforce/mcp-provider-dx-core/-/mcp-provider-dx-core-0.7.0.tgz",
6506
- "integrity": "sha512-5VbqefBzzZcBdR4kOmpvre2xnB0i3IAThp7HgfCCnn2akXhHOEc3QtPp8DAGYS9shva1q2SYweGpau7jPcDwLg==",
6555
+ "version": "0.8.0",
6556
+ "resolved": "https://registry.npmjs.org/@salesforce/mcp-provider-dx-core/-/mcp-provider-dx-core-0.8.0.tgz",
6557
+ "integrity": "sha512-aGfHDBLYPlJJixIPnl9i9N+TohRKf6FE/4CAXj3aJ11UFyXpGDuu19aW2mG6tt+POBDPTOUBA40VNIZzP0Woqw==",
6507
6558
  "license": "Apache-2.0",
6508
6559
  "dependencies": {
6509
6560
  "@modelcontextprotocol/sdk": "^1.18.0",
@@ -6582,6 +6633,39 @@
6582
6633
  "zod": "^3.25.76"
6583
6634
  }
6584
6635
  },
6636
+ "node_modules/@salesforce/mcp-provider-metadata-enrichment/node_modules/@salesforce/mcp-provider-dx-core": {
6637
+ "version": "0.7.0",
6638
+ "resolved": "https://registry.npmjs.org/@salesforce/mcp-provider-dx-core/-/mcp-provider-dx-core-0.7.0.tgz",
6639
+ "integrity": "sha512-5VbqefBzzZcBdR4kOmpvre2xnB0i3IAThp7HgfCCnn2akXhHOEc3QtPp8DAGYS9shva1q2SYweGpau7jPcDwLg==",
6640
+ "license": "Apache-2.0",
6641
+ "dependencies": {
6642
+ "@modelcontextprotocol/sdk": "^1.18.0",
6643
+ "@salesforce/agents": "^0.15.4",
6644
+ "@salesforce/apex-node": "^8.2.1",
6645
+ "@salesforce/core": "^8.24.3",
6646
+ "@salesforce/kit": "^3.1.6",
6647
+ "@salesforce/mcp-provider-api": "^0.4.1",
6648
+ "@salesforce/source-deploy-retrieve": "^12.31.8",
6649
+ "@salesforce/source-tracking": "^7.8.2",
6650
+ "@salesforce/ts-types": "^2.0.11",
6651
+ "open": "^10.1.2",
6652
+ "zod": "^3.25.76"
6653
+ }
6654
+ },
6655
+ "node_modules/@salesforce/mcp-provider-metadata-enrichment/node_modules/@salesforce/mcp-provider-dx-core/node_modules/@salesforce/mcp-provider-api": {
6656
+ "version": "0.4.1",
6657
+ "resolved": "https://registry.npmjs.org/@salesforce/mcp-provider-api/-/mcp-provider-api-0.4.1.tgz",
6658
+ "integrity": "sha512-+e+xIEqfgNSETnn8Mv0jlto3q3MDX5V781ijrm5irwcZn9QmXPRBVDmVvByKHi8gDhDh9Wm5hzCcinTqtUaAcg==",
6659
+ "license": "Apache-2.0",
6660
+ "dependencies": {
6661
+ "@modelcontextprotocol/sdk": "^1.18.0",
6662
+ "@salesforce/core": "^8",
6663
+ "@salesforce/ts-types": "^2",
6664
+ "@types/semver": "^7.7.1",
6665
+ "semver": "^7.7.2",
6666
+ "zod": "^3.25.76"
6667
+ }
6668
+ },
6585
6669
  "node_modules/@salesforce/mcp-provider-mobile-web": {
6586
6670
  "version": "0.2.2",
6587
6671
  "resolved": "https://registry.npmjs.org/@salesforce/mcp-provider-mobile-web/-/mcp-provider-mobile-web-0.2.2.tgz",
@@ -6952,9 +7036,9 @@
6952
7036
  "license": "ISC"
6953
7037
  },
6954
7038
  "node_modules/@salesforce/source-deploy-retrieve": {
6955
- "version": "12.31.13",
6956
- "resolved": "https://registry.npmjs.org/@salesforce/source-deploy-retrieve/-/source-deploy-retrieve-12.31.13.tgz",
6957
- "integrity": "sha512-TgvUGBd2NacIDQH1L+QXLJtGQ+etOQ443CH892B90kxRkQL5QtuzqPCPUgO+WXlmZjdIciHLStRi+uTSy1UeUA==",
7039
+ "version": "12.31.14",
7040
+ "resolved": "https://registry.npmjs.org/@salesforce/source-deploy-retrieve/-/source-deploy-retrieve-12.31.14.tgz",
7041
+ "integrity": "sha512-tLnTCG6t+d+MN8pGijF6nL4lsqE37FaBINZZvyd+IDAw+7eWffFqIXK/nNyQ1ZARTNeHOs5K/NlNXNBp5+x/YQ==",
6958
7042
  "license": "Apache-2.0",
6959
7043
  "dependencies": {
6960
7044
  "@salesforce/core": "^8.26.2",
@@ -6962,7 +7046,7 @@
6962
7046
  "@salesforce/ts-types": "^2.0.12",
6963
7047
  "@salesforce/types": "^1.6.0",
6964
7048
  "fast-levenshtein": "^3.0.0",
6965
- "fast-xml-parser": "^5.3.4",
7049
+ "fast-xml-parser": "^5.3.6",
6966
7050
  "got": "^11.8.6",
6967
7051
  "graceful-fs": "^4.2.11",
6968
7052
  "ignore": "^5.3.2",
@@ -7082,9 +7166,9 @@
7082
7166
  }
7083
7167
  },
7084
7168
  "node_modules/@salesforce/types": {
7085
- "version": "1.6.0",
7086
- "resolved": "https://registry.npmjs.org/@salesforce/types/-/types-1.6.0.tgz",
7087
- "integrity": "sha512-UHk1L3QRaa3WfIqQn5RLmcZmxErXvpFPUteLLgIxlFLrxhcKevvEwkMJF2xNIHpfT4Xj7PcYvqtrRYapX4Pp+A==",
7169
+ "version": "1.7.1",
7170
+ "resolved": "https://registry.npmjs.org/@salesforce/types/-/types-1.7.1.tgz",
7171
+ "integrity": "sha512-PyV3ZyZum8bjO1LByNXWCSOGt1b9X9x2knIiFWgnYTsHmLK8OP+f6i+wPh4qu1e8+Zr+hNV0rTKVP8p/kCGqyQ==",
7088
7172
  "license": "BSD-3-Clause",
7089
7173
  "engines": {
7090
7174
  "node": ">=18"
@@ -8484,9 +8568,9 @@
8484
8568
  }
8485
8569
  },
8486
8570
  "node_modules/acorn-walk": {
8487
- "version": "8.3.4",
8488
- "resolved": "https://registry.npmjs.org/acorn-walk/-/acorn-walk-8.3.4.tgz",
8489
- "integrity": "sha512-ueEepnujpqee2o5aIYnvHU6C0A42MNdsIDeqy5BydrkuC5R1ZuUFnm27EeFJGoEHJQgn3uleRvmTXaJgfXbt4g==",
8571
+ "version": "8.3.5",
8572
+ "resolved": "https://registry.npmjs.org/acorn-walk/-/acorn-walk-8.3.5.tgz",
8573
+ "integrity": "sha512-HEHNfbars9v4pgpW6SO1KSPkfoS0xVOM/9UzkJltjlsHZmJasxg8aXkuZa7SMf8vKGIBhpUsPluQSqhJFCqebw==",
8490
8574
  "dev": true,
8491
8575
  "license": "MIT",
8492
8576
  "dependencies": {
@@ -9035,12 +9119,15 @@
9035
9119
  }
9036
9120
  },
9037
9121
  "node_modules/baseline-browser-mapping": {
9038
- "version": "2.9.19",
9039
- "resolved": "https://registry.npmjs.org/baseline-browser-mapping/-/baseline-browser-mapping-2.9.19.tgz",
9040
- "integrity": "sha512-ipDqC8FrAl/76p2SSWKSI+H9tFwm7vYqXQrItCuiVPt26Km0jS+NzSsBWAaBusvSbQcfJG+JitdMm+wZAgTYqg==",
9122
+ "version": "2.10.0",
9123
+ "resolved": "https://registry.npmjs.org/baseline-browser-mapping/-/baseline-browser-mapping-2.10.0.tgz",
9124
+ "integrity": "sha512-lIyg0szRfYbiy67j9KN8IyeD7q7hcmqnJ1ddWmNt19ItGpNN64mnllmxUNFIOdOm6by97jlL6wfpTTJrmnjWAA==",
9041
9125
  "license": "Apache-2.0",
9042
9126
  "bin": {
9043
- "baseline-browser-mapping": "dist/cli.js"
9127
+ "baseline-browser-mapping": "dist/cli.cjs"
9128
+ },
9129
+ "engines": {
9130
+ "node": ">=6.0.0"
9044
9131
  }
9045
9132
  },
9046
9133
  "node_modules/basic-ftp": {
@@ -12498,16 +12585,16 @@
12498
12585
  }
12499
12586
  },
12500
12587
  "node_modules/glob/node_modules/minimatch": {
12501
- "version": "10.2.1",
12502
- "resolved": "https://registry.npmjs.org/minimatch/-/minimatch-10.2.1.tgz",
12503
- "integrity": "sha512-MClCe8IL5nRRmawL6ib/eT4oLyeKMGCghibcDWK+J0hh0Q8kqSdia6BvbRMVk6mPa6WqUa5uR2oxt6C5jd533A==",
12588
+ "version": "10.2.2",
12589
+ "resolved": "https://registry.npmjs.org/minimatch/-/minimatch-10.2.2.tgz",
12590
+ "integrity": "sha512-+G4CpNBxa5MprY+04MbgOw1v7So6n5JY166pFi9KfYwT78fxScCeSNQSNzp6dpPSW2rONOps6Ocam1wFhCgoVw==",
12504
12591
  "dev": true,
12505
12592
  "license": "BlueOak-1.0.0",
12506
12593
  "dependencies": {
12507
12594
  "brace-expansion": "^5.0.2"
12508
12595
  },
12509
12596
  "engines": {
12510
- "node": "20 || >=22"
12597
+ "node": "18 || 20 || >=22"
12511
12598
  },
12512
12599
  "funding": {
12513
12600
  "url": "https://github.com/sponsors/isaacs"
@@ -12757,9 +12844,9 @@
12757
12844
  }
12758
12845
  },
12759
12846
  "node_modules/hashery": {
12760
- "version": "1.4.0",
12761
- "resolved": "https://registry.npmjs.org/hashery/-/hashery-1.4.0.tgz",
12762
- "integrity": "sha512-Wn2i1In6XFxl8Az55kkgnFRiAlIAushzh26PTjL2AKtQcEfXrcLa7Hn5QOWGZEf3LU057P9TwwZjFyxfS1VuvQ==",
12847
+ "version": "1.5.0",
12848
+ "resolved": "https://registry.npmjs.org/hashery/-/hashery-1.5.0.tgz",
12849
+ "integrity": "sha512-nhQ6ExaOIqti2FDWoEMWARUqIKyjr2VcZzXShrI+A3zpeiuPWzx6iPftt44LhP74E5sW36B75N6VHbvRtpvO6Q==",
12763
12850
  "license": "MIT",
12764
12851
  "dependencies": {
12765
12852
  "hookified": "^1.14.0"
@@ -12806,9 +12893,9 @@
12806
12893
  "license": "MIT"
12807
12894
  },
12808
12895
  "node_modules/hono": {
12809
- "version": "4.11.10",
12810
- "resolved": "https://registry.npmjs.org/hono/-/hono-4.11.10.tgz",
12811
- "integrity": "sha512-kyWP5PAiMooEvGrA9jcD3IXF7ATu8+o7B3KCbPXid5se52NPqnOpM/r9qeW2heMnOekF4kqR1fXJqCYeCLKrZg==",
12896
+ "version": "4.12.0",
12897
+ "resolved": "https://registry.npmjs.org/hono/-/hono-4.12.0.tgz",
12898
+ "integrity": "sha512-NekXntS5M94pUfiVZ8oXXK/kkri+5WpX2/Ik+LVsl+uvw+soj4roXIsPqO+XsWrAw20mOzaXOZf3Q7PfB9A/IA==",
12812
12899
  "license": "MIT",
12813
12900
  "peer": true,
12814
12901
  "engines": {
@@ -14731,11 +14818,11 @@
14731
14818
  }
14732
14819
  },
14733
14820
  "node_modules/minipass": {
14734
- "version": "7.1.2",
14735
- "resolved": "https://registry.npmjs.org/minipass/-/minipass-7.1.2.tgz",
14736
- "integrity": "sha512-qOOzS1cBTWYF4BH8fVePDBOO9iptMnGUEZwNc/cMWnTV2nVLZ7VoNWEPHkYczZA0pdoA7dl6e7FL659nX9S2aw==",
14821
+ "version": "7.1.3",
14822
+ "resolved": "https://registry.npmjs.org/minipass/-/minipass-7.1.3.tgz",
14823
+ "integrity": "sha512-tEBHqDnIoM/1rXME1zgka9g6Q2lcoCkxHLuc7ODJ5BxbP5d4c2Z5cGgtXAku59200Cx7diuHTOYfSBD8n6mm8A==",
14737
14824
  "dev": true,
14738
- "license": "ISC",
14825
+ "license": "BlueOak-1.0.0",
14739
14826
  "engines": {
14740
14827
  "node": ">=16 || 14 >=14.17"
14741
14828
  }
@@ -16119,9 +16206,9 @@
16119
16206
  "license": "MIT"
16120
16207
  },
16121
16208
  "node_modules/path-scurry": {
16122
- "version": "2.0.1",
16123
- "resolved": "https://registry.npmjs.org/path-scurry/-/path-scurry-2.0.1.tgz",
16124
- "integrity": "sha512-oWyT4gICAu+kaA7QWk/jvCHWarMKNs6pXOGWKDTr7cw4IGcUbW+PeTfbaQiLGheFRpjo6O9J0PmyMfQPjH71oA==",
16209
+ "version": "2.0.2",
16210
+ "resolved": "https://registry.npmjs.org/path-scurry/-/path-scurry-2.0.2.tgz",
16211
+ "integrity": "sha512-3O/iVVsJAPsOnpwWIeD+d6z/7PmqApyQePUtCndjatj/9I5LylHvt5qluFaBT3I5h3r1ejfR056c+FCv+NnNXg==",
16125
16212
  "dev": true,
16126
16213
  "license": "BlueOak-1.0.0",
16127
16214
  "dependencies": {
@@ -16129,7 +16216,7 @@
16129
16216
  "minipass": "^7.1.2"
16130
16217
  },
16131
16218
  "engines": {
16132
- "node": "20 || >=22"
16219
+ "node": "18 || 20 || >=22"
16133
16220
  },
16134
16221
  "funding": {
16135
16222
  "url": "https://github.com/sponsors/isaacs"
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@salesforce/mcp",
3
- "version": "0.26.5",
3
+ "version": "0.26.7",
4
4
  "description": "MCP Server for interacting with Salesforce instances",
5
5
  "bin": {
6
6
  "sf-mcp-server": "bin/run.js"
@@ -45,12 +45,12 @@
45
45
  "@salesforce/core": "^8.24.3",
46
46
  "@salesforce/kit": "^3.1.6",
47
47
  "@salesforce/mcp-provider-api": "0.5.0",
48
- "@salesforce/mcp-provider-dx-core": "0.7.0",
48
+ "@salesforce/mcp-provider-dx-core": "0.8.0",
49
49
  "@salesforce/mcp-provider-code-analyzer": "0.5.2",
50
50
  "@salesforce/mcp-provider-lwc-experts": "0.6.5",
51
51
  "@salesforce/mcp-provider-aura-experts": "0.3.6",
52
52
  "@salesforce/mcp-provider-mobile-web": "0.2.2",
53
- "@salesforce/mcp-provider-devops": "0.1.9",
53
+ "@salesforce/mcp-provider-devops": "0.2.0",
54
54
  "@salesforce/mcp-provider-scale-products": "0.0.4",
55
55
  "@salesforce/mcp-provider-metadata-enrichment": "0.0.4",
56
56
  "@salesforce/source-deploy-retrieve": "^12.31.7",