craft-gtm-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pmf_scorecardA | Helps you decide whether you have product market fit and whether to scale: it takes your product, target market and current metrics (MRR, ACV, churn, NPS, CAC, LTV, retention, activation and similar) and returns a scorecard that scores each dimension against example benchmark ranges. It also gives priority actions and the data gaps to fill, reads the business model from your inputs, leaves the activation score out for services, connectivity and investment businesses, and quotes and answers your customer feedback. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing required fields or invalid values return an error naming what to supply or correct. Use this instead of scale_paid_check when you need a broad PMF assessment against the tool's example benchmarks. |
| launch_commanderA | Helps you decide your launch plan: it 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 'TBD' or a quarter such as 'Q2 2027' for a flexible plan. Tasks and messaging follow the sector and business model read from your inputs, and each goal is filed under its own metric. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing required fields or invalid values return an error naming what to supply or correct. Use this instead of craft_gtm_analyzer when you need to create a launch plan from a product, segments and goals. |
| customer_interview_kitA | Helps you decide what to ask customers to test your hunch: it 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 and the product complexity. Questions use the sector's own language (the sector is chosen, or read from your inputs), your hypotheses are kept whole, and synthesis templates are included. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing required fields or invalid values return an error naming what to supply or correct. Use this instead of icp_interview_synthesizer when you need questions and synthesis templates before conducting interviews. |
| retention_playbookA | Helps you decide why customers leave and what to do about each reason: it 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 instead. Your current interventions and data signals are used when you give them. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing required fields or invalid values return an error naming what to supply or correct. Use this instead of scale_paid_check when you need interventions and email drafts for supplied churn reasons. |
| partner_architectA | Helps you decide what partner program to run and how to start it: it takes your company, product, partner model, partner goal and deal size, and returns a partner program with tiers, example commission amounts and KPIs. The structure differs for resellers, referrals, integrations, agencies, affiliates and white label, uses your existing partners when given, and names the partner types that fit your sector's buying committee. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing required fields or invalid values return an error naming what to supply or correct. Use this instead of launch_commander when you need a partner program with tiers, commissions and KPIs. |
| crisis_plannerA | Helps you decide who does what when a crisis hits: it 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; without them it 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. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing required fields or invalid values return an error naming what to supply or correct. Use this instead of retention_playbook when you need response roles and notification steps for operational crises. |
| competitive_intelA | Helps you decide how to win against each competitor: it 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 stay in your own words. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing required fields or invalid values return an error naming what to supply or correct. Use this instead of competitive_trap_setter when you need complete battle cards across the competitors you supply. |
| craft_gtm_analyzerA | Helps you decide whether a GTM plan is clear enough to run: it takes the text of a GTM document or plan and returns a score for each CRAFT dimension, based only on what the plan contains. Timeline counts real dates, durations and quarters; the answer shows the plan's own line for each dimension, names only the elements that are missing and suggests sections to add. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing required fields or invalid values return an error naming what to supply or correct. Use this instead of launch_commander when you already have a GTM document to assess against CRAFT. |
| scale_paid_checkA | Helps you decide whether to scale paid now: it takes your customer list (signing date, segment, monthly fee and any stop or return dates) and your churn reasons, and returns, for each customer group, scale, run a capped test, or hold, with the counts behind it, the stop rule, payback, a first draft response to each churn reason and a churn interview guide. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing required fields or invalid values return an error naming what to supply or correct. Use this instead of pmf_scorecard when you need a paid-growth decision grounded in customer cohorts and unit economics. |
| segment_and_seat_cut_checkA | Helps you decide which customer segment to back, and whether your pricing is safe if AI cuts seats: it takes each segment's ACV, sales cycle, accounts, deal source and CAC, its logo, gross and net retention, how you charge in your own words, and your seller ramp, cost and qualified demand, and returns one page per segment with payback, gross profit per dollar of CAC, seller capacity after ramp and cycle, and the renewal if customers cut a share of seats. Ask the person to confirm the segment split, their own win rate and what customers can cut before marking each as confirmed; anything not confirmed or not given is shown as missing, never guessed. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing required fields or invalid values return an error naming what to supply or correct. Use this instead of scale_paid_check when you need segment economics, seller capacity and seat-reduction scenarios. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| helix-results |
TDQS
Scored across 10 tools
Most tools have distinct GTM decision outputs, and several descriptions explicitly say when to use one instead of another overlapping tool. The main ambiguity is among scale_paid_check, pmf_scorecard, retention_playbook, and segment_and_seat_cut_check, which all touch growth/churn decisions, but their inputs and outputs are differentiated enough for an agent to select appropriately.
All tool names use consistent snake_case and compound descriptive names, which makes the set readable and predictable in style. The names are mostly artifact/function nouns rather than a strict verb_noun pattern, but the convention is internally consistent.
Ten tools is well within the appropriate range for a GTM advisory server. Each tool covers a distinct planning or decision area, and the count is neither bloated nor too thin.
The surface covers a broad GTM decision lifecycle: competitive intel, plan assessment, PMF, paid scaling, launch, interviews, retention, partners, crisis planning, and segment economics. There are minor adjacent gaps such as dedicated positioning/messaging or sales-enablement operations, but the core advisory workflows are well represented.