---
title: "Android-MCP vs codebase-memory-mcp"
type: "comparison"
canonical_url: "https://www.graphcanon.com/compare/cursortouch-android-mcp-vs-deusdata-codebase-memory-mcp"
tools: ["cursortouch-android-mcp", "deusdata-codebase-memory-mcp"]
---

# Android-MCP vs codebase-memory-mcp

*GraphCanon updated Sep 20, 2026*

## Verdict

Pick Android-MCP if android-MCP is a Python-based server for interacting with Android devices designed to ease development tasks that require automation and interaction through a dedicated MCP server; pick codebase-memory-mcp if codebase-memory-mcp excels at indexing codebases into a persistent knowledge graph with support for 158 languages, sub-ms query times, and minimal token use, delivered as a single static binary.

[Android-MCP](https://github.com/CursorTouch/Android-MCP) reports 857 GitHub stars, 112 forks, and 10 open issues, last pushed Jul 1, 2026. [codebase-memory-mcp](https://deusdata.github.io/codebase-memory-mcp/) has 44k stars, 3.6k forks, and 597 open issues, last pushed Sep 20, 2026. Figures are from public GitHub metadata via [Android-MCP's repository](https://github.com/CursorTouch/Android-MCP) and [codebase-memory-mcp's repository](https://github.com/DeusData/codebase-memory-mcp).

| | [Android-MCP](/tools/cursortouch-android-mcp.md) | [codebase-memory-mcp](/tools/deusdata-codebase-memory-mcp.md) |
| --- | --- | --- |
| Tagline | MCP Server for interacting with Android Devices | High-performance code intelligence MCP server indexing codebases into a persistent knowledge graph quickly |
| Stars | 857 | 43,838 |
| Forks | 112 | 3,570 |
| Open issues | 10 | 597 |
| Language | Python | C |
| Adopt for | Android-MCP is a Python-based server for interacting with Android devices designed to ease development tasks that require automation and interaction through a dedicated MCP server. | codebase-memory-mcp excels at indexing codebases into a persistent knowledge graph with support for 158 languages, sub-ms query times, and minimal token use, delivered as a single static binary. |
| Persona | - | - |
| Runtime | - | - |
| License | MIT | MIT |
| Categories | Developer Tools | Data & Retrieval, Developer Tools |

## Trust and health

_Sourced signals - not a safety guarantee. No winner column._

| | [Android-MCP](/tools/cursortouch-android-mcp.md) | [codebase-memory-mcp](/tools/deusdata-codebase-memory-mcp.md) |
| --- | --- | --- |
| Maintenance | Steady (60%) | Very active (96%) |
| Days since push | 80d | 0d |
| Open issues (now) | 10 | 597 |
| Stars delta | +52 (30d) | +8.5k (30d) |
| Open issues delta | +2 (30d) | +249 (30d) |
| Owner type | Organization | User |
| Full report | [trust report](/tools/cursortouch-android-mcp/trust.md) | [trust report](/tools/deusdata-codebase-memory-mcp/trust.md) |

## Decision facts: Android-MCP

- **Adopt for:** Android-MCP is a Python-based server for interacting with Android devices designed to ease development tasks that require automation and interaction through a dedicated MCP server.

## Decision facts: codebase-memory-mcp

- **Adopt for:** codebase-memory-mcp excels at indexing codebases into a persistent knowledge graph with support for 158 languages, sub-ms query times, and minimal token use, delivered as a single static binary.

## Choose when

### Choose Android-MCP if…

- Android-MCP is primarily Python; codebase-memory-mcp is C.
- Tags unique to Android-MCP: ai, android, automation, mcp-server.
- When developing applications requiring close integration with the Android device's hardware and needing an automated testing framework

### Choose codebase-memory-mcp if…

- codebase-memory-mcp is primarily C; Android-MCP is Python.
- Tags unique to codebase-memory-mcp: aider, ast, claude-code, code-analysis.
- Also covers Data & Retrieval.
- When needing rapid codebase indexing into a knowledge graph with low latency queries

## When NOT to use Android-MCP

- If your project requires extensive use of native Java or Kotlin for deep system interactions that cannot leverage Python effectively
- In scenarios demanding very lightweight server solutions, as Android-MCP might introduce additional overhead due to its full-feature set

## When NOT to use codebase-memory-mcp

- If you demand extensive interactive graphical UI features beyond its command-line interface capabilities
- When your project prioritizes a dynamic runtime environment over static binaries

## Common questions

### What is the difference between Android-MCP and codebase-memory-mcp?

Android-MCP: MCP Server for interacting with Android Devices. codebase-memory-mcp: High-performance code intelligence MCP server indexing codebases into a persistent knowledge graph quickly. See the comparison table for live GitHub stats and shared categories.

### When should I choose Android-MCP over codebase-memory-mcp?

Choose Android-MCP over codebase-memory-mcp when Android-MCP is primarily Python; codebase-memory-mcp is C; Tags unique to Android-MCP: ai, android, automation, mcp-server; When developing applications requiring close integration with the Android device's hardware and needing an automated testing framework.

### When should I choose codebase-memory-mcp over Android-MCP?

Choose codebase-memory-mcp over Android-MCP when codebase-memory-mcp is primarily C; Android-MCP is Python; Tags unique to codebase-memory-mcp: aider, ast, claude-code, code-analysis; Also covers Data & Retrieval; When needing rapid codebase indexing into a knowledge graph with low latency queries.

### When should I avoid Android-MCP?

If your project requires extensive use of native Java or Kotlin for deep system interactions that cannot leverage Python effectively In scenarios demanding very lightweight server solutions, as Android-MCP might introduce additional overhead due to its full-feature set

### When should I avoid codebase-memory-mcp?

If you demand extensive interactive graphical UI features beyond its command-line interface capabilities When your project prioritizes a dynamic runtime environment over static binaries

### Is Android-MCP or codebase-memory-mcp more popular on GitHub?

codebase-memory-mcp has more GitHub stars (43,838 vs 857). Stars measure visibility, not whether either tool fits your constraints.

### Are Android-MCP and codebase-memory-mcp open source?

Yes - both are open-source projects on GitHub (Android-MCP: MIT, codebase-memory-mcp: MIT).

### Where can I find alternatives to Android-MCP or codebase-memory-mcp?

GraphCanon lists graph-backed alternatives at [Android-MCP alternatives](/tools/cursortouch-android-mcp/alternatives) and [codebase-memory-mcp alternatives](/tools/deusdata-codebase-memory-mcp/alternatives) ([Android-MCP markdown twin](/tools/cursortouch-android-mcp/alternatives.md), [codebase-memory-mcp markdown twin](/tools/deusdata-codebase-memory-mcp/alternatives.md)), ranked by typed relationship edges rather than popularity votes.

### Is there a machine-readable version of this comparison?

Yes. The markdown twin at [this comparison](/compare/cursortouch-android-mcp-vs-deusdata-codebase-memory-mcp.md) mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers.

### Which is better maintained, Android-MCP or codebase-memory-mcp?

Android-MCP: Steady. codebase-memory-mcp: Very active. Compare maintenance labels, days since push, and release cadence in the trust section below - stars alone do not measure maintenance.

### Where are the full trust reports for Android-MCP and codebase-memory-mcp?

GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: [Android-MCP trust report](/tools/cursortouch-android-mcp/trust); [codebase-memory-mcp trust report](/tools/deusdata-codebase-memory-mcp/trust).

---

**Machine-readable endpoints**

- JSON: [`/api/graphcanon/graph?tool=cursortouch-android-mcp`](/api/graphcanon/graph?tool=cursortouch-android-mcp)
- LLM index: [/llms.txt](/llms.txt)
- Full corpus: [/llms-full.txt](/llms-full.txt)

_GraphCanon - The knowledge graph for AI development. https://www.graphcanon.com/_
