Skip to main content
Glama
artik0din

MCP LinkedIn Sales Navigator

by artik0din

Related Servers

Alternatives to MCP LinkedIn Sales Navigator

No user-submitted related servers found.

    Related Servers

    TDQS

    A3.8/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool addresses a distinct operation: profile retrieval, session health, lead saving, InMail sending, exporting, list creation, list enumeration, and searching. There is no functional overlap; even export_leads and search_leads have clear boundaries (export vs. discover). An agent can unambiguously select the correct tool for each task.

    Naming Consistency4/5

    All tools share the 'linkedin_' prefix and use snake_case. Most follow a clear verb_noun pattern (get_lead_profile, save_lead, send_inmail, export_leads, create_lead_list, list_lead_lists, search_leads). The exception is linkedin_session_status, which uses a noun_noun structure and lacks a verb, creating a minor but noticeable inconsistency.

    Tool Count5/5

    With 8 tools, the server is well-scoped for a LinkedIn Sales Navigator integration. Each tool covers a core workflow (searching, profiling, list management, outreach, and session monitoring) without unnecessary bloat. The count is firmly within the ideal 3-15 range and feels neither thin nor overloaded.

    Completeness4/5

    The surface covers the primary Sales Navigator operations: search, profile views, list CRUD (create/list, and save implies add to list), InMail sending, and export. Minor gaps exist—such as removing leads from lists or updating list metadata—but agents can accomplish most sales workflows without dead ends. The only notable omission is a list-lead enumeration function (e.g., list leads in a specific list), which is a secondary workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive