algorithmaide-mcp
Related Servers
Alternatives to algorithmaide-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server that lets AI agents drive the LuckyStar/LS_KTool Android memory-debugging stack, exposing tools for memory read/write, scanning, pointer operations, and device/process management via the Model Context Protocol.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that wraps Android ADB functionality into AI assistant tools, enabling device management, shell execution, file operations, app management, media capture, and log analysis via natural language.262MIT
- AlicenseAqualityBmaintenanceA minimal, secure MCP server for AI-assisted mobile development, enabling build, install, interact, and inspect Android/iOS apps.331477Apache 2.0
- FlicenseNot gradedqualityAmaintenanceMCP server that provides AI coding agents real Android development tools—Gradle, adb, logcat, lint, crash triage—through a local, permissioned interface. Enables agents to inspect projects, run safe Gradle tasks, capture logs/screenshots, and triage crashes.1-
- AlicenseNot gradedqualityBmaintenanceThis server enables AI-assisted APK reverse-engineering entirely on-device, orchestrating jadx, apktool, adb, frida, and APKiD through a job/workflow engine, and exposing those agents as native MCP tools for Claude without any cloud dependency.3MIT
- AlicenseNot gradedqualityAmaintenanceLocal-first MCP server that enables AI agents to safely control and observe Android mobile devices, supporting device diagnostics, app lifecycle management, async task execution, and performance monitoring through a policy-constrained interface with explicit confirmations.Apache 2.0
TDQS
Scored across 23 tools
Several tool pairs have overlapping purposes (e.g., multiple log querying tools, add/inject/replace hooks), which may confuse an agent about which to use. However, descriptions help differentiate most tools.
All tools follow a consistent verb_noun snake_case pattern, but some verbs are vague (e.g., 'get' vs 'query' vs 'read') and import_hook_json breaks the config naming pattern.
23 tools is reasonable for the specialized domain of Frida hook management. The count slightly exceeds the ideal 3-15 range but is still manageable.
The tool surface covers most lifecycle operations: config, hooks, profiles, logs, and workflows. Minor gaps include lack of explicit hook removal and a dedicated disable function.