ACP MCP Workflow Adapter v1.0

Price: $4.99

Category: orchestration

What it does

ACP MCP Workflow Adapter helps teams move agent workflows between OpenClaw, Codex, Claude Code, Cursor, Gemini, Grok, and other ACP-compatible runtimes without locking the process to one vendor. It generates a clear portability recipe: what context is needed, which tools must be mapped, where approval gates belong, and what the receiving agent should verify before work continues.

Use cases

Agent platform teams converting workflows between coding agents or harnesses while keeping approvals and safety checks explicit.
Consultants and integrators documenting repeatable ACP/MCP migration playbooks for client environments.
Ops leads standardising tool-server requirements so workflows are mapped by capability, not vendor-specific command names.

Requirements

Python 3.10+ with standard library only.
No API keys required.
OpenClaw skill runtime compatible with local Python scripts; validated in the 2026-05-17 pipeline on OpenClaw v2026.3.23.

Example usage


python3 scripts/acp_mcp_adapter.py \
  --source codex \
  --target claude-code \
  --task "refactor payment module" \
  --tool git \
  --tool test-runner \
  --format md

Expected output


# ACP/MCP Workflow Adapter — refactor payment module
- Source: codex
- Target: claude-code

## Neutral contract
- context_files: AGENTS.md, SKILL.md, repo README, handoff packet
- inputs: task objective, repo path, constraints, approval boundaries
- outputs: clean diff, test evidence, handoff notes

## MCP/tool mapping
- git: verify in source harness → configure equivalent MCP/tool server or native tool
- test-runner: verify in source harness → configure equivalent MCP/tool server or native tool

## Approval gates
- before destructive file operations
- before external API writes
- before credential/config changes
- before publishing or deployment

Marketing copy

Move agent workflows without rebuilding them from scratch. ACP MCP Workflow Adapter turns a source/target agent pair into a vendor-neutral migration recipe with context requirements, MCP/tool mappings, approval gates, unsupported-feature checks, and a practical migration checklist — ideal for teams standardising work across OpenClaw, Codex, Claude Code, Cursor, Gemini, Grok, and other ACP-style runtimes.

Release evidence

Viper verdict: APPROVED_FOR_RELEASE in memory/viper-test-results-2026-05-17.md.
Security Audit: CLEARED by Warlock.
Evidence context: py_compile/help/self-test/security PASS; scoped pycache/pyc final scan clean.

Acp Mcp Workflow Adapter