Skip to main content
Glama
vanman2024

Multilead Open API MCP Server

by vanman2024

Related Servers

Alternatives to Multilead Open API MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to manage email campaigns, contact lists, analytics, A/B tests, and transactional emails through natural language, using OAuth for secure connection.
      MIT
    • F
      license
      C
      quality
      C
      maintenance
      Exposes 153 tools to connect AI assistants to the Ploomes CRM, enabling CRUD operations, funnel configuration, CPQ, automations, and webhooks.
      100
      1
      -
    • A
      license
      C
      quality
      D
      maintenance
      Enables AI assistants to interact with the Zapmail API through natural language commands for domain management, mailbox operations, and exports to third-party platforms like Reachinbox and Instantly. Provides complete coverage of 46+ Zapmail tools with dynamic API integration and multi-workspace support.
      100
      86 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI assistants to interact with GoHighLevel's complete API including contacts, opportunities, calendars, workflows, communications, and business management tools. Supports both Bearer token and OAuth2 authentication with automatic token management.
      24 npm
      10
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to manage omnichannel CRM data (WhatsApp, Instagram, Facebook) via the official API, including leads, deals, pipelines, activities, tags, products, conversations, lists, attachments, and notes.
      MIT

    TDQS

    B3.2/5.0

    Scored across 77 tools

    Disambiguation2/5

    Many tools have overlapping purposes that could cause confusion. For example, there are multiple tools for retrieving leads (get_leads_from_campaign, get_leads_from_seat, list_leads, get_lead), multiple tools for managing tags (create_tag, assign_tag_to_lead, remove_tag_from_lead, get_tags_for_leads, get_tags_for_seat, get_tags_of_a_specific_seat), and multiple tools for webhooks (create_webhook, create_global_webhook, delete_webhook, delete_global_webhook, list_webhooks, list_global_webhooks). While descriptions help, the boundaries between these tools are often unclear, leading to potential misselection.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (e.g., create_campaign_from_template, get_campaign_info, update_lead). There are minor deviations, such as 'change_a_password' (includes 'a'), 'get_user_information' (uses 'information' instead of 'info'), and 'list_all_seats_of_a_specific_user' (verbose with articles). However, the overall pattern is readable and predictable, with snake_case used consistently throughout.

    Tool Count2/5

    With 77 tools, the count is excessive for the apparent scope of a LinkedIn outreach and lead management platform. Many tools appear redundant or overly granular (e.g., separate tools for seat suspension and reactivation, multiple export tools with slight variations). This volume will overwhelm agents and increase the risk of misselection, indicating poor scoping and a need for consolidation.

    Completeness5/5

    The tool set provides comprehensive coverage for the domain of LinkedIn outreach, lead management, and team administration. It includes full CRUD operations for leads, campaigns, tags, webhooks, seats, teams, and users, along with advanced features like message syncing, blacklisting, statistics, and exports. There are no obvious gaps; agents can perform end-to-end workflows without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessResponsive