Breakthrough

io.breakthroughsalesPublished by breakthroughsales.ioOfficial publisherv0.24.1Updated Nov 5, 2026

Connects your AI assistant to a living playbook distilled from your team's sales calls.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that connects an AI assistant to a living sales playbook distilled from your team's sales calls.

What you can do
  • The listing gives no tool list, so capabilities are known only from the description: it links an assistant to a sales playbook built from the team's recorded sales calls.
  • The playbook is described as living, implying it is kept up to date from call content rather than being a static document.
  • No further actions, resources or outputs are documented in the supplied material.
When to use it
Consider it when a sales team wants an assistant to draw on guidance derived from its own sales calls, for example to prepare for or review conversations. It is not suitable if you need a documented tool list before connecting.
Requirements
A remote streamable HTTP endpoint at mcp.breakthroughsales.io. OAuth authentication is required; no environment variables or headers are declared. A Breakthrough account with access to the team's sales call data is implied.
Before you install
OAuth grants the server access on your behalf, and the playbook is derived from your team's sales calls, so call recordings or transcripts are likely processed by a third party. Review what data the OAuth consent covers before connecting. No tools are listed, so what the assistant can read or change cannot be verified from this listing.

Installation

In SourceWeft

  1. Open Breakthrough in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.breakthroughsales%2Fbreakthrough/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "breakthrough": {
      "type": "http",
      "url": "https://mcp.breakthroughsales.io/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.24.1LatestNov 5, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.