Skip to main content
Glama
abd3lraouf

Specter MCP

by abd3lraouf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Specter MCP

No user-submitted related servers found.

    Related Servers

    • devilge

      Yercko
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to build, drive, and observe Android/KMM apps end-to-end through ADB and Gradle, with tools for UI automation, error capture, and testing.
      33
      43 npm
      MIT

    • Karagöz

      yagizdo
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to automate Android and iOS devices, including emulators and physical devices, by capturing screenshots, reading UI accessibility trees, performing touch and text input, and managing app lifecycle and logs.
      MIT

    • Kotlin Multi-Agent

      peter14l
      A
      license
      A
      quality
      B
      maintenance
      Enables end-to-end generation, scaffolding, testing, diagnosis, and auditing of Kotlin applications for Android, Compose Multiplatform, Ktor, and Spring Boot through a coordinated team of specialized agents.
      24
      1
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.7/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool targets a distinct function: crash analysis, building, cleaning, deep link navigation, UI capture, app state inspection, log inspection, installation, UI interaction, launch, device listing, environment management, linter, E2E tests, and unit tests. There is no ambiguity between tools.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (e.g., analyze_crash, build_app). One exception is deep_link_navigate (noun_verb), and interact_with_ui uses a preposition, but overall the naming is mostly consistent.

    Tool Count5/5

    15 tools is well-scoped for a mobile app development and testing server. Each tool earns its place, covering build, test, deploy, device management, and analysis without being overwhelming.

    Completeness4/5

    The tool set covers core workflows: building, testing (unit, lint, E2E), installing, launching, UI interaction, logging, crash analysis, and device management. Minor gaps like uninstall or app data reset are absent but not critical.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources