@salesforce/mcp 0.29.1 → 0.29.3
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.
- package/README.md +6 -3
- package/npm-shrinkwrap.json +593 -633
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -209,10 +209,12 @@ For complete documentation, see [Use the Aura-to-LWC Migration Tools](https://de
|
|
|
209
209
|
|
|
210
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_.
|
|
211
211
|
|
|
212
|
-
- `
|
|
213
|
-
- `
|
|
212
|
+
- `create-custom-rule` (NON-GA) - Creates a custom XPath-based PMD rule from a provided Apex code sample.
|
|
213
|
+
- `describe_code_analyzer_rule` (GA) - Gets the description of a Code Analyzer rule.
|
|
214
|
+
- `generate_xpath_prompt` (NON-GA) - Builds the prompt that guides XPath authoring from AST context. Invoked when creating an XPath-based PMD custom rule.
|
|
215
|
+
- `list_code_analyzer_rules` (GA) - Selects Code Analyzer rules based on a number of criteria.
|
|
214
216
|
- `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) -
|
|
217
|
+
- `run_code_analyzer` (GA) - Performs a 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.
|
|
216
218
|
|
|
217
219
|
### Core Toolset (always enabled)
|
|
218
220
|
|
|
@@ -239,6 +241,7 @@ For complete documentation, see [Merge Conflict Resolution with DevOps Center MC
|
|
|
239
241
|
- `list_devops_center_projects` (NON-GA) - List all DevOps Center projects in a specific org.
|
|
240
242
|
- `list_devops_center_work_items` (NON-GA) - List all the work items for a specific DevOps Center project.
|
|
241
243
|
- `promote_devops_center_work_item` (NON-GA) - Promote an approved work item to the next stage in the DevOps Center pipeline.
|
|
244
|
+
- `resolve_devops_center_deployment_failure` (NON-GA) - Diagnose and resolve deployment failures.
|
|
242
245
|
- `resolve_devops_center_merge_conflict` (GA) - Apply a selected resolution method to a merge conflict.
|
|
243
246
|
|
|
244
247
|
### Enrichment Toolset
|