LibXposed MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_libxposedA | Search across all LibXposed modules (api, helper, service, lint, example, migration) by keyword, class name, method name, or concept. |
| get_api_docA | Retrieve detailed documentation, method signatures, parameters, return types, sinceApi version, and official Javadoc links for LibXposed core API classes. |
| get_helper_guideA | Get comprehensive guides and API references for libxposed:helper, including HookBuilder fluent discovery, Reflector reflection utilities, and Kotlin helper-ktx DSL. |
| 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. |
| 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. |
| migrate_legacy_codeA | Convert legacy XposedBridge / EdXposed code (e.g., handleLoadPackage, findAndHookMethod, XC_MethodHook, XSharedPreferences) into modern, type-safe LibXposed code. |
| check_api_compatibilityA | Inspect LibXposed API version requirements (@SinceApi 101 vs 102), breaking changes, and prohibited @InternalApi usage. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.