Skip to main content
Glama
johnalvero

Promotexter MCP Server

by johnalvero
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Promotexter MCP Server

No user-submitted related servers found.

    Related Servers

    • sms-web2sms-mcp-server

      Pibot-Dev
      F
      license
      A
      quality
      D
      maintenance
      Enables sending SMS messages and checking delivery status and credit balance via the web2sms.ro Romanian SMS gateway.
      3
      -

    • przypominamy-mcp

      pawelmamcarz
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables sending and managing SMS, voice messages, contacts, templates, blacklists, and account reports through the przypominamy.com REST API, with key-scoped authorization and safety confirmations for destructive actions.
      MIT

    • SMS.ir MCP server

      ali-toghiani
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables safe interaction with the SMS.ir Panel V2 API, providing read-only tools like balance and report checks, and billable SMS sending (including verification codes and personalized messages) only when explicitly confirmed and enabled. It also includes safety features like masking sensitive data, rate limiting, and a kill switch.
      1
      MIT

    • @theyahia/mts-exolve-mcp

      theYahia
      A
      license
      B
      quality
      F
      maintenance
      Enables sending SMS, making calls, retrieving call recordings, managing phone numbers, and sending Viber messages through the MTS Exolve API.
      8
      53 npm
      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 2 tools

    Disambiguation5/5

    The two tools have completely distinct purposes: get_balance retrieves account information, while send_sms sends messages. There is no overlap in functionality, and an agent would never confuse one for the other.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern (get_balance, send_sms) with clear, descriptive names. The naming convention is uniform throughout the toolset.

    Tool Count2/5

    With only two tools, the server feels severely underpowered for an SMS service domain. There are obvious missing operations like checking SMS status, viewing message history, managing contacts, or handling bulk sends that would be expected in a complete SMS API surface.

    Completeness2/5

    The toolset is severely incomplete for an SMS service. While it covers basic balance checking and message sending, it lacks essential operations like viewing sent messages, checking delivery status, managing templates, or handling errors. This will cause significant agent failures when trying to perform common SMS workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources