chore(mcp): create dxt file for mcp server in pipeline

[bastiandoetsch]

Pull Request Submission Checklist

• Follows CONTRIBUTING guidelines
• Commit messages
  are release-note ready, emphasizing
  what was changed, not how.
• Includes detailed description of changes
• Contains risk assessment (Low | Medium | High)
• Highlights breaking API changes (if applicable) - N/A
• Links to automated tests covering new functionality
• Includes manual testing instructions (if necessary)
• Updates relevant GitBook documentation (PR link: ___)
• Includes product update to be announced in the next stable release notes

What does this PR do?

This PR adds support for building Claude Desktop Extensions (DXT) as part of the Snyk CLI build pipeline. At the end of the pipeline the DXT build is triggered via github API (github.com/snyk/mcp-dxt).

Where should the reviewer start?

• Verify the CircleCI configuration changes in .circleci/config.yml
• Verify the upload artifacts script changes

How should this be manually tested?

• run the pipeline

What's the product update that needs to be communicated to CLI users?

Risk assessment (Low | Medium | High)?

Low

Any background context you want to provide?

The MCP (Model Context Protocol) server is located in the snyk-ls repository. This PR extracts the mcp_extension directory from snyk-ls during the build process and packages it as a Claude Desktop Extension. The extension follows the DXT specification and can be installed in Claude Desktop to provide security scanning capabilities.

What are the relevant tickets?

[Add ticket reference if applicable]

[snyk-io]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

✅ license/snyk check is complete. No issues have been found. (View Details)

✅ code/snyk check is complete. No issues have been found. (View Details)