Skip to main content
Glama

Server Details

Manage contacts, templates, sequences and broadcasts in your Meisa email account from chat.

Ownership verified

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.0% over the last 24 hours
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP
URL
ChatGPT
–
Claude
–

TDQS

A3.8/5.0

Scored across 63 tools

Disambiguation4/5

Most tools target a distinct resource plus action, and descriptions carefully spell out boundaries (e.g. add_contact vs upsert_contact, send_email vs send_broadcast vs test_send_broadcast). The main overlaps are activate_trigger/deactivate_trigger being explicit shortcuts for update_trigger's is_active toggle, and the several broadcast test/preview/send variants, which an agent could occasionally confuse despite clarifying text.

Naming Consistency4/5

Names are uniformly snake_case with a consistent meisa_ prefix and resource-oriented suffixes (broadcast, template, sequence, trigger, contact). The only notable deviation is mixing 'add_' (add_contact, add_sequence_step, add_test_recipient) with 'create_' for other resource creation, plus a few longer action phrases like resend_broadcast_to_non_openers.

Tool Count2/5

63 tools is very heavy for a single MCP surface, even for a broad email platform with nine resource families. While many tools earn their place, the set clearly exceeds the 16-25 comfort band and forces agents to navigate fine-grained operations like block moves and trigger test dry-runs separately.

Completeness4/5

Coverage is broad and deep: contacts, templates (including block-level editing), sequences with steps and enrollment, triggers, broadcasts with scheduling/pausing/resend/analytics, senders, products, and test recipients. Gaps remain around contact deletion, sender/product update or deletion, and standalone tag creation beyond list_tags, but these are relatively minor lifecycle omissions.

Publisher details

Operator
Meisa · Publisher source
Vendor relationship
First-party · Publisher source
Privacy policy
Not provided
Trust center
Not available
Restrictions
Requires a Meisa account with email sending set up on your own AWS SES. · Publisher source

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables management of AI-powered email marketing automation, including subscriber segments, campaigns, and templates. It allows users to generate email sequences with AI and track detailed analytics through natural language commands.
      443
      2,924 npm
      4
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables connecting your own Gmail or SMTP mailbox and managing email through tools for sending, replying, searching, reading threads, and creating drafts.
      8
      Apache 2.0
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to manage mailing lists and contacts, read campaign reports with per-link clicks, and trigger automations. Supports lookups and updates by email address, tag and status management, and destructive operations with client confirmation.
      13
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables running cold email from AI apps, including mailbox and domain setup, warmup, lead search, campaign creation and review, reply handling, deals, and reporting.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources