DCC-MCP Creator

Implement the requested adapter or service within its owner's project. A private service needs no public repository, catalog entry, issue or release. For operating an existing app use dcc-mcp; for individual tool packages use dcc-mcp-skills-creator. An already-loaded skill needs no installation or new agent turn.

Implementation boundaries

Use DccServerBase and DccServerOptions.from_env(...), with host API calls through HostExecutionBridge. Embedded, sidecar and standalone services have different owner/host lifetimes; resolve that contract before wiring the runtime. Reuse Core's public lifecycle, discovery and state owners rather than parallel adapter implementations. Keep identity and host configuration data-driven.

Application UI uses project-owned dcc-cua / ui-control. Before observation or input report provider=dcc-cua runtime=<version> pid=<exact-pid> hwnd=<exact-native-hwnd>. Missing binding blocks actions. Read the bundled dcc-cua skill for UI work; never fall back to generic Computer Use without the user's explicit change of provider.