Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Control and use an MCP Toolkit running in Docker. Use when setting up Docker MCP Toolkit (docker compose up/down), checking status/logs, configuring environm...
Control and use an MCP Toolkit running in Docker. Use when setting up Docker MCP Toolkit (docker compose up/down), checking status/logs, configuring environm...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Run, manage, and invoke Docker Desktop’s MCP Toolkit using the docker mcp CLI.
Install/upgrade Docker Desktop (MCP Toolkit is in Docker Desktop 4.62+ per docs). Enable MCP Toolkit: Docker Desktop → Settings → Beta features → Enable Docker MCP Toolkit → Apply. Preflight: ./scripts/preflight.sh
List enabled servers/tools: ./scripts/servers.sh ./scripts/tools.sh
List/enable/disable servers: ./scripts/servers.sh ./scripts/server-enable.sh <server-name> ./scripts/server-disable.sh <server-name> List tools: ./scripts/tools.sh Invoke a tool (via Docker’s gateway/tool runner): ./scripts/call-tool.sh --tool "mcp-find" --json '{"query":"postgres","limit":5}' Notes: call-tool.sh requires jq. docker mcp tools call uses key=value tokens. Non-string values use := (example: limit:=5, activate:=true). This skill currently supports only primitive JSON values (string/number/bool/null). Nested objects/arrays are rejected. For tools requiring object arguments (e.g. mcp-config-set), call docker mcp tools inspect <tool> --format json then run docker mcp tools call ... directly until this skill adds a tested encoder.
Docker MCP Toolkit runs an MCP Gateway and exposes tools through it. This skill intentionally uses the docker mcp tools … commands so OpenClaw can invoke tools without needing native MCP client support. If you need a true MCP client connection (stdio/SSE), pair this skill with the mcporter skill.
Prefer Docker Desktop’s secrets/keychain integration when possible. Do not expose gateway ports publicly. Use least-privilege credentials (separate Neon role with only required grants). For hardening guidance, read: references/security.md.
If commands say “Docker Desktop is not running”: start Docker Desktop. If MCP Toolkit isn’t visible: confirm it’s enabled in Beta features. If a tool call fails: run docker mcp tools --verbose inspect <tool> and check Docker Desktop MCP Toolkit UI for server configuration.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.