{"id":"dassianinc-dassian-adt","name":"dassian-adt","af_score":68.2,"security_score":54.0,"reliability_score":42.5,"what_it_does":"MCP server that connects AI assistants to an SAP system via the ADT API for ABAP development tasks (read/write/activate objects, manage transports, run syntax/ATC checks, query tables, execute ABAP “run”, and handle sessions/health). Provides both stdio (local) and HTTP (team) MCP transports.","best_when":"Teams want an MCP-compatible, tool-based interface to SAP ABAP development with iterative error correction and session recovery.","avoid_when":"You cannot safely store/use SAP credentials for a long-running server, or you need strict audit separation per user without compensating controls.","last_evaluated":"2026-03-30T15:41:49.761133+00:00","has_mcp":true,"has_api":true,"auth_methods":["Environment-variable credentials for SAP_USER/SAP_PASSWORD","Session-based ADT login handled by server"],"has_free_tier":false,"known_gotchas":["Running/releasing operations can be irreversible; ensure the agent/host requires confirmation steps for transport release.","Using NODE_TLS_REJECT_UNAUTHORIZED=0 disables TLS verification (for self-signed certs) and may create security risk.","Execution via abap_run may leave artifacts if cleanup fails; README mentions prompting when leftover temp classes exist.","HTTP transport mode is multi-client and implies concurrent SAP sessions; ensure isolation/auditing on the MCP server side."],"error_quality":80.0}