Skip to main content
Glama
OsamaHassouna

HTML Email Playbook

Related Servers

Alternatives to HTML Email Playbook

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Local-first visual design workspace for AI assistants. Compose wireframes and branded multi-page HTML/CSS documents with live preview, annotations, brand and asset libraries, typed data collections, layout validation, PDF export, and draft-only Gmail handoff.
      14
      9
      19
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides SMTP integration for sending HTML emails and specialized prompts for intent detection and client information extraction. It enables LLMs to automate personalized email workflows and structure user communication data.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Let your AI assistant design beautiful emails & layouts — in your Temway workspace. It turns Claude, ChatGPT, Cursor and friends into a visual email & layout authoring studio.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI to send, read, search, delete and reply to emails through SMTP or Gmail API, supporting common email services like QQ, 163, Gmail and Outlook with HTML/text formats and attachments.
      20
      1
      ISC
    • A
      license
      A
      quality
      A
      maintenance
      Renders markdown into email-safe HTML that holds up in Outlook and Gmail, lints drafts for deliverability problems, and returns a live preview link. Also serves the emailmd syntax reference so an assistant can look up directives on demand.
      3
      1,368
      MIT

    TDQS

    A4.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool serves a distinct, well-defined purpose: listing categories, listing components, fetching component details, and fetching rule pages. No two tools overlap in functionality.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern using snake_case: 'list' for enumeration and 'get' for retrieval. The naming is predictable and easily distinguishable.

    Tool Count5/5

    With only 4 tools, the server is tightly scoped to browsing and retrieving email playbook content. This count is ideal for the domain—neither too few nor excessive.

    Completeness4/5

    The tools cover listing and retrieval of both components and rule categories. A minor gap is the lack of a tool to list all individual rules without specifying a category, but the existing tools enable complete navigation of the playbook.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues