LibXposed MCP Server
Provides API references, architectural guides, code scaffolding, and legacy migration tools for building LibXposed modules on Android, including AndroidManifest.xml templates, Gradle project configurations, and hooking API documentation.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@LibXposed MCP Servermigrate my legacy XposedBridge hook code to LibXposed"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
LibXposed MCP Server
A structured, full-spectrum Model Context Protocol (MCP) server providing API references, architectural guides, code scaffolding, and legacy migration tools for modern LibXposed Android development.
Deployed globally on Cloudflare Edge with zero cold start.
Quick Setup
Option A: Remote Server (Recommended)
Connect directly to the deployed Cloudflare Edge endpoint without local installation.
Transport and Protocol Requirements
Endpoint Path: Use the root path (
https://libxposed-mcp.ra1nify.workers.dev). Do not append/sse. Modern MCP clients communicate over statelessstreamable-httpat the root path.Transport Field: Explicit MCP environments (such as DSH) require
"transport": "streamable-http".
Client Configuration (DSH, Cursor, Windsurf, Claude Desktop)
{
"mcpServers": {
"libxposed": {
"url": "https://libxposed-mcp.ra1nify.workers.dev",
"transport": "streamable-http"
}
}
}Web Dashboard: Visit https://libxposed-mcp.ra1nify.workers.dev for server health and tool discovery.
Option B: Local Stdio Mode
Run as a local process via standard input/output.
1. Build Bundle
npm install
npm run build2. Configure Local Client
{
"mcpServers": {
"libxposed": {
"command": "node",
"args": ["<PATH_TO_PROJECT>/dist/index.js"]
}
}
}Related MCP server: Android Source Explorer MCP Server
Architecture and Coverage
The server models 100% of all five LibXposed subprojects and legacy migration pathways:
libxposed:api: Core hook interfaces (XposedInterface,XposedModule,Hooker,Chain,Invoker,CtorInvoker,HookHandle,HookBuilder,ExceptionMode,XposedInterfaceWrapper), module lifecycle events, and Javadoc references.libxposed:helper&helper-ktx: High-throughput reflection caching (Reflector), fluent matching chains (HookBuilder), dex analysis, and idiomatic Kotlin DSL.libxposed:service: Cross-process communication (RemotePreferencesreplacing legacyXSharedPreferences), framework IPC bindings (XposedService), target discovery (HookedTarget), hot reload protocols (HotReloadResult), Direct Boot compatibility, and AIDL specifications.libxposed:lint: API level compatibility constraints (@SinceApi(101/102)), internal API restrictions (@InternalApi), and lint checks.libxposed:example: Standard project templates (build.gradle.kts,AndroidManifest.xml,proguard-rules.pro,META-INF/xposed/java_init.list,ModuleMain.java,ModuleMainKt.kt).migration: 1:1 mapping definitions and structural transformation guides from legacy XposedBridge (de.robv.android.xposed.*) to modern LibXposed.
Available MCP Tools
All seven tools operate across both streamable-http and local stdio transports:
Tool Name | Parameters | Description |
|
| Search across classes, methods, constants, architecture guides, and migration rules. |
|
| Query signatures, parameter specifications, sinceApi constraints, and Javadoc links. |
|
| Retrieve HookBuilder patterns, Reflector caching mechanisms, and Kotlin DSL usage. |
|
| Access RemotePreferences IPC guides, reactive listener examples, and AIDL definitions. |
|
| Generate compile-ready project configurations and module skeletons. |
|
| Provide 1:1 migration maps and code conversions from legacy XposedBridge to LibXposed. |
|
| Inspect API 101/102 differences, breaking changes, and @InternalApi enforcement. |
Verification and Testing
Execute the test suites to verify server behavior:
# Run stdio tool invocation test
npm test
# Run exhaustive edge-case test suite (34 cases)
npm run test:deep
# Run TypeScript static analysis
npm run typecheckCI/CD and Deployment
Automated delivery is managed by GitHub Actions (.github/workflows/deploy.yml). Each push to master or main automatically type-checks, builds, and deploys the Cloudflare Worker.
Continuous Deployment Setup:
Navigate to Settings > Secrets and variables > Actions in your GitHub repository.
Add a new secret named
CLOUDFLARE_API_TOKENcontaining your Cloudflare API token (Workers:Editpermissions).Pushes to
masterwill deploy directly to Cloudflare Edge using Node.js 22 and Wrangler v4.
License
Licensed under the Apache License 2.0.
Available Tools
7 toolscheck_api_compatibilityA
Inspect LibXposed API version requirements (@SinceApi 101 vs 102), breaking changes, and prohibited @InternalApi usage.
Inputs: version (required).
get_api_docA
Retrieve detailed documentation, method signatures, parameters, return types, sinceApi version, and official Javadoc links for LibXposed core API classes.
Inputs: className (required), memberName.
get_helper_guideA
Get comprehensive guides and API references for libxposed:helper, including HookBuilder fluent discovery, Reflector reflection utilities, and Kotlin helper-ktx DSL.
Inputs: topic (required).
get_scaffoldB
Generate standard project scaffolds and configurations for LibXposed modules, including build.gradle.kts, AndroidManifest.xml, ProGuard/R8 rules, entry list, and Java/Kotlin module skeletons.
Inputs: type (required).
get_service_guideB
Get comprehensive guides for libxposed:service, including XposedService, XposedServiceHelper, modern RemotePreferences, HookedTarget process introspection, Hot Reload protocols, Direct Boot rules, and AIDL definitions.
Inputs: topic (required).
migrate_legacy_codeA
Convert legacy XposedBridge / EdXposed code (e.g., handleLoadPackage, findAndHookMethod, XC_MethodHook, XSharedPreferences) into modern, type-safe LibXposed code.
Inputs: legacySnippet.
search_libxposedA
Search across all LibXposed modules (api, helper, service, lint, example, migration) by keyword, class name, method name, or concept.
Inputs: query (required), module.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
TDQS
Scored across 7 tools
Each tool has a distinct role: global keyword search, targeted API/helper/service documentation, scaffolding, migration, and compatibility checking. The only mild overlap is between search_libxposed and the get_* documentation tools, since a search may surface the same content, but the descriptions make the intended distinction clear.
All names are snake_case with a leading verb (search_, get_, migrate_, check_) followed by a clear target. The pattern is predictable throughout and the resource is always obvious from the name.
Seven tools is well-scoped for a documentation/guidance server covering a library ecosystem. Each tool maps to a distinct developer need (discover, read docs, scaffold, migrate, verify compatibility) with no filler.
The surface covers discovery, documentation for core/helper/service modules, scaffolding, migration, and version compatibility, which spans the main developer lifecycle. Minor gaps exist: the lint and example modules are only reachable via generic search, and there is no tool to enumerate modules or API versions directly.
Maintenance
Related MCP Connectors
Docsy gives AI assistants current, version-specific documentation for libraries, frameworks and SDKs. Resolve library IDs and versions, then search and fetch focused official documentation with original source links using five read-only MCP tools. Hosted Streamable HTTP with OAuth 2.1 sign-in.
Dated, verified API breakages for coding agents, plus a local scan for them in your existing code.
Get up-to-date, version-specific documentation and code examples from official sources directly in…
Your Expo and EAS project in natural language: up to date SDK docs, cloud builds (status, logs, trig
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides Android development assistance following NowInAndroid best practices, including architecture patterns, code generation for feature modules/ViewModels/repositories, and searchable documentation for Jetpack Compose and modularization.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to query real AOSP and AndroidX source code on demand, offering class and method lookup, class member and hierarchy inspection, source-wide text/regex search, and optional LSP-powered cross-file definition, reference, and type resolution from a local offline cache.-
- FlicenseNot gradedqualityAmaintenanceEnables AI tools to retrieve and navigate actual AOSP and AndroidX source code on demand for accurate framework internals, with tools for class/method lookup, member listing, hierarchy, and source search. Optional LSP features add cross-file definitions, references, and type information.-
- FlicenseNot gradedqualityBmaintenanceProvides AI assistants with on-demand, precise access to real AOSP and AndroidX source code, enabling class and method lookups, class member and hierarchy inspection, source-wide text/regex search, and optional cross-file definition, reference, and type resolution via LSP. Sources are synced locally for instant offline queries against framework internals like the Activity lifecycle, ViewModel restoration, and Compose internals.-