Skip to main content
Glama
Systeme.io MCP server for sales and pages

Systeme.io MCP server for sales and pages

Related Servers

Alternatives to Systeme.io MCP server for sales and pages

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables Claude to manage Systeme.io accounts, including contacts, tags, courses, and subscriptions, through natural language.
      18
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Connects AI assistants to the complete Salesforge product suite, enabling management of workspaces, contacts, sequences, mailboxes, domains, and more across multiple sales tools.
      54 npm
      2
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to manage email marketing, including lists, subscribers, segments, templates, draft campaigns, reports, transactional emails, and deliverability checks, through an OAuth-authenticated remote server.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to read and manage Syncro (SyncroMSP) data such as customers, contacts, tickets, assets, and invoices, with explicit write actions for creating and updating records and emailing invoices.
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to manage a signed-in Bloom account by booking clients, preparing invoices and contracts, and following up on payments through natural-language requests.
      7
      Elastic 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

    TDQS

    A3.5/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool maps to a distinct browser-automation primitive (open, read, click, type, close) or a distinct meta function (guide, status), so misselection is unlikely. The only soft overlap is guide vs. status, both framed as things to do first, but their descriptions clarify the difference.

    Naming Consistency5/5

    Every tool uses the same systeme_io_ prefix followed by a single clear verb (guide, status, open, read, click, type, close). The pattern is uniform snake_case with no deviations.

    Tool Count5/5

    Seven tools is well-scoped for a browser-driven integration: one session lifecycle pair, three page-interaction primitives, and two onboarding helpers. Nothing feels redundant or padded.

    Completeness3/5

    The core interaction loop (open, read, click, type, close) is covered, but there are notable gaps for the stated domain: no navigation to a specific URL, no select/dropdown handling for funnel and campaign forms, and no keypress/scroll/wait primitives. Agents can partially work around these via click and type, but form-building workflows will hit dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues