Skip to main content
Glama
bluereacher-mcp

bluereacher-mcp

Official
by Blue-Reacher

Related Servers

Alternatives to bluereacher-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables an AI agent to read and send real iMessages—including text, voice notes, stickers, links, images, and reactions—through a managed cloud phone line without needing a Mac.
      16 npm
      AGPL 3.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to read, search, and send iMessages with features like contact name resolution, session grouping, and attachment listing. It provides intent-aligned tools to efficiently navigate conversation history and manage messages through natural language queries.
      6
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to send real iMessage, SMS, and WhatsApp messages from a business's dedicated number, run campaigns, read replies and lead scores, manage contacts and sequences, and check which numbers are iPhones or on WhatsApp. It is available as a hosted OAuth connector for Claude and ChatGPT or as a local npm package with an API key that adds SMS verification, verify widgets, and reply webhooks.
      406 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to send and receive iMessages and emails, and manage agent identities, in MCP-compatible clients.
      6
      20 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to read iMessage history and send messages on macOS. Supports conversation listing, message search with keyword and semantic modes, contact lookup, and sending messages to existing conversations.
      13
      11
      MIT

    TDQS

    A4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct responsibility: sending, checking delivery status, reading conversation history, and verifying iMessage capability. There is no meaningful overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case: send_imessage, get_message_status, list_conversations, check_imessage_capability. The naming is predictable and uniform.

    Tool Count4/5

    Four tools is a reasonable, focused size for an iMessage-sending server. The set feels slightly lean but each tool earns its place and the count is not a problem.

    Completeness4/5

    The core iMessage workflow is covered: send, check status, view conversation history, and verify capability. Minor gaps exist, such as no explicit message-content retrieval by ID or inbound message handling, but agents can work around these.

    Maintenance

    ActivitySlowing
    ResponsivenessSyncing