LeadFlow MCP
Related Servers
Alternatives to LeadFlow MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage a simple SQLite lead CRM by creating leads, listing and filtering them by status, updating status values, viewing per-status statistics, and using a daily report prompt.MIT

agentreadycrmofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to manage a full CRM: resolving and creating organizations and contacts, logging interactions, moving deals through pipelines, and recording signals and proof points backed by quotes and URLs. Data lives in a local SQLite file or a hosted team service, with the same tools, views, and skills in both.MIT- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage an outreach CRM via SQLite, including importing contacts from Apollo/Crunchbase, fuzzy matching, seniority ranking, drafting and scoring emails, and tracking sends/replies through pluggable email providers.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage CRM data including companies, contacts, prospects, pipelines, forecasts, and tasks via typed MCP tools, with local SQLite storage and a JSON CLI.MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude to read local CRM records, capture notes, and propose updates through MCP while keeping human approval in the dashboard or CLI. It supports querying relationships, follow-ups, tickets, and qualification data backed by SQLite.1MIT
- FlicenseNot gradedqualityDmaintenanceEnables querying and interacting with a SQLite CRM database of sales leads using natural language, offering tools for pipeline summaries, lead search, and weighted forecasting.-
TDQS
Scored across 11 tools
Each tool has a distinct resource+action target: lead CRUD (create/update/get/search), scoring explanation, interaction logging, follow-up scheduling/status/listing, summary, and export. The only near-overlap is get_lead (which returns a score) and score_lead (which explains it), but the descriptions make the split explicit — retrieve vs. explain. No two tools appear to do the same thing.
Nearly all tools follow a snake_case verb_noun pattern (create_lead, search_leads, set_follow_up_status, export_leads_csv). The one deviation is pipeline_summary, which is noun-only with no verb. Minor but noticeable inconsistency in an otherwise predictable scheme.
11 tools is well within the 3-15 sweet spot and each maps to a real workflow step (intake, edit, lookup, search, scoring, interactions, follow-ups, reporting, export). Nothing looks redundant or padding.
The surface covers the lead lifecycle well: create, read, update, search, score, interact, follow-up, summarize, export. Gaps: there is no delete_lead or delete/void interaction, and no direct tool to list a lead's follow-ups independently (only set status on an existing one). These are workable around but represent real dead ends for cleanup workflows.