Skip to main content
Glama
ssaffhauser-web

kpi-dealflow-mcp

by ssaffhauser-web
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to kpi-dealflow-mcp

No user-submitted related servers found.

    Related Servers

    • Scout MCP

      Flikah
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to look up real estate agents, search MLS listings, submit buyer/seller leads, and access proprietary seller-intent signals in SC and GA.
      MIT

    • Kommo MCP Server

      wdavidce
      F
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to autonomously interact with Kommo CRM, providing tools for managing pipelines, leads, contacts, and custom fields via the Kommo API v4.
      27
      1
      -

    • Pipedrive MCP Server

      ckalima
      A
      license
      B
      quality
      A
      maintenance
      Enables users to manage Pipedrive CRM data including deals, contacts, and activities directly through an AI assistant. It supports full CRUD operations, email engagement analysis, and mapping of custom field metadata for comprehensive pipeline management.
      123
      135 npm
      8
      MIT

    • Zoho CRM MCP demo

      Monsteroo
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables LLM agents to search deals, summarize pipeline metrics, find duplicate leads, and create leads using real Zoho CRM field names through plain-language tool calls.
      -

    • Outlet das Cores CRM

      oeduardomanoel
      F
      license
      Not graded
      quality
      D
      maintenance
      Integrates CRM data with AI agents to manage leads, track pipeline statistics, and search price catalogs via Supabase. It enables automated lead creation, stage updates, and history tracking through natural language commands.
      -
    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 4 tools

    Disambiguation5/5

    Each tool targets a distinct operation on leads: creation, listing, retrieval, and update. There is no overlap in purpose, making it easy for an agent to select the correct tool.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case (e.g., add_lead, list_leads, get_lead, update_lead). The minor pluralization in list_leads does not detract from clarity.

    Tool Count5/5

    Four tools is well-scoped for a lead pipeline server. Each tool serves a necessary function without redundancy, and the count falls comfortably within the 3-15 ideal range.

    Completeness4/5

    The tools cover the core lead lifecycle: add, list, get, and update. A delete tool is missing, but for many pipelines this may be intentional. Overall, the surface is adequately complete for common agent tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources