Managed MCP connectors for Claude.
We turn useful open-source MCP servers into maintained, patched, production-ready connector packages. You get the image, the code, the update path, and a team responsible for keeping it current.
More than a Dockerfile.
Patched image and source fork
A reproducible downstream package based on a pinned open-source upstream, with your required patches applied cleanly.
Upstream maintenance
Regular checks against upstream releases, dependency changes, security issues, and protocol changes that affect Claude.
Connector hardening
Scope narrowing, redirect allowlists, read-only defaults where possible, audit-friendly settings, and deployment notes.
Release evidence
Build logs, changelogs, version pins, SBOM-ready artefacts, and a clear handover trail for every shipped version.
A repeatable supplier workflow.
The goal is not to fork forever and hope. The goal is a small downstream patch set, a known Claude test profile, and a clear path for each upstream update.
Confirm the Claude custom connector profile, tenant constraints, and tool scope.
Fork or vendor the upstream MCP server with a minimal patch delta.
Build and scan a container image from a pinned upstream release.
Test OAuth discovery, tool listing, and representative Claude tool calls.
Document update cadence, support boundaries, and rollback steps.
Claude-first
We test against Claude custom connector behaviour instead of claiming generic MCP support for every client.
Least privilege
Tool exposure and OAuth scopes are narrowed to the actual business use case before anyone signs in.
Clear ownership
The customer keeps their tenant, secrets, and consent. We maintain the connector package and update process.
Or build it yourself.
Do it yourself
- Fork and patch the upstream server yourself, and track every release for breaking changes.
- Work out OAuth scoping and least-privilege access for your tenant from scratch.
- Build and maintain your own container image, scanning, and version pins.
- Own the on-call burden when Claude or the upstream server changes behaviour.
Managed by Highland Code
- We maintain the patch set and track upstream releases for you.
- Scopes and OAuth access narrowed to your business use case before anyone signs in.
- A reproducible, scanned image with version pins and release evidence for every update.
- You keep your tenant and secrets. We own the connector package and its update process.
Microsoft 365 for Claude.
Our first packaged profile is for organisations that want Claude to work with Microsoft 365 through a managed MCP custom connector.
View Microsoft 365 connector