Skip to main content
Glama
ohneben

ActiveCampaign MCP

by ohneben
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to ActiveCampaign MCP

No user-submitted related servers found.

    Related Servers

    • mcp-activecampaign

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables interaction with ActiveCampaign email marketing and CRM via API v3 through natural language.
      26 npm
      MIT

    • mcp-activecampaign

      AlexlaGuardia
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to manage ActiveCampaign CRM, marketing automation, and contact data via 33 tools including contacts, deals, tags, automations, pipelines, custom fields, campaigns, accounts, and webhooks.
      65
      27 PyPI
      1
      MIT

    • DLF Agency MCP Server

      drleadflow
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to manage GoHighLevel workspaces through natural language, with 508 tools across 18 domains for complete CRM, marketing, and workflow automation.
      Apache 2.0

    • GoHighLevel MCP Server

      REALSolutions605
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to directly interact with the entire GoHighLevel CRM via 563+ tools across 44 categories, allowing natural language control for contacts, messaging, opportunities, calendars, and more.
      9 npm
      1
      ISC

    • GoHighLevel MCP Server

      ThinkBeDo
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects GoHighLevel sub-accounts to AI models with over 260 tools for managing contacts, messaging, sales pipelines, and marketing automation. It enables users to automate complex CRM operations and business tasks through natural language interfaces like Claude Desktop.
      9 npm
      ISC
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.3/5.0

    Scored across 325 tools

    Disambiguation1/5

    Tool names frequently collide or use vague verbs (e.g., `saved_responses`, `local_events`, `forms_1`), and `retrieve_a_savedresponse` is actually a destructive delete. Variants like `list_all_calendar_feeds` vs `list_all_calendar_feeds_1` and multiple count-history endpoints are nearly indistinguishable, so agents will frequently select the wrong tool.

    Naming Consistency1/5

    Naming follows no consistent pattern: `get_`, `list_`, `retrieve_`, `create_`, `add_`, `edit_`, `set_`, `remove_`, and `delete_` are used interchangeably, with arbitrary suffixes like `_1` and `_new`. Some tools are bare nouns (`brandings`, `saved_responses`, `local_events`), and one tool (`retrieve_a_savedresponse`) is misnamed as a read but actually deletes.

    Tool Count1/5

    Exposing 325 tools is far beyond what an agent can sensibly navigate; this is a raw API surface dump rather than a curated tool set. Even broad platforms typically need only a fraction of this count.

    Completeness2/5

    The surface is extensive across contacts, deals, ecommerce, segments, and custom objects, but common resources lack full CRUD: there is no delete campaign, no update list, no create/delete branding, and forms/templates are read-only. These gaps will cause agent failures when attempting standard lifecycle operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources