ARC 1 vs Trace MCP
A side-by-side look at the ARC 1 and Trace MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose ARC 1 for developer tools work; choose Trace MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose ARC 1 when
- You need dedicated capabilities in the Developer Tools domain.
- Its auth model fits you: other.
- You have the keys it needs:
SAP_ALLOW_GIT_WRITES, SAP_ALLOW_DATA_PREVIEW, SAP_ALLOW_FREE_SQL, SAP_DENY_ACTIONS, SAP_BLOCKED_DATA_SOURCES, ARC1_ALLOWED_ORIGINS, ARC1_RATE_LIMIT, ARC1_MCP_HTTP_RATE_LIMIT. - You want tools like
SAPRead, SAPSearch, SAPWrite.
Choose Trace MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 55/100 · Good | 63/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | other | No auth required |
| Pricing | Free | Free |
| Required env vars | SAP_ALLOW_GIT_WRITESSAP_ALLOW_DATA_PREVIEWSAP_ALLOW_FREE_SQLSAP_DENY_ACTIONSSAP_BLOCKED_DATA_SOURCESARC1_ALLOWED_ORIGINSARC1_RATE_LIMITARC1_MCP_HTTP_RATE_LIMIT | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 229 | 193 |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 12 | Not listed |
| Full listing | View ARC 1 | View Trace MCP |
Tools & capabilities
ARC 1 tools 12
SAPReadRead 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…SAPSearchObject search + full-text source code search across the systemSAPWriteCreate/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`,…SAPActivateActivate 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)SAPNavigateGo-to-definition, find references, code completionSAPQueryRead saved SAPscript long texts or execute ABAP SQL; each path requires its own opt-inSAPTransportCTS transport management (list/get/create/release/delete/reassign/release-recursive), transport layer/target lookup, package transport requirement checks, and reverse lookup history (`action="history"`)SAPGitGit-based ABAP workflows across gCTS and abapGit (list/clone/pull/push/commit/branch/unlink) with backend auto-selection and safety gating (`--allow-git-writes`)SAPContextDependency 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"`)SAPLintLocal ABAP lint (system/release-aware presets, auto-fix, pre-write validation) + ADT PrettyPrint (server-side formatting)SAPDiagnoseSyntax check, ABAP Unit tests, ATC code quality, CDS test-case suggestions, active/inactive object-state comparison, generic ADT quickfix proposals/application deltas, gateway/system message diagnostics, short dumps, profiler traces, and the on-prem authorization trace (`SUAUTHVALTRC`, data-preview…SAPManageFeature probing, cache statistics, package lifecycle/change-package operations, and FLP catalog/group/tile helpers
Trace MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
ARC 1
No confirmed install command for ARC 1 yet — follow the setup steps linked from its listing page rather than a guessed package name.
Trace MCP
{
"mcpServers": {
"nikolai-vysotskyi-trace-mcp": {
"command": "npx",
"args": [
"-y",
"trace-mcp"
]
}
}
}
Frequently asked questions
ARC 1 is categorized under Developer Tools and uses an install path we have not confirmed yet. Trace MCP belongs to Developer Tools and uses a local stdio subprocess. Pick ARC 1 for developer tools work and Trace MCP for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. ARC 1 has no confirmed install command yet — follow its own setup instructions.
ARC 1 is listed as free. Auth: other. Trace MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add arc-1 and nikolai-vysotskyi-trace-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, ARC 1 has a quality signal of 55/100 (Good) with 2 views, 0 installs and 229 GitHub stars. Trace MCP has 63/100 (Good) with 2 views, 0 installs and 193 GitHub stars.