Abency
Run a marketing agency's social, SEO, ads, WordPress and email from an AI agent.
Search your sales content library, answer seller questions and query CRM deals.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Highspot MCP server connects the Highspot sales enablement platform to Claude, ChatGPT and any MCP-compatible agent. It exposes 7 tools that search your content library, answer seller questions, look up CRM opportunities and assemble a pitch. Sign-in is OAuth 2.0, and the server is in beta — Highspot issues your OAuth client through your account team.
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
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.
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.
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.
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.
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.
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.
developers.highspot.com/robots.txt disallows the host generally but explicitly allows /viewer.) · retrieved 2026-08-19app.highspot.com and the path-append form returns 404) · retrieved 2026-08-19app.highspot.com/signin as of 2026-08-19, so no public permission or plan documentation could be read) · retrieved 2026-08-19https://mcp.highspot.com/mcp — 2026-08-19 (a plain GET request returns HTTP 405 with Allow: POST; an anonymous initialize returns HTTP 401 with WWW-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-19Connect Highspot once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.