[FEATURE] Claude Cowork custom connector options

Resolved 💬 1 comment Opened Apr 26, 2026 by emack463 Closed May 29, 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

Claude cowork only permits custom connectors that have an HTTPS connection available. This makes it challenging to build and deploy local MCP. My current example is a pyzotero implementation running locally. With my current configuration I need to wrap this is in a proxy and self-sign a certificate prior to utilising the connector. This is a bit onerous.

Proposed Solution

Could we get the option to have HTTP/HTTPS or local execution?

Alternative Solutions

_No response_

Priority

Low - Nice to have

Feature Category

MCP server integration

Use Case Example

When creating a custom connector the UI offers a choice of route i.e. HTTP/HTTPS/local

Additional Context

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗