podcast-guest-crm
Related Servers
Alternatives to podcast-guest-crm
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables automated lead generation, AI enrichment, personalized messaging, and outreach orchestration through MCP tools and n8n workflows.-
- FlicenseNot gradedqualityCmaintenanceEnables AI-powered LinkedIn content creation, profile and company analytics, lead generation, and connection request automation through MCP tools.-
- AlicenseNot gradedqualityDmaintenanceAI-native productivity backend that gives your AI assistant persistent memory, pattern awareness, and computed intelligence about your work. 14 MCP tools for task management, daily planning, weekly review, and personal context.MIT
- FlicenseBqualityBmaintenanceEnables managing a small CRM of companies, contacts, deals, and activities through MCP tools, including creating and updating records, logging activities, searching across the CRM, and summarizing pipeline stages.15-
- FlicenseBqualityDmaintenanceCentralizes 10 marketing APIs into 14 MCP tools for AI assistants to pull data, audit sites, research trends, and manage Google Drive without switching tabs.35-
- AlicenseAqualityDmaintenanceMulti-platform content distribution — draft posts, repurpose content, generate carousels, schedule, analyze performance, create threads. 7 MCP tools.712 npmMIT
TDQS
Scored across 5 tools
Each tool maps to a clearly distinct action and resource: drafting an email, listing guests, adding a guest, transitioning a stage, and fetching analytics. There is no meaningful overlap between any pair, so an agent can select the right tool without confusion.
All five tools follow a consistent snake_case verb_noun pattern (draft_outreach_email, list_guests, add_guest, update_guest_stage, get_analytics_summary). The convention is predictable and readable throughout.
Five tools is on the lean side for a CRM but each earns its place and covers a distinct workflow step. Adding a guest detail/read tool would round it out without bloat.
Core lifecycle actions (add, stage transition, list, analytics) are present, but there is no way to fetch a single guest, edit guest fields (name, contact, notes), delete a guest, or log outreach replies. Notably, add_guest's description references an unexposed 'guest detail endpoint,' creating a dead end.