Keap MCP Server
Related Servers
Alternatives to Keap MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceComplete Model Context Protocol server for ClickUp, enabling interaction with tasks, spaces, lists, docs, goals, time tracking, and more through 93 tools and 18 React MCP apps.-
- AlicenseAqualityDmaintenanceA Model Context Protocol server for Plunk, the open-source self-hosted email platform. Provides 84 tools for transactional email, contacts, campaigns, segments, templates, workflows, events, and analytics through the Plunk API.119 npm2MIT
- AlicenseCqualityCmaintenanceMCP server that exposes the Kommo CRM API v4 (plus Files, Conversations, and analytics helpers) as Model Context Protocol tools, resources, and prompts.100MIT
- AlicenseAqualityCmaintenanceMCP server for Keap CRM, providing tools to manage contacts, tags, opportunities, notes, tasks, campaigns, and users via the Keap REST API v1.15Apache 2.0
- AlicenseBqualityAmaintenanceComprehensive Model Context Protocol server for MySQL databases featuring 191 specialized tools for CRUD operations, JSON functions, spatial/GIS, schema management, performance monitoring, and advanced features like OAuth 2.1 authentication and connection pooling.4349 npm10MIT
- AlicenseCqualityCmaintenanceA comprehensive MCP server covering the full GoHighLevel API surface with 651 tools, enabling management of contacts, opportunities, calendars, invoices, and more through natural language, with multi-tenant support and read-only safety defaults.10033 npm1MIT
TDQS
Scored across 111 tools
Most tools have distinct purposes targeting specific entities and actions (e.g., create_contact vs create_company). A few pairs like add_contact_to_campaign and add_contact_to_sequence are very similar but descriptions clarify the difference. Overall, ambiguity is low despite the large number.
All tools follow a consistent 'keap_verb_noun' pattern using standard verbs (create, get, list, update, delete) and appropriate singular/plural nouns (contact, contacts, tag, tags). No naming style mixing, making it predictable.
111 tools is very high for a typical MCP server. While the CRM domain has many entities, the count is inflated by separating model-getters and sub-resource operations (e.g., get_contact_credit_cards). Some consolidation could reduce the number without losing clarity.
CRUD operations are present for most core entities (contact, company, opportunity, product, order, etc.). There are minor gaps: missing update for subscriptions and affiliates, and no delete for some entities. However, the surface is comprehensive with additional operations like search, merge, opt-in/out, and webhooks.