@W-23122929@ - feat: delete enrich_metadata MCP tool and its provider package#470
Open
kumar-aman2-general wants to merge 1 commit into
Open
Conversation
… package Retire the NON-GA enrich_metadata MCP tool in favor of the sanctioned portable Skill migration target, and delete the 1:1 provider package that existed solely to ship it. - Delete packages/mcp-provider-metadata-enrichment/ in its entirety - Remove EnrichMetadataMcpProvider from MCP_PROVIDER_REGISTRY - Drop @salesforce/mcp-provider-metadata-enrichment dependency from @salesforce/mcp - Remove package from CODEOWNERS and both publish workflows - Remove the Enrichment Toolset section from the README Verified: @salesforce/mcp builds and all tests pass; no remaining references to the package, provider, tool, or Toolset.ENRICHMENT. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Thanks for the contribution! It looks like @kumar-aman2-general is an internal user so signing the CLA is not required. However, we need to confirm this. |
3 tasks
ShipraShreyasi
approved these changes
Jul 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What & Why
Retires the NON-GA
enrich_metadataMCP tool in favor of the sanctioned portable Skill (the migration target), and deletes the 1:1 provider package that existed solely to ship it. Resolves W-23122929.Changes
packages/mcp-provider-metadata-enrichment/package (src/index.ts,src/provider.ts,src/tools/enrich_metadata.ts, tests,package.json, configs).EnrichMetadataMcpProvider(import + instance) fromMCP_PROVIDER_REGISTRYinpackages/mcp/src/registry.ts.@salesforce/mcp-provider-metadata-enrichmentdependency from@salesforce/mcp(packages/mcp/package.json).CODEOWNERSand both publish workflows (publish-providers.yml,publish-mcp-server.yml).README.md.Acceptance criteria
enrich_metadata.tsremoved frompackages/mcp-provider-metadata-enrichment/src/tools/packages/mcp-provider-metadata-enrichment/deletedEnrichMetadataMcpProviderremoved fromMCP_PROVIDER_REGISTRY; no remainingToolset.ENRICHMENTreferences for this tool@salesforce/mcp-provider-metadata-enrichment@salesforce/mcpbuilds without the packageVerification
yarn build—@salesforce/mcpcompiles cleanly without the package.yarn test— 82/82 passing in themcppackage.yarn lint— 0 errors.Toolset.ENRICHMENT.Note
The
ENRICHMENT = 'enrichment'value inpackages/mcp-provider-api/src/enums.tswas intentionally left in place — it's a value in a separately-published shared API package, so removing it is a potential breaking change for other consumers and was out of scope for this story. Happy to remove it in a follow-up if the team prefers.🤖 Generated with Claude Code