# Trumpet (sendtrumpet.com): MCP server status, API access gate and what it does

> Digital sales room / "Pod" builder for buyer-facing deal collateral, tracking granular buyer engagement... Official MCP, Free to start. Checked 2026-08-24.

*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).*

---
[Directory](../index.md) /
[Proposals & Deals](../categories/proposals-deals.md) /
Trumpet (sendtrumpet.com)

# Trumpet (sendtrumpet.com)

[Official MCP](../mcp/official.md)
[Free to start](../gates/free.md)
[Proposals & Deals](../categories/proposals-deals.md)
RESEARCHED
Checked 2026-08-24

> **RESEARCHED** Facts from public sources with URLs. No usage claims. Nobody has run this tool. The other tier is BENCH-TESTED, which means Andrew personally ran the tool on a stated date and cannot be bought at any price. Across the whole directory that count is 0.

Vendor: [sendtrumpet.com](https://sendtrumpet.com) · entry id 13-trumpet · source 13-proposals-deals.md line 223

**What it does**
Digital sales room / "Pod" builder for buyer-facing deal collateral, tracking granular buyer engagement (clicks, time-on-page, returning champions) across the deal cycle.

**AI features, separated from automation with an AI label on it**
No independently verified core-product AI/ML claims beyond engagement tracking (which is instrumentation, not AI); the MCP server itself is the standout AI-facing feature, explicitly marketed for "surfacing signals" and "diagnosing deal risk" from an AI client.

**RevOps role**
Buyer-engagement / digital-sales-room signal layer, notable as one of the few tools in this file with both a real free tier AND a free-tier-accessible official MCP server.

**MCP server**

- **Status bucket**: Official MCP

- **Auth**: unknown - vendor states it is "installable in five minutes with no engineering required," implying a simple hosted-connector flow, but the specific auth mechanism (OAuth vs. key) isn't detailed in the announcement.

- **Parsed URLs**: 1 found in the mcp_url field

The vendor ships and maintains the server itself. A wrapper built by Zapier, Composio or a similar third party does not count as official. The status was established on 2026-08-24 and has not been re-fetched since.

mcp_status, verbatim from the file:

official

mcp_url, verbatim from the file:

https://www.sendtrumpet.com/blog-posts/introducing-trumpet-mcp

- [https://www.sendtrumpet.com/blog-posts/introducing-trumpet-mcp](https://www.sendtrumpet.com/blog-posts/introducing-trumpet-mcp)

**Access gate**

- **Gate bucket**: Free to start

- **Can a solo operator reach it**: Yes, without talking to anyone

api_gate, verbatim from the file:

free (generous). Trumpet is free to get started for everyone with no credit card required; paid plans start at £29/month, with Enterprise custom. The MCP server works across the free tier per the announcement, not gated to a paid plan.

**API documentation**

No documentation URL recorded.

263 of 293 entries are in the same position. Blank is legal and it is published as blank.

**GitHub health**

Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.

The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.

**Jobs it can do**

- [Create and send a prospecting video](../jobs/create-and-send-prospecting-video.md)
- [Read outreach performance](../jobs/read-outreach-performance.md)
- [Create a digital sales room](../jobs/create-digital-sales-room.md)

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.

Tagged by machine-pass on 2026-08-25 against the closed 55 job vocabulary. 271 of 293 entries carry at least one tag; 827 tags are assigned in total.

**Also listed in another category**

This page is the canonical home. The listing below is the same product, counted separately in the source markdown.

- **Listed as**: Trumpet

- **Category**: [Video Prospecting](../categories/video-prospecting.md)

- **MCP status there**: Official MCP

- **Gate there**: Gate unknown

- **Source**: 08-video-prospecting.md line 261

- **Canonical page**: [Trumpet (sendtrumpet.com)](../tools/trumpet.md)

What that listing says it does: Digital-sales-room / buyer-facing microsite platform ("Pods") for revenue teams, with a built-in webcam/screen-recording tool for sellers to send personalized welcome and post-demo recap videos embedded in the buyer's deal microsite, plus mutual action plans and engagement analytics.

16 of the 293 entries are cross listed like this. They are why the entry count is 293 and the unique product count is 277. The canonical home is declared in INDEX.md, not chosen by the parser.

**Sources**

- [https://www.sendtrumpet.com/blog-posts/introducing-trumpet-mcp](https://www.sendtrumpet.com/blog-posts/introducing-trumpet-mcp)
- [https://www.sendtrumpet.com/pricing](https://www.sendtrumpet.com/pricing)
- [https://www.sendtrumpet.com/blog-posts/best-mcp-servers-for-sales-teams-2026](https://www.sendtrumpet.com/blog-posts/best-mcp-servers-for-sales-teams-2026)

3 source URLs. Raw sources field, verbatim:

https://www.sendtrumpet.com/blog-posts/introducing-trumpet-mcp, https://www.sendtrumpet.com/pricing, https://www.sendtrumpet.com/blog-posts/best-mcp-servers-for-sales-teams-2026

**Notes, verbatim from the file**
Trumpet also publishes its own "10 Best MCP Servers for Sales Teams" roundup - a secondary source worth cross-checking against this directory's own findings in a future pass, since it's a competitor's self-interested list, not neutral.

**Provenance**

- **Entry id**: 13-trumpet

- **Source file**: 13-proposals-deals.md

- **Source line**: 223

- **Tier**: RESEARCHED

- **last_checked**: 2026-08-24

- **Data baked**: 2026-08-25

Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the [methodology page](../methodology.md).
