Combien d'outils expose io.github.shashwatgtm/craft-gtm-mcp ?

io.github.shashwatgtm/craft-gtm-mcp expose 8 outil(s). Le coût de contexte pour les charger tous est d'environ 5306 tokens (coût unique au chargement, pas par appel).

accueil / serveurs / Dev & Code / io.github.shashwatgtm/craft-gtm-mcp

io.github.shashwatgtm/craft-gtm-mcp

serveur MCP (Model Context Protocol) · craft-gtm-mcp 2.2.23

▸ Dev & Code

[ Non encore testé ]

Verdict MCP Hub
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.

streamable-httpType / transport

directAccès

~5306 tokensCoût de contexte

8Outils

Est-ce que io.github.shashwatgtm/craft-gtm-mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.shashwatgtm/craft-gtm-mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 8 outils

competitive_intel≈ 760 tokens
Takes your product and the competitors you name, and returns one battle card per competitor built from your strengths, weaknesses, competitor details, objections, wins and losses. Each competitor detail goes to the competitor it names, each objection gets its own answer, and strengths and gaps taken from wins and losses are your own words.
Paramètres, retour & exemple (11)
Paramètres
- industry · string · optionnel · logistics_tech | fintech | saas | vertical_saas | ai_native | ites | telecom | software
  Optional: the sector you sell into, so the answer uses that sector's buyers, measures and objections. Leave it out and the tool reads the sector from your other inputs and names what it read
- competitors · string · requis
  Competitor names, comma-separated. You get one battle card for each competitor named
- recent_wins · string · optionnel
  Why customers chose you over competitors: used as your strengths when none are given
- your_sector · string · optionnel · logistics_tech | fintech | saas | vertical_saas | ai_native | ites | telecom | software
  Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
- your_product · string · requis
  Your product name and brief description
- recent_losses · string · optionnel
  Why you lost deals to competitors: used as your gaps when none are given
- business_model · string · optionnel · saas | services | connectivity | transactions | marketplace | hardware_software | investment
  Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other inputs and says how it read it
- your_strengths · string · optionnel
  Optional: what you do better, comma-separated. Taken from your wins, in your own words, if not provided
- your_weaknesses · string · optionnel
  Optional: where competitors beat you, comma-separated. Taken from your losses, in your own words, if not provided
- common_objections · string · optionnel
  Sales objections you hear (comma-separated). E.g., 'too expensive, missing X feature, competitor has better Y'
- competitor_details · string · optionnel
  Optional: Any known details about competitors, one per line or separated by semicolons. E.g., 'Competitor A is cheaper; Competitor B targets enterprise'. Each detail goes to the competitor it names
Exemple d'appel
```
{"name": "competitive_intel", "arguments": {"competitors": "texte", "your_product": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
craft_gtm_analyzer≈ 500 tokens
Takes the text of a GTM document or plan and returns an analysis against the CRAFT framework, with a score for each dimension. Each dimension is scored only on what the plan contains (Timeline counts real dates, durations and quarters), the tool shows the plan's own line for each, names only the elements that are missing and suggests sections to add.
Paramètres, retour & exemple (6)
Paramètres
- industry · string · optionnel · logistics_tech | fintech | saas | vertical_saas | ai_native | ites | telecom | software
  Optional: the sector you sell into, so the answer uses that sector's buyers, measures and objections. Leave it out and the tool reads the sector from your other inputs and names what it read
- your_sector · string · optionnel · logistics_tech | fintech | saas | vertical_saas | ai_native | ites | telecom | software
  Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
- document_type · string · requis · gtm_strategy | launch_plan | campaign_brief | quarterly_plan | project_proposal | marketing_plan
  Type of document (shown in the analysis)
- desired_outcome · string · optionnel
  Optional: What action should this document drive
- document_content · string · requis
  The GTM document or plan to analyze. Paste the full text: the tool reads it and scores it against the framework
- intended_audience · string · optionnel
  Optional: Who will read/approve this document
Exemple d'appel
```
{"name": "craft_gtm_analyzer", "arguments": {"document_type": "gtm_strategy", "document_content": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
crisis_planner≈ 731 tokens
Takes your company, industry, customer base and data sensitivity, and returns crisis playbooks with a response team and notification steps for each crisis. Name the crises you know of to get those playbooks. If you leave them out, the tool uses a default set of common crises for your sector (not ranked by likelihood). Each compliance item you list is used in the notification steps.
Paramètres, retour & exemple (9)
Paramètres
- company · string · requis
  Company name
- industry · string · requis · fintech | saas | logistics_tech | vertical_saas | ai_native | ites | telecom | software
  Industry affects which crises to prioritize
- your_sector · string · optionnel · logistics_tech | fintech | saas | vertical_saas | ai_native | ites | telecom | software
  Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
- company_size · string · optionnel · startup_under_50 | scaleup_50_200 | midsize_200_1000 | enterprise_1000_plus
  Affects response team structure
- customer_base · string · requis · b2b_enterprise | b2b_smb | b2c_consumer | mixed
  Customer type affects communication approach
- business_model · string · optionnel · saas | services | connectivity | transactions | marketplace | hardware_software | investment
  Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other inputs and says how it read it
- data_sensitivity · string · requis · high_pii_financial | medium_business_data | low_general
  Data sensitivity affects security protocols
- potential_crises · string · optionnel
  Optional: crisis types to plan for, comma-separated. If not provided, the tool uses a default set of common crises for your sector (not ranked by likelihood). Options: data_breach, service_outage, sla_breach, regulatory_action, fraud_incident, ai_wrong_action, pr_incident, executive_departure, security_vulnerability, customer_data_exposure, product_safety
- compliance_requirements · string · optionnel
  Optional: Relevant compliance, comma-separated (for example ISO 27001, SOC 2, GDPR). Each item is named in the notification steps
Exemple d'appel
```
{"name": "crisis_planner", "arguments": {"company": "texte", "industry": "fintech", "customer_base": "b2b_enterprise", "data_sensitivity": "high_pii_financial"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
customer_interview_kit≈ 615 tokens
Takes the interview type, the product context and the person you are interviewing, and returns an interview guide that fits the interview type, the sector (chosen, or read from your inputs) and the product complexity. Questions use the sector's own language, your hypotheses are kept whole, and synthesis templates are included.
Paramètres, retour & exemple (8)
Paramètres
- industry · string · optionnel · saas | fintech | logistics_tech | vertical_saas | ai_native | ites | telecom | software
  Industry affects terminology and context. Leave it out and the sector is read from your other inputs
- your_sector · string · optionnel · logistics_tech | fintech | saas | vertical_saas | ai_native | ites | telecom | software
  Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
- business_model · string · optionnel · saas | services | connectivity | transactions | marketplace | hardware_software | investment
  Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other inputs and says how it read it
- interview_type · string · requis · discovery | validation | feedback | churn | win_loss | persona_research
  Type of interview determines question focus
- key_hypotheses · string · optionnel
  Optional: Hypotheses to validate during interview, one per line or separated by semicolons
- target_persona · string · requis
  Who you're interviewing (role/title)
- product_context · string · requis
  Product/service being researched
- product_complexity · string · optionnel · simple | moderate | complex | highly_technical
  Affects technical depth of questions
Exemple d'appel
```
{"name": "customer_interview_kit", "arguments": {"interview_type": "discovery", "target_persona": "texte", "product_context": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
launch_commander≈ 766 tokens
Takes what you are launching, the launch type, your target segments and your goals, and returns a phased launch plan with tasks, a messaging table and success metrics. Give a date for a dated timeline, or enter 'TBD' or a quarter such as 'Q2 2027' for a flexible plan. Tasks and the messaging table follow the sector and business model read from your inputs, and each goal is filed under its own metric.
Paramètres, retour & exemple (11)
Paramètres
- goals · string · requis
  Launch success metrics (for example '40 qualified meetings, $300K pipeline, 5 reference customers')
- industry · string · optionnel · logistics_tech | fintech | saas | vertical_saas | ai_native | ites | telecom | software
  Optional: the sector you sell into, so the answer uses that sector's buyers, measures and objections. Leave it out and the tool reads the sector from your other inputs and names what it read
- team_size · string · optionnel · solo | small_2_5 | medium_6_15 | large_15_plus
  Marketing/GTM team size affects task distribution
- launch_date · string · optionnel
  Target launch date. Accepts: 'YYYY-MM-DD', 'Q1 2027', 'March 2027', or 'TBD' for planning mode
- launch_type · string · requis · major_release | feature_launch | beta_launch | product_update | market_expansion
  Type of launch determines plan complexity
- your_sector · string · optionnel · logistics_tech | fintech | saas | vertical_saas | ai_native | ites | telecom | software
  Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
- budget_level · string · optionnel · bootstrap | moderate | well_funded
  Budget affects recommended tactics
- business_model · string · optionnel · saas | services | connectivity | transactions | marketplace | hardware_software | investment
  Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other inputs and says how it read it
- product_feature · string · requis
  What you're launching (product/feature name and description)
- target_segments · string · requis
  Target customer segments (comma-separated)
- available_channels · string · optionnel
  Optional: Marketing channels available (comma-separated). E.g., 'email, linkedin, blog, webinar, PR, paid_ads, community'
Exemple d'appel
```
{"name": "launch_commander", "arguments": {"goals": "texte", "launch_type": "major_release", "product_feature": "texte", "target_segments": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
partner_architect≈ 724 tokens
Takes your company, product, partner model, partner goal and deal size, and returns a partner program with tiers, example commission amounts and KPIs, with a different structure for resellers, referrals, integrations, agencies, affiliates and white label. Uses your stated goal, existing partners and deal size, and names the partner types that fit your sector's buying committee.
Paramètres, retour & exemple (10)
Paramètres
- company · string · requis
  Your company name
- product · string · requis
  Product partners will sell/integrate
- industry · string · optionnel · logistics_tech | fintech | saas | vertical_saas | ai_native | ites | telecom | software
  Optional: the sector you sell into, so the answer uses that sector's buyers, measures and objections. Leave it out and the tool reads the sector from your other inputs and names what it read
- your_sector · string · optionnel · logistics_tech | fintech | saas | vertical_saas | ai_native | ites | telecom | software
  Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
- partner_goals · string · requis
  Revenue/growth targets from partners (shown as the target of the first KPI row)
- partner_model · string · requis · reseller | referral | integration_tech | agency_si | affiliate | oem_white_label
  Partner type determines program structure
- business_model · string · optionnel · saas | services | connectivity | transactions | marketplace | hardware_software | investment
  Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other inputs and says how it read it
- your_deal_size · string · requis
  Average deal size as one amount (e.g., '$5000 ACV', '$5K' or '$500/month'; a range is refused). It scales the example commission amounts; the example rates are fixed
- existing_partners · string · optionnel
  Optional: Current partner types/count, one per line or separated by semicolons (listed in the plan)
- partner_support_capacity · string · optionnel · minimal_self_serve | moderate | high_touch
  How much partner support can you provide?
Exemple d'appel
```
{"name": "partner_architect", "arguments": {"company": "texte", "product": "texte", "partner_goals": "texte", "partner_model": "reseller", "your_deal_size": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
pmf_scorecard≈ 677 tokens
Takes your product, target market and current metrics (MRR, ACV, churn, NPS, CAC, LTV, retention, activation and similar) and returns a product-market fit scorecard that scores each dimension against example benchmark ranges. Reads the business model from your inputs and leaves the activation score out for services, connectivity and investment businesses. Quotes your customer feedback and answers it.
Paramètres, retour & exemple (7)
Paramètres
- product · string · requis
  Product name and brief description
- your_sector · string · optionnel · logistics_tech | fintech | saas | vertical_saas | ai_native | ites | telecom | software
  Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
- target_market · string · requis · enterprise_saas | smb_saas | consumer | marketplace | fintech | logistics_tech | vertical_saas | ai_native
  Target market segment (for example enterprise SaaS, telecom or logistics tech)
- business_model · string · optionnel · saas | services | connectivity | transactions | marketplace | hardware_software | investment
  Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other inputs and says how it read it
- time_in_market · string · optionnel · pre_launch | 0_6_months | 6_12_months | 1_2_years | 2_plus_years
  How long the product has been in market (shown in the scorecard)
- current_metrics · string · requis
  Your current metrics, written as text (the tool reads the figures from it). Include any of: MRR, ARR, ACV, churn rate, NPS, CAC, LTV, retention rate, activation rate, DAU/MAU, trial conversion, revenue growth. Example: 'MRR: $50K, Churn: 3%, NPS: 45, CAC: $500, LTV: $3000, Retention: 92%'. A figure that no rule scores is listed as not scored
- customer_feedback · string · optionnel
  Optional: Qualitative feedback themes, one per line or separated by semicolons (for example 'Customers like X; they struggle with Y'). Each theme is quoted and answered
Exemple d'appel
```
{"name": "pmf_scorecard", "arguments": {"product": "texte", "target_market": "enterprise_saas", "current_metrics": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
retention_playbook≈ 744 tokens
Takes your customer segment, business model and current churn rate, and returns a retention playbook with health signals, interventions and an email draft for each churn reason. If you do not know why customers leave, leave the churn reasons out and you get a churn discovery kit with a framework for finding out. Health signals and interventions follow the business model, each churn reason gets its own answer, and your current interventions and data signals are used.
Paramètres, retour & exemple (10)
Paramètres
- product · string · optionnel
  Optional: Your product or company name, used in the title and the email drafts
- industry · string · optionnel · logistics_tech | fintech | saas | vertical_saas | ai_native | ites | telecom | software
  Optional: the sector you sell into, so the answer uses that sector's buyers, measures and objections. Leave it out and the tool reads the sector from your other inputs and names what it read
- your_sector · string · optionnel · logistics_tech | fintech | saas | vertical_saas | ai_native | ites | telecom | software
  Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
- cs_team_size · string · optionnel · no_dedicated_cs | small_1_3 | medium_4_10 | large_10_plus
  CS team capacity affects intervention strategy
- churn_reasons · string · optionnel
  Optional: known churn reasons, comma-separated. If you do not know them, leave this blank and you get a churn discovery kit with a framework for finding the reasons
- business_model · string · requis · saas_subscription | usage_based | marketplace | transactional | freemium | enterprise_contract | services_contract | connectivity_contract
  Business model affects health score weighting. enterprise_contract is read further from your text when it names services, connectivity or investment
- customer_segment · string · requis
  Customer segment to focus on
- current_churn_rate · string · requis
  Current churn rate (e.g., '5%' or '5% monthly')
- current_interventions · string · optionnel
  Optional: What retention tactics you already do (listed and compared with the playbook)
- available_data_signals · string · optionnel
  What you can track (comma-separated). E.g., 'login frequency, support tickets, SLA attainment, QBR attendance'
Exemple d'appel
```
{"name": "retention_playbook", "arguments": {"business_model": "saas_subscription", "customer_segment": "texte", "current_churn_rate": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://craft-gtm.gtmhelix.com/mcp