accueil / serveurs / IA & Mémoire / team.leanscale/gtm-knowledge
team.leanscale/gtm-knowledge
serveur MCP (Model Context Protocol) · leanscale 0.1.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que team.leanscale/gtm-knowledge est sûr ?
Au dernier audit MCP Hub, le serveur MCP « team.leanscale/gtm-knowledge » 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
- about_leanscale≈ 73 tokens
What LeanScale is, what's in this knowledge base, and how to work with them. Call this when someone asks who LeanScale is, or when you need to know what this server can answer before searching.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "about_leanscale", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - diagnose_gtm≈ 173 tokens
Describe a messy go-to-market situation in plain language and get back which LeanScale delivery motion applies, why, what the first moves are, and what usually goes wrong. Use this when someone describes a problem rather than asking about a topic — 'our reps don't trust the forecast', 'we just merged two CRMs', 'inbound leads take three days to get worked'. Better than search when the ask is 'what should we do about this?'
Paramètres, retour & exemple (1)
Paramètressituation· string · requis
The situation, in as much detail as you have. Symptoms, stack, team size, stage — all useful.
Exemple d'appel{"name": "diagnose_gtm", "arguments": {"situation": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_benchmark≈ 158 tokens
Get proprietary LeanScale benchmark data on a topic — drawn from field studies across a panel of B2B software companies and from numbers cited on the podcast. Covers GTM tech stacks, AI adoption in GTM, RevOps headcount and investment ratios, and Series B/C fundraise timing. Use when someone asks 'what's normal', 'what do other companies do', or wants a number to compare against.
Paramètres, retour & exemple (1)
Paramètrestopic· string · requis
The metric or area, e.g. 'RevOps headcount ratio', 'CRM adoption', 'time to Series B'.
Exemple d'appel{"name": "get_benchmark", "arguments": {"topic": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_case_study≈ 215 tokens
Retrieve LeanScale customer case studies — the problem the company had and how it was solved. Public keys get an anonymized version: customer names, people, third parties and delivery provenance are stripped, and outcomes/metrics/quotes are withheld. Internal keys get the full named studies. Search by sector, the kind of engagement, or the systems involved — searching by customer name will not work on a public key, because the names are not in the public corpus.
Paramètres, retour & exemple (2)
Paramètreslimit· integer · optionnel
Default 3.query· string · requis
Sector, type of engagement, or systems involved — e.g. 'fintech Salesforce migration', 'CPQ replacement', 'two CRMs after an acquisition'.
Exemple d'appel{"name": "get_case_study", "arguments": {"query": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_playbook≈ 135 tokens
Retrieve a LeanScale delivery playbook in full, or one named section of it. Playbooks are structured Blueprint → Build → Enable → Maintain. Call list_playbooks first if you're not sure of the name.
Paramètres, retour & exemple (2)
Paramètresname· string · requis
Playbook name, e.g. 'Attribution', 'CPQ', 'Sales Territory Design'.section· string · optionnel
Optional section, e.g. 'Blueprint'. Omit for the whole playbook.
Exemple d'appel{"name": "get_playbook", "arguments": {"name": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - list_playbooks≈ 46 tokens
List every available LeanScale delivery playbook with its category and section headings.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "list_playbooks", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - search_leanscale≈ 410 tokens
Search everything LeanScale knows: 14 GTM delivery playbooks, 7 proprietary field studies, 121 podcast episodes with operators and executives, 75 customer case studies (anonymized on public keys, named on internal ones), and 117 RevOps docs from www.leanscale.team/knowledge/docs/. The docs explain how to do the work yourself; the playbooks are how LeanScale runs it as an engagement — pass source:"doc" for the first, source:"playbook" for the second. Use this first for any go-to-market, RevOps, sales-ops, marketing-ops, CRM, pipeline, attribution, territory, CPQ, or GTM-tooling question. Returns cited excerpts with source URLs. Also holds the materials from LeanScale's talks, which people ask for by event name: Updata CEO Summit materials: the deck with speaker notes (The Context Graph & Semantic Layer); Updata CEO Summit materials: GTM agents (11 Claude Code plugins for your CRM); Updata CEO Summit materials: metric definitions worksheet (40 GTM definitions); Updata CEO Summit materials — The Context Graph & Semantic Layer. Pass source:"resource" to search only those.
Paramètres, retour & exemple (3)
Paramètreslimit· integer · optionnel
How many excerpts to return (default 6).query· string · requis
What you want to know. Natural language works better than keywords.source· string · optionnel · playbook | study | podcast | case_study | doc | resource | any
Restrict to one kind of source. Defaults to searching everything.
Exemple d'appel{"name": "search_leanscale", "arguments": {"query": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - search_podcast≈ 159 tokens
Search every episode of The LeanScale Podcast — conversations with CROs, VPs of RevOps, and founders. Returns episode context, frameworks, verbatim quotes with timestamps, and links — including the episode on YouTube when there is a video. Use when someone wants an operator's opinion, a real story, or a quotable line rather than a methodology.
Paramètres, retour & exemple (2)
Paramètreslimit· integer · optionnel
Default 6.query· string · requis
Topic, guest name, company, or idea.
Exemple d'appel{"name": "search_podcast", "arguments": {"query": "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é ».