Skip to main content
Glama
voriq-ai

smartleadai-mcp

by voriq-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to smartleadai-mcp

No user-submitted related servers found.

    Related Servers

    • smartlead-cli

      bcharleson
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server for managing cold email campaigns, leads, email accounts, sequences, analytics, webhooks, and client sub-accounts via the Smartlead API.
      6 npm
      7
      MIT

    • smartlead-mcp-server-sse

      jacob-dietle
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI agents to manage Smartlead campaigns, including creating campaigns, updating schedules, managing email sequences, and adding leads, all over SSE.
      247 npm
      5
      MIT

    • Prosp MCP Server

      AvolveAi
      A
      license
      A
      quality
      D
      maintenance
      MCP server for Prosp.ai LinkedIn outreach automation. Manage leads, campaigns, messaging, and analytics programmatically.
      17
      MIT

    • Smartlead Simplified MCP

      jonathan-politzki
      A
      license
      B
      quality
      F
      maintenance
      A Multi-Channel Proxy server that provides a structured interface for interacting with Smartlead's API, organizing functionality into logical tools for campaign management, lead management, and other marketing automation features.
      20
      10 npm
      18
      MIT

    • SmartLead MCP Server

      LeadMagic
      A
      license
      Not graded
      quality
      F
      maintenance
      A Model Context Protocol server that provides AI coding assistants (Claude, Cursor, etc.) with access to SmartLead's cold email automation platform through 116+ API endpoints for campaign management, lead tracking, and email delivery.
      152 npm
      21
      MIT

    • SalesTouch

      antoineDsh
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for AI-native LinkedIn prospecting. It enables lead research, audience building, conversation management, and controlled outreach actions such as messaging and publishing through an OAuth-protected remote endpoint.
      2
      MIT
    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

    A3.9/5.0

    Scored across 39 tools

    Disambiguation4/5

    The tools are clearly separated into SmartProspect and Smartlead domains, and most actions target distinct resources. However, smartprospect_get_contacts, smartprospect_fetch_contacts, and smartprospect_find_emails all relate to obtaining contacts/emails with subtle differences that could cause misselection despite detailed descriptions.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with domain prefixes (smartprospect_/smartlead_). Reference data tools use list_*, actions use get_, create_, update_, etc., producing a predictable and readable naming convention.

    Tool Count2/5

    With 39 tools, the server is quite heavy, exceeding the typical well-scoped range. Many are reference data listers (countries, states, cities, etc.) that could be consolidated, making the surface feel bloated even though the two domains are clear.

    Completeness3/5

    Core workflows are covered (search, fetch, campaign management, lead import, block list management), but notable lifecycle gaps exist: no delete for saved searches or campaigns, no remove leads from campaign, and no campaign content update. Agents may hit dead ends when needing these operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources