Skip to main content
Glama
Sign In
luneos-mcp

luneos-mcp

Official
by webOS-ports
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to luneos-mcp

No user-submitted related servers found.

    Related Servers

    • A.R.T MCP Server

      limingerf
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables users to manage Android ROM projects through MCP by importing, unpacking, repacking, and synthesizing images, DAT/BR files, and super partitions using the toolkit’s shared workflows.
      2
      AGPL 3.0

    • APK-MCP

      tkb-bit
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides AI agents with a unified MCP interface for Android APK reverse engineering, metadata analysis, Smali/resource editing, rebuilding, signing, verification, and ADB device testing.
      MIT

    • Android Studio MCP

      crimSun-dev
      A
      license
      B
      quality
      B
      maintenance
      Lets AI coding agents build, test, and lint Android projects with Gradle, control devices and emulators via adb, automate UI through screenshots and input injection, and use a live IDE bridge for refactoring, code inspection, and run configurations. Works with any MCP client over stdio or authenticated HTTP.
      46
      MIT

    • android-mcp-toolkit

      Nam0101
      A
      license
      A
      quality
      C
      maintenance
      A growing collection of MCP tools for Android Development. Currently features a deterministic Figma-SVG-to-Android-XML converter, with plans for Gradle analysis, Resource management, and ADB integration tools.
      7
      14 npm
      18
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools map cleanly onto distinct retrieval modes: enumerate topics (list), fetch one full document (get), and full-text search across the corpus (search). Descriptions explicitly state when to use each, including cross-references ('Use luneos_list_topics to see valid names'), leaving no realistic chance of misselection.

    Naming Consistency5/5

    All three names use the same luneos_ prefix followed by a verb_noun pattern (luneos_list_topics, luneos_get_topic, luneos_search). The singular/plural distinction between get_topic and list_topics is meaningful rather than inconsistent, and the style is uniform throughout.

    Tool Count4/5

    Three tools is on the thin side but each has a distinct, non-overlapping role and the whole surface is coherent for a read-only knowledge base. Nothing feels padded or missing at the operation level, though a slightly larger set (e.g. browsing by category or recency) would not be unreasonable.

    Completeness4/5

    For a read-only knowledge base, list/get/search covers the full retrieval lifecycle with no dead ends: an agent can discover topics, read them in full, or jump straight to a symptom via search. Minor gaps exist around metadata such as topic freshness, categories, or pagination for very large corpora, but core usage is fully supported.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources