Highspot
by Highspot
Search your sales content library, answer seller questions and query CRM deals from your AI assistant. 7 tools, a real mcp:write scope, and a beta gate that needs your Highspot account team before you can connect.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Highspot via MCP
https://mcp.highspot.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Highspot Tools & Capabilities (7)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Frequently asked questions
Can I just connect the Highspot MCP server myself?
No. Highspot's own MCP document opens by stating the server is in beta and asking you to contact your account team or alliances manager to onboard. Anthropic's directory reinforces this by listing a custom OAuth client id and client secret as fields you must supply, so there is no self-service connect button and no public sign-up path for this connector.
Does the Highspot MCP server send a pitch to a customer?
No, generate_pitch creates a pitch and hands you a link to it. Highspot's document says the tool creates exactly one AI-generated pitch from specific content items, and that what the user sees is a link to that pitch with the selected content added. Delivery to a recipient is a separate step you take yourself inside Highspot after reviewing what was assembled.
Why does Highspot ask for write access when all seven tools look like reads?
Because one tool genuinely writes. The server's OAuth descriptor advertises mcp:read and mcp:write, and Anthropic's directory labels the connector Read and write. The write half is generate_pitch, which creates a new pitch object in your Highspot domain. The other six tools read content, answers, recommendations and CRM deal records without changing anything.
Does the Highspot MCP server reach my Salesforce or CRM data?
Yes, indirectly. Highspot states that get_deal_answer answers questions about a CRM opportunity by combining CRM data with Highspot engagement, and lookup_deal finds the right CRM record from an opportunity name. That data arrives through the CRM connection your Highspot administrator already configured, so an assistant reaches it through a grant you made to Highspot.
What does the Highspot MCP server actually return from my content library?
Full document text, not just titles and links. Highspot's document says get_item_content pulls the full text or file of an item, and describes this as happening behind the scenes when an agent needs to read or analyse content. Search and recommendation results return document lists with metadata, and get_content_answer returns a synthesised answer with links to its source documents.
Which MCP clients work with the Highspot connector?
Any application that has implemented an MCP client, per Highspot's stated requirement. Its document names Claude.ai specifically and marks it as coming soon at the time of writing, which reflects the beta status rather than a technical restriction. The transport is streamable HTTP, so a standard MCP client with your issued OAuth credentials is what the server expects.
Sources
- Highspot MCP overview, "Using Highspot's MCP Server" — https://engage.highspot.com/viewer/b5e7f88cbce41d93deb6aa291a94f961 (fetched 2026-08-19. This is the documentation URL Anthropic's directory publishes for this connector. It is not a documentation site: it is a Highspot buyer-engagement viewer page — the vendor published its MCP documentation as a piece of Highspot content, delivered through its own pitch product. The page is client-rendered; the underlying PDF was retrieved from the public asset the same page references.
developers.highspot.com/robots.txtdisallows the host generally but explicitly allows/viewer.) · retrieved 2026-08-19 - RFC 9728 protected resource descriptor — https://mcp.highspot.com/.well-known/oauth-protected-resource/mcp (fetched 2026-08-19; the root form 302s to
app.highspot.comand the path-append form returns 404) · retrieved 2026-08-19 - RFC 8414 authorization server descriptor — https://app.highspot.com/.well-known/oauth-authorization-server (fetched 2026-08-19; the path-insert form returns an identical body) · retrieved 2026-08-19
- Highspot privacy policy — https://www.highspot.com/privacy/ (fetched 2026-08-19) · retrieved 2026-08-19
- Highspot help centre and developer portal — https://help.highspot.com/ and https://developers.highspot.com/ (both redirect to
app.highspot.com/signinas of 2026-08-19, so no public permission or plan documentation could be read) · retrieved 2026-08-19 - Live authentication probe on
https://mcp.highspot.com/mcp— 2026-08-19 (a plain GET request returns HTTP 405 withAllow: POST; an anonymousinitializereturns HTTP 401 withWWW-Authenticate: Bearer realm="mcp-server"naming the descriptor above. No tool was called, no pitch was generated and no OAuth flow was started.) · retrieved 2026-08-19 - Anthropic connector directory — https://claude.ai/directory/9c052ba1-9319-48bf-8ccd-adb042a24dc2 (snapshot 2026-08-16) · retrieved 2026-08-16
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Sales & CRM
- Developer
- Highspot
- Tools
- 7
- Domain
- mcp.highspot.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.