ARC 1 vs Docker MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
ARC 1 vs Docker MCP
In-depth architectural comparison of the ARC 1 and Docker MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
ARC 1
Developer Tools · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Docker MCP
Developer Tools · Local stdio
Quality: 47/100 (Fair) | Auth: No auth required
Verdict Summary: Choose ARC 1 if you need specialized Developer Tools tools running via a local process. Choose Docker MCP if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose ARC 1 when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Read exact ABAP source, method bodies, grep matches, table data, CDS views, access controls (`DCLS`), metadata extensions (`DDLX`), service bindings (`SRVB`), knowledge-transfer docs (`SKTD` or friendly alias `KTD`), message classes (`MSAG`), revision history (`VERSIONS`/`VERSION_SOURCE`), inactive…
SAPSearch
Object search + full-text source code search across the system
SAPWrite
Create/update/delete ABAP source and DDIC metadata with automatic lock/unlock (PROG, CLAS, INTF, FUNC, FUGR, INCL, DDLS, DCLS, DDLX, BDEF, SRVD, SRVB, SKTD/KTD, TABL, DOMA, DTEL, MSAG; availability adapts for BTP). Class updates can target local includes (`definitions`, `implementations`, `macros`,…
SAPActivate
Activate ABAP objects — single or batch (essential for RAP stacks), with guarded retry for the S/4HANA ED064 batch quirk. Publish/unpublish OData service bindings (SRVB)
SAPNavigate
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
ARC 1 is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Docker MCP belongs to Developer Tools using local stdio subprocess. Select ARC 1 when you need capabilities focused on developer tools and Docker MCP when you require tools for developer tools.
Execute ABAP SQL with table-not-found suggestions and automatic chunking for simple long literal `IN (...)` lists
SAPTransport
CTS transport management (list/get/create/release/delete/reassign/release-recursive), transport layer/target lookup, package transport requirement checks, and reverse lookup history (`action="history"`)
SAPGit
Git-based ABAP workflows across gCTS and abapGit (list/clone/pull/push/commit/branch/unlink) with backend auto-selection and safety gating (`--allow-git-writes`)
SAPContext
Dependency APIs (`action="deps"`): optional KTD plus bounded source-derived contracts, not a complete relationship inventory. Also supports live where-used (`action="usages"`), CDS impact (`action="impact"`), and TABL includes/appends (`action="structure"`)