@pitchmentor/mcp
OfficialRelated Servers
Alternatives to @pitchmentor/mcp
No user-submitted related servers found.
Related Servers
- FlicenseCqualityCmaintenanceExposes 153 tools to connect AI assistants to the Ploomes CRM, enabling CRUD operations, funnel configuration, CPQ, automations, and webhooks.1001-
- FlicenseNot gradedqualityCmaintenanceConnects AI assistants to the Ploomes CRM, exposing 153 tools for CRUD operations on entities, pipeline and field configuration, CPQ proposal models, automations, and webhooks.-
- AlicenseCqualityCmaintenanceProvides AI assistants with access to all public GoHighLevel API endpoints as MCP tools, enabling contact, conversation, opportunity, calendar, and other CRM operations with configurable safety gates for writes and deletes.5565 npm2MIT
- AlicenseAqualityDmaintenanceConnects AI agents to the Ploomes CRM REST API, exposing 56 tools for managing contacts, deals, tasks, pipelines, interactions, quotes, orders, products, fields, users, and account information.569 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to read and write leads, contacts, companies, tasks, notes, pipelines, tags, custom fields, users, events, conversations, and catalogs in the conversation-first sales CRM through its official v4 API, including a raw API call tool for any endpoint.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to access and manage Nynch CRM data, relationship intelligence, context querying, and multi-agent orchestration through 47 tools.MIT
TDQS
Scored across 41 tools
Most tools map to a single resource+action, and descriptions clearly separate similar operations (get_call vs summarize_call, get_webhook_endpoint vs test_webhook_endpoint). Some boundaries blur within analytics/usage (get_analytics_overview, get_analytics_by_member, get_usage, list_member_usage) and lead writing (upsert_lead vs update_lead vs batch_upsert_leads), but scope labels and descriptions help an agent choose correctly.
Every tool follows a strict verb_noun snake_case pattern (list_leads, get_call, create_api_key, rotate_webhook_secret). Voice and noun phrasing are consistent across all domains, making names highly predictable.
41 tools is heavy, though the server covers many distinct domains (calls, leads, webhooks, team, billing, coaching, API keys, analytics). Each tool generally earns its place, but the surface is large enough that it approaches the limit of comfortable scoping for an agent.
Core lifecycle coverage is strong for webhooks, API keys, team/invites, and leads. Minor gaps exist: no delete operation for leads, calls, or custom coaching styles (only archive for calls), and analytics is limited to overview and per-member without time-series granularity.