Skip to content

LeanScale GTM Knowledge

by leanscale.team · remote · no sign-in to list tools · v0.1.0 · published by team.leanscale

GTM operations knowledge: delivery playbooks, field studies, benchmarks and operator interviews.

Changes · 1
CompareRegistry entry

8 tools: 1 change things and 7 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http gtm-knowledge https://mcp.leanscale.team/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

8 tools

Changes things 1Claude Code: ask
  • about_leanscaleWhat LeanScale is, what's in this knowledge base, and how to work with them.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 7Claude Code: allow
  • diagnose_gtmDescribe 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.No findings

    Why it is in this group

    • The description's first verb is "describe": a word for reading.
    Description, as the server wrote it
    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?'
  • get_benchmarkGet 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.No findings

    Why it is in this group

    • The name "get_benchmark" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_case_studyRetrieve LeanScale customer case studies — the problem the company had and how it was solved.No findings

    Why it is in this group

    • The name "get_case_study" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_playbookRetrieve a LeanScale delivery playbook in full, or one named section of it.No findings

    Why it is in this group

    • The name "get_playbook" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • list_playbooksList every available LeanScale delivery playbook with its category and section headings.No findings

    Why it is in this group

    • The name "list_playbooks" says "list": a word for reading.
    Description, as the server wrote it
    List every available LeanScale delivery playbook with its category and section headings.
  • search_leanscaleSearch everything LeanScale knows: 14 GTM delivery playbooks, 7 proprietary field studies, 121 podcast episodes with operators and executives, 75 customer case studies (anonymized …No findings

    Why it is in this group

    • The name "search_leanscale" says "search": a word for reading.
    Description, as the server wrote it
    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.
  • search_podcastSearch every episode of The LeanScale Podcast — conversations with CROs, VPs of RevOps, and founders.No findings

    Why it is in this group

    • The name "search_podcast" says "search": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http gtm-knowledge https://mcp.leanscale.team/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__gtm-knowledge__search_leanscale",
      "mcp__gtm-knowledge__diagnose_gtm",
      "mcp__gtm-knowledge__get_playbook",
      "mcp__gtm-knowledge__list_playbooks",
      "mcp__gtm-knowledge__get_benchmark",
      "mcp__gtm-knowledge__search_podcast",
      "mcp__gtm-knowledge__get_case_study"
    ],
    "ask": [
      "mcp__gtm-knowledge__about_leanscale"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as gtm-knowledge. Review it before you use it.