Skip to main content
Glama
JackJProsp

Prosp MCP Server

by JackJProsp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Prosp MCP Server

No user-submitted related servers found.

    Related Servers

    • instantly-mcp

      katekruger
      A
      license
      A
      quality
      A
      maintenance
      Enables MCP clients to read Instantly.ai analytics and manage leads, campaigns, Unibox, sender accounts, blocklist, and webhooks, with write actions gated behind confirm prompts and configurable safety policies.
      40
      59 PyPI
      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
      1
      MIT

    • linkedin-mcp

      rzere
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that lets AI agents operate a real LinkedIn account in plain English with safety controls and approval queues.
      12 npm
      1
      MIT

    • Prosyo MCP Server

      ShubhamTuts
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to connect to a hosted multichannel B2B outbound engine for LinkedIn messaging, cold email sequencing, and pipeline management, including campaign reads and prospect research. Write actions that send, launch, enroll, or spend credits require chat confirmation before completing.
      MIT

    • GTM MCP Server

      vivz-git
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to perform go-to-market workflows such as company and contact enrichment, CRM querying, and controlled, audited writes to a CRM through MCP tools callable from any MCP client.
      1
      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

    B3.4/5.0

    Scored across 26 tools

    Disambiguation4/5

    Tools are mostly distinct across accounts, campaigns, leads, inbox, and analytics. The only mild overlap is between account-level operational checks like get_account_budget and get_account_health, and between campaign/workspace reporting tools, but descriptions clarify their separate purposes.

    Naming Consistency4/5

    The set follows a strong snake_case verb_noun pattern: list_, get_, set_, create_, import_, search_, add_, send_, mark_, diagnose_. The main deviation is signal_attribution, which is noun-only rather than starting with a verb like get_, but otherwise naming is predictable.

    Tool Count3/5

    26 tools is heavy for a single MCP server and exceeds the typical 3-15 range. The domain is broad enough that most tools earn their place, but the surface sits at the upper edge of reasonable and includes several reporting/account checks that could potentially be consolidated.

    Completeness4/5

    Coverage spans the core outreach lifecycle: account health and budgets, lead lists/imports/tagging, campaign creation/limits/status, inbox replies, and diagnostics with signal attribution. Minor gaps exist around editing an existing campaign's node sequence and explicit lead/list deletion, but these are largely workaround-able.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources