Model Context Protocol (MCP) server for Apollo.io API integration
Nothing to run from here
LeanScale GTM Knowledge is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
8
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
GTM operations knowledge: delivery playbooks, field studies, benchmarks and operator interviews.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http leanscale-gtm-knowledge-mcp https://mcp.leanscale.team/mcp
# 2 — ask your agent for something these tools do
# search_leanscale, diagnose_gtm, get_playbook and 5 more
LeanScale GTM Knowledge costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
LEAll 1 server
leanscale1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http leanscale-gtm-knowledge-mcp https://mcp.leanscale.team/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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:"
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | What you want to know. Natural language works better than keywords. |
| source | string | no | Restrict to one kind of source. Defaults to searching everything. |
| limit | integer | no | How many excerpts to return (default 6). |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| situation | string | yes | The situation, in as much detail as you have. Symptoms, stack, team size, stage — all useful. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Playbook name, e.g. 'Attribution', 'CPQ', 'Sales Territory Design'. |
| section | string | no | Optional section, e.g. 'Blueprint'. Omit for the whole playbook. |
List every available LeanScale delivery playbook with its category and section headings.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | The metric or area, e.g. 'RevOps headcount ratio', 'CRM adoption', 'time to Series B'. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Topic, guest name, company, or idea. |
| limit | integer | no | Default 6. |
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 wor
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Sector, type of engagement, or systems involved — e.g. 'fintech Salesforce migration', 'CPQ replacement', 'two CRMs after an acquisition'. |
| limit | integer | no | Default 3. |
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.
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install LeanScale GTM Knowledge or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish LeanScale GTM Knowledge can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.