merge-api

Docker Merge Kit — DevOps skill for Claude Code

DevOps community

Docker Sandboxes mixin kit granting sandboxed agents access to Merge Agent Handler's tool catalog.

How to install Docker Merge Kit

This entry records only its repository, not the path inside it, so there is no exact command to give. Open merge-api/docker-merge-kit and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Docker Merge Kit does

Docker Sandboxes mixin kit granting sandboxed agents access to Merge Agent Handler's tool catalog.

Alternatives in DevOps

Docker 71.9k ★
Skypilot — Run, manage, and scale AI workloads on any AI infrastructure 9.7k ★
Skill Claw — OpenClaw instance administration — manage hosts across macOS, Ubuntu/Debian, Docker, OCI, and Proxmox 2.8k ★

README

Merge Agent Handler kit

A [Docker Sandboxes](https://docs.docker.com/ai/sandboxes/) **mixin kit** that gives a sandboxed AI agent access to [Merge Agent Handler](https://docs.merge.dev/merge-agent-handler/overview) — a single authenticated gateway to hundreds of enterprise SaaS systems (CRM, HRIS, ATS, ticketing, accounting, file storage) exposed as one MCP tool catalog.

The kit tells the agent what Agent Handler is and when to use it, pins the sandbox's egress policy, and leaves every credential outside the sandbox VM.

**Status:** v1. Docker's kit format is experimental and still changing; this kit targets `schemaVersion: "2"` and is validated against `sbx` v0.42.1.

What's in the kit

Kit declares	Value
`kind`	`mixin` — layers onto any agent sandbox
`permissions.network.allow`	`ah-api.merge.dev:443` — nothing else. Defense in depth; see Network access
`agentInstructions`	What Agent Handler is, when to reach for it, and not to authenticate to third-party systems directly
`credentials`	none — see Why there is no credential block

The kit installs no packages, runs no startup commands, and writes no files. It touches none of Docker's [reserved agent-managed config paths](https://docs.docker.com/ai/sandboxes/customize/kits/) (`~/.claude.json`, `~/.codex/config.toml`, and friends) — there is nothing for it to configure there, because MCP registration happens on the host.

Prerequisites

Install the `sbx` CLI:

brew trust docker/tap && brew install docker/tap/sbx

Then sign in, which the MCP gateway requires:

sbx login

**Give your agent its own model-provider credential.** This is separate from anything the kit does, and it is the most common first-run failure: without it the agent exits immediately with `ERROR: agent exited with code 1` and no explanation. For Claude Code: