Servidor MCP de GrowthKit

• Nombre en el registrotools.growthkit/revenue-intelligenceverificado en el registro MCP

El nombre en el registro está bajo growthkit.tools. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-10-26
• Herramientas74
• El servidor se llamagrowthkit-mcp
• Versión del servidor1.12.2
• Versión del protocolo2025-11-25

El 2026-10-26 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 95 ms.

• Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.
• Comprobado 2 de los 7 días necesarios para juzgar su fiabilidad.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 2 hasta ahora
• Respondiómidiendo2 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta148 ms
• Espacio en el contexto del agente≈ 18.802 tokenslas definiciones de todas sus herramientas (74), que el agente lleva en cada turno
• Definiciones de herramientasA · 100 de 100
• Resultados tipados6 de 74 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Todas las herramientas pasan las seis comprobaciones.

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• embedMemory

  Store knowledge into long-term memory. Supports single items and batch embedding (max 50). IMPORTANT — Chapter System: Every memory MUST be classified into exactly one chapter via metadata.chapter. Available chapters: icp, strategy…

• searchMemory

  Search long-term memory using semantic similarity. ALWAYS SEARCH BEFORE ANSWERING marketing/strategy questions. Use short, specific keywords as queries. Available chapters: icp, strategy, campaigns, analytics, brand, competitors…

• listMemories

  List stored memories in stored order with pagination. Unlike searchMemory (semantic relevance ranking), use this to browse, enumerate, or audit a chapter — not to find the most relevant memory for a question. Filter by chapter via…

• updateMemory

  Update content or metadata of a stored memory. Use to enrich, fix, or reclassify. You MUST provide a change_reason explaining WHAT changed and WHY. The reason is stored in the version history audit log.

• deleteMemories

  Delete memories by IDs. Always confirm with user first. You MUST provide a change_reason explaining WHY these memories should be deleted. The reason is stored in the version history audit log.

• clearMemories

  Delete ALL memories. Irreversible. Always ask for explicit confirmation. You MUST provide a change_reason.

• countMemories

  Return only counts, not content — use for overview/sizing (e.g. 'how many competitor memories exist?') before deciding whether to list or search. Optionally filter by chapter via metadata_filter.chapter. For a per-chapter breakdown in one…

• getChapterOverview

  Get memory count per chapter. Use as FIRST STEP in new conversations or reviews.

• uploadDocument

  Upload a file to GrowthKit document storage. Optionally extracts text and embeds insights.

• listDocuments

  List stored documents with optional filtering by category or chapter.

• getDocument

  Get a specific document with fresh download URL and linked insights.

• deleteDocument

  Delete a document and its associated insights. Irreversible — always confirm with the user first.

• createReminder

  Schedule a reminder. Convert relative times to ISO 8601.

• listReminders

  List reminders, ordered by remind_at ascending. By default returns only pending reminders; pass status=sent|cancelled|all to widen. Optionally scope to one task via task_id. Returns each reminder's id, title, remind_at, and status.

• cancelReminder

  Cancel a pending reminder by ID.

• getHistory

  Get the version history of a specific memory. Shows all previous versions with timestamps and who made changes.

• restoreVersion

  Restore a memory to a previous version. Works for both existing and deleted memories. Use version_id from getHistory or listDeleted results.

• listDeleted

  List recently deleted memories that can be restored. Shows content preview and deletion info.

• listTeam

  List all team members (token holders) for your account. Shows display names, roles, and identifies which token is yours.

• sendNotification

  Send a notification to a team member. First use listTeam to find the recipient. For 2-person teams, the recipient is auto-resolved.

• checkNotifications

  Check for unread notifications (direct messages and broadcasts).

• crmSearchCompany

  Search CRM for a company by name. ALWAYS search before creating to avoid duplicates.

• crmGetCompany

  Get full company details by ID. Returns name, domain, industry, employees, address, CRM link.

• crmCreateCompany

  Create a new company. ALWAYS search first to avoid duplicates.

• crmGetCompanyDeals

  Get all deals linked to a company, by company ID. Use after crmSearchCompany or crmGetCompany to review that company's pipeline.

• crmGetCompanyContacts

  Get all contacts linked to a company, by company ID. Use to find who to reach at a known company.

• crmSearchContact

  Search CRM for a contact by name or keyword (fuzzy match); returns the top matches. Use to look up one known person. For structured segment queries across the contact base (e.g. 'all CEOs in pipeline companies'), use crmListPeople instead.

• crmListCompanies

  List companies from CRM with structured filters. Use for segment queries like 'all pharma companies with 50-200 employees in DACH'. All filter fields optional. Returns companies with id, name, industry, employees, country, and pagination…

• crmListPeople

  List people/contacts from CRM with structured filters. Use for segment queries like 'all CEOs in pipeline companies'. All filter fields optional. Unlike crmSearchContact (fuzzy lookup of one person by name), this does precise structured…

• crmGetContact

  Get full contact details by ID.

• crmCreateContact

  Create a new contact. ALWAYS pass company_id when the company exists.

• crmGetPipelines

  Get all pipelines with stages. ALWAYS call before creating deals to get valid stage_id.

• crmCreateDeal

  Create a new deal. Requires title + stage_id. MUST call crmGetPipelines first.

• crmUpdateDeal

  Update a deal. Use generic names: company_id, contact_id, expected_close.

• crmGetDeal

  Get the full record for one deal by ID. Use after a search or list returns a deal id when you need its complete details.

• crmAddNote

  Add a note to a CRM record — a deal, company, or contact. Provide content (HTML supported) and at least one target id (deal_id, company_id, or contact_id). Use to log call summaries, context, or decisions against the record.

• crmCreateActivity

  Create a follow-up activity on a CRM record. Provide a subject and set type (call | meeting | task | email | deadline; default task). Optionally link it to a deal, company, or contact and set a due_date (YYYY-MM-DD). Use to schedule next…

• crmCheckConnection

  Check if CRM is connected and which provider is active.

• enrichCompany

  Get company info by domain or name. Returns industry, employees, revenue, location, technologies. Prefer `domain` — it is unambiguous; a name matches whatever the provider thinks it means. `domain_unresolved` is not a provider failure…

• enrichPerson

  Get person profile from email or LinkedIn URL.

• findContacts

  Find contacts at a company. Filter by seniority or department.

• findEmail

  Find one person's email by name + domain.

• verifyEmail

  Check if an email is deliverable. Use before outreach.

• discoverSimilar

  Find lookalike companies for a seed and re-rank them by fit. mode='account' (seed={domain}) finds companies similar to that domain via Hunter similar_to; mode='icp' (no seed) discovers companies matching your saved ICP; mode='won_deals'…

• scoreLeads

  Trigger ICP lead scoring. Two independent modes — choose by WHERE the leads live, they do not overlap. (1) CAMPAIGN MODE — mode='campaign' plus campaign_id: scores the leads of one campaign (campaign_leads). Use this whenever the request…

• getTopLeads

  Retrieve the highest-scoring leads from the CRM, ranked by ICP fit. Returns company details, contact (if any), 4-dimension score breakdown, and qualitative reasons like 'Industry X — strong match to ICP'. By default filters out leads with…

• email_compose

  Compose an email via the user's connected email provider (currently Gmail; Microsoft 365 coming in Phase B). DEFAULT mode is 'draft' — creates a real draft in Gmail that the user can review before sending. Only use mode='send' when the…

• createCampaign

  Create a new campaign briefing. Use after collecting the 7 required fields via the campaign-briefing-playbook (search 'campaign-briefing-playbook' in playbook chapter to load the methodology). Sets status='draft'. Returns the created…

• listCampaigns

  List campaigns for the current user, optionally filtered by status. Returns campaign metadata plus per-stage lead counts.

• getCampaign

  Get a single campaign with full briefing details and lead-stage counts.

• updateCampaign

  Update fields on an existing campaign. Pass only the fields to change. Use `scoring` to give THIS campaign its own lead-scoring profile — without it the campaign is scored against the user's global ICP, which is wrong whenever the…

• addCampaignLeads

  Add one or more leads to a campaign. Standard fields (company_name, contact_email, etc.) go to typed columns. ANY OTHER FIELD you pass automatically gets stored in the metadata jsonb column — no schema migration needed for new fields…

• getCampaignLeadFields

  Discover which fields are actually used in a campaign's leads. Returns standard columns with non-null values PLUS all metadata (custom) keys with usage counts and sample values. ALWAYS call this BEFORE asking the user about lead structure…

• updateCampaignLead

  Update fields on an existing campaign lead. Pass lead_id (UUID from listCampaignLeads) and an updates object with only the fields to change. Use this to mark leads as rejected, manually correct enrichment data, or attach custom metadata…

• listCampaignLeads

  List leads in a campaign, optionally filtered by lifecycle_stage or enrichment_status. Returns up to 100 per call. Compact rows by default — id, company name, domain, score, fit_gate, strong_signals, has_email, has_phone, lifecycle_stage…

• getCampaignLead

  One campaign lead with everything stored about it: contact, company, score, lifecycle_stage, metadata and the complete enrichment_data. That is where you answer why a contact was chosen and who else was found: enrichment_data.persona…

• pipelineStatus

  Show where a campaign's leads stand in the qualification chain. Returns the funnel (how many leads have a domain, firmographics, a score, a signal, an email, a phone), how many candidates each stage currently has, and the top 10 leads by…

• pipelineRun

  Run ONE stage of the qualification chain for the next N candidates. Stages in order: resolve → score → signals → reveal → rescore; rerank follows reveal and re-judges the contacts that are already there. ALWAYS call with dry_run=true…

• listLeadSignals

  List the stored why-now signals for one lead or for a whole campaign: `id` (the signal_id that updateLeadSignal and deleteLeadSignal take), type (funding, hiring, job_change, leadership, acquisition, expansion, tech_change, regulatory…

• updateLeadSignal

  Correct ONE stored why-now signal in place. signal_id is the `id` of a signal from listLeadSignals — call that with active_only=false to also see expired signals. updates carries only the fields to change: type, signal, source_url…

Las primeras 60 de 74, en el orden del servidor.