Skip to main content
Glama
TecniForge

AndroidAPI net MCP

by TecniForge
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to AndroidAPI net MCP

No user-submitted related servers found.

    Related Servers

    • textbee-mcp by textbee

      textbee-mcpofficial

      textbee
      A
      license
      A
      quality
      A
      maintenance
      Send and read SMS through your own Android phone via textbee.dev, the open-source SMS gateway. Three tools for Claude, Cursor, and any MCP client: send_sms, get_messages (replies, verification codes, delivery status), list_devices. Self-hosted friendly.
      3
      36 npm
      1
      MIT

    • WAHA WhatsApp MCP Server

      Maheidem
      A
      license
      A
      quality
      C
      maintenance
      Enables Claude to interact with WhatsApp through a unified backend API, providing 20 tools for messaging, media, groups, contacts, and chat management.
      22
      13 npm
      MIT

    • Zapr WhatsApp MCP Server

      fcavalcantirj
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables sending WhatsApp messages through Claude Desktop and other MCP-compatible LLMs. Supports single and bulk messaging, phone number validation, and session management via the zapr.link service.
      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

    B3.4/5.0

    Scored across 52 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action (e.g., create_contact, send_sms, delete_wa_campaign). The prefixes clearly separate SMS, WhatsApp, USSD, contacts, groups, and account management, leaving no ambiguity between tools.

    Naming Consistency5/5

    All tools follow the pattern `androidapi_<verb>_<resource>`, with consistent snake_case and no deviations. Naming is uniform and predictable across the entire set.

    Tool Count2/5

    52 tools is significantly higher than the recommended range. While the domain covers multiple channels (SMS, WhatsApp, USSD, OTP, contacts, groups, campaigns, account info), the large number may be overwhelming and could likely be consolidated (e.g., merging send operations or reducing duplicate CRUD patterns).

    Completeness3/5

    Core operations for sending messages and managing contacts/groups are covered, including campaigns and OTPs. However, missing update operations for contacts and groups, no tool for editing campaigns (beyond start/stop), and no device or subscription management create notable gaps in the lifecycle coverage.

    Resources