Skip to main content
Glama
Mautic MCP Connector

Mautic MCP Connector

by si-essence

Related Servers

Alternatives to Mautic MCP Connector

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      A lightweight MCP server that connects Claude AI to Mautic marketing automation, enabling contact management, email sending, campaign operations, and analytics via natural language.
      1
      -
    • F
      license
      C
      quality
      D
      maintenance
      Enables comprehensive integration with Mautic marketing automation platform, providing contact management, campaign automation, email operations, form management, analytics, and content management through natural language commands.
      68
      34
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables agents and scripts to drive a social publishing account through remote or local MCP tools: drafting, scheduling, approving and publishing posts, running durable background jobs with file attachments, and reading or editing Brand Memory, assets, and standing agents. Hosts can connect over OAuth with no API key, or run the stdio variant with a key for local disk tools.
      65
      1
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables MCP clients such as Claude and Cursor to read timelines, search statuses, and look up users or conversations, plus optionally post, delete, favorite, and follow with explicit confirmation. It supports both local stdio launches and remote HTTP hosting with per-user authorization.
      15
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Comprehensive MCP server for the Mautic marketing automation API, providing 203 tools for managing contacts, campaigns, emails, segments, and more.
      2
      ISC
    • A
      license
      B
      quality
      B
      maintenance
      Connects MCP clients to a self-hosted Seafile server through the seahub HTTP API, exposing libraries, files, search, sharing, and optional admin operations over stdio or Streamable HTTP. It defaults to read-focused tools and gates writes behind confirmation, with token redaction and dry-run previews.
      4
      MIT

    TDQS

    C2.9/5.0

    Scored across 50 tools

    Disambiguation4/5

    Most tools target clearly distinct resources and actions, with helpful separation between single-contact and global activity, and between row-level stats and email stats. A few pairs such as update_contact vs add/remove_contact_tags and list_activity vs get_contact_activity could be confused, but the descriptions clarify the boundaries.

    Naming Consistency4/5

    All names use snake_case with the mautic_ prefix and a predictable verb_noun structure. The main minor inconsistency is change_contact_stage using 'change' while analogous membership tools use add_contact_to_* / remove_contact_from_*.

    Tool Count2/5

    At 50 tools, the surface is heavy for an agent-facing connector, with many list/get pairs and resource families that could be consolidated or scoped more tightly. The domain is broad, but the count exceeds a well-scoped tool set.

    Completeness3/5

    Read coverage is broad across contacts, companies, campaigns, segments, emails, forms, stages, points, notes, reports, stats, webhooks, and assets. However, write lifecycle is uneven: contacts lack a delete operation, and campaigns, segments, emails, forms, stages, notes, reports, and assets have no create/update/delete tools, leaving notable gaps for full CRUD.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues