# Highspot: products, MCP servers and connect URLs, one vendor page > Highspot (highspot.com): 1 product in The GTM MCP Directory, 1 with an official MCP server, 0 answering a live handshake, 0 tools catalogued. Data baked 2026-09-27. *Markdown twin of the HTML page at the same path. Same content, no navigation, no styling, no scripts. Links below point at other twins. Site map for machines: [llms.txt](../llms.txt). The whole dataset: [directory.json](../data/directory.json).* *Maintained by Andrew McGuire (https://andrewcmcguire.com), who also publishes https://gtmsignals.co and https://justsaid.ai.* --- [Directory](../index.md) / [Vendors](../vendors/index.md) / Highspot # Highspot 1 product in the directory 1 official MCP server 0 live handshakes Data baked 2026-09-27 Vendor domain: [highspot.com](https://highspot.com) · vendor page id highspot-com **The rollup** - **Products**: 1, facts checked by hand 2026-09-07 - **Official MCP servers**: 1 of 1, as recorded on 2026-09-07 - **Community MCP servers**: 0 of 1 - **Live handshake**: 0 of 1 answered an MCP initialize, 1 probed, 2026-09-04 - **Repo local**: 0 of 1: a server you install and run yourself - **Docs only**: 1 of 1: the recorded URL is a page about the server, not the server - **Tools catalogued**: not measured on any product of this vendor - **Bench tested**: 0 of 1 here, 1 of 1,252 across the directory - **Ships a CLI**: 0 of 1 official, 1 community only, 0 none found, harvested 2026-09-27 - **GitHub organisation**: [github.com/highspot](https://github.com/highspot), tied to the domain with evidence 2026-09-08 A live handshake means the URL answered an MCP initialize as a server on the probe date. It is liveness and nothing more: nobody has run its tools. A tool being catalogued means a server names it, by answering tools/list, in its own source, or in the vendor's documentation. None of them has been called. A tool count of 0 means not measured, never zero tools. **Products, 1** ### [Highspot](../tools/highspot.md) Sales enablement platform (content management, training) that has added a genuine call-recording and conversation-intelligence module on top of its core content product. [Official MCP](../mcp/official.md) · [Enterprise only](../gates/enterprise-only.md) [Conversation Intel](../categories/conversation-intel.md) RESEARCHED - **Endpoint probe**: docs page, not an endpoint, 2026-09-04 - **Connect URL**: [https://www.highspot.com/product/mcp-server/](https://www.highspot.com/product/mcp-server/) (docs page) - **Tools catalogued**: not measured - **last_checked**: 2026-09-07 **The gates, in plain words** 1 of 1 enterprise only, API access needs a contract. The gate is the api_gate field on each product entry, established by hand on the last_checked date shown above. It records whether a solo operator can get API access without a contract. Money is not tracked. **Jobs the vendor says its products do** - [Fetch a call transcript](../jobs/fetch-call-transcript.md) - [Summarize a meeting](../jobs/summarize-meeting.md) - [Extract deal signals from calls](../jobs/extract-deal-signals-from-calls.md) - [Retrieve sales content](../jobs/retrieve-sales-content.md) - [Score rep performance](../jobs/score-rep-performance.md) 5 distinct job labels, the union across 1 product, tagged 2026-08-25. A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records. **Connect URLs** - [https://www.highspot.com/product/mcp-server/](https://www.highspot.com/product/mcp-server/) (Highspot, docs page, probed 2026-09-04) An endpoint is where an agent connects. A docs page is where a person reads about connecting. Both are published because both are what the probe found; an agent needs the first. **Command line** ### [Highspot](../tools/highspot.md) highspot community CLI This is a third party's CLI. It was published by somebody other than the vendor, so it is that author's surface for the vendor's API and not the vendor's published surface. The two must not be read as the same thing. ``` npm install -g highspot-cli ``` quoted from [https://www.npmjs.com/package/highspot-cli](https://www.npmjs.com/package/highspot-cli) on 2026-09-27, via npm, a third party source harvested 2026-09-27, all on the [tool page](../tools/highspot.md). A CLI being listed means the harvest found an install command or a package on a stated date. Nobody has run it. Every command is quoted verbatim from the URL beneath it. **On GitHub** [github.com/highspot](https://github.com/highspot) tied to the vendor by rule 3, account website https://www.highspot.com has the vendor's domain, confidence strong - **Public repositories**: 5, forks excluded, as read on 2026-09-08 - **Mention MCP**: 0 of them - **Look like CLIs**: 0 of them - **Latest push**: 2022-10-12 The five most recently pushed, on 2026-09-08: | Repository | Kind | Description | Stars | Pushed | Latest release | |---|---|---|---|---|---| | [accelerate-starter-code-fe](https://github.com/highspot/accelerate-starter-code-fe) | docs or examples | | 0 | 2022-10-12 | | | [coding-interview-mobile-app](https://github.com/highspot/coding-interview-mobile-app) | app | | 0 | 2022-09-21 | | | [highspot-accelerate-starter-code-frontend](https://github.com/highspot/highspot-accelerate-starter-code-frontend) | docs or examples | | 0 | 2022-09-21 | | | [Backbone](https://github.com/highspot/Backbone) | other | | 0 | 2021-10-18 | | | [git-sparse-checkout-buildkite-plugin](https://github.com/highspot/git-sparse-checkout-buildkite-plugin) | plugin or integration | Buildkite plugin that performs a bare-bones partial clone of a repo and then a sparse-checkout of specified directories | 0 | 2021-08-19 | | Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08. **What this page does not claim** A job tag is a vendor claim: it means the vendor says the product does this, and it is not a test result. A listed tool has not been run: the catalogue says what an agent could try, not what works. 1 of 1,252 directory entries are bench tested, meaning somebody personally ran the tool on a stated date, and 0 of this vendor's 1 product are among them. There is no verdict here on whether this vendor is better than another. Vendor pages group the directory's canonical product entries by vendor_domain. The vendor name is the product display name that matches the domain when several products share it; nothing on this page is typed by hand. Data baked 2026-09-27 by build_directory.py (phase 1).