[FEATURE] API endpoint to programmatically deploy Desktop Extensions (.mcpb) to an organization

Resolved 💬 2 comments Opened Mar 31, 2026 by matanyaasisinnovid Closed Apr 3, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

When an organization manages multiple Claude Desktop Extensions (.mcpb files), there is no programmatic way to deploy them.
Every update requires manually uploading the file through the Claude.ai UI (Organization Settings → Connectors → Desktop → Add custom extension), which makes it impossible to automate extension deployments as part of a standard software release process.

Proposed Solution

Provide a Management API endpoint to upload/update Desktop Extensions for an organization, e.g.:

POST /v1/organizations/{org_id}/extensions
Content-Type: multipart/form-data
Body: .mcpb file

This would allow CI/CD pipelines to deploy extensions automatically after a successful build, completing the full automation loop without manual UI
steps.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

API and model interactions

Use Case Example

Use Case Example:

  1. A developer merges a bug fix into a Desktop Extension repository
  2. CI/CD pipeline automatically builds and packages the updated .mcpb file
  3. The pipeline calls an Anthropic API endpoint to upload the new version to the organization
  4. All org members get the updated extension without any manual intervention

Additional Context

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗