Overview
trumpet’s MCP server connects your AI assistant directly to your trumpet workspace, giving you instant access to your sales rooms (pods) and their data.
With trumpet MCP, you can search across your pods using powerful filters or fetch detailed information on any individual room, all without leaving Claude or ChatGPT.
🚀 Coming soon: trumpet MCP is currently going through the approval process for both the Claude and ChatGPT directories.
If you don't want to wait for the official app, reach out to us to be part of our Beta program, and we can give you early access!
What you can do with trumpet MCP
MCP tools (Trumpet)
Search across Pods (search tool)
Find Pods using a text query. The backend matches it (case-insensitive) against:
Pod title
Pod description
Recipient company
CRM ID (when stored on the Pod)
Optional filters to narrow results
Filter | Purpose |
| Pods created by a specific Trumpet user |
| Pods created on or after this time (ISO 8601 datetime) |
| Pods created on or before this time (ISO 8601 datetime) |
| Match recipient company |
| Match the CRM id stored on the Pod |
| Restrict to Pod deal status: |
Limits and data scope
Results are capped at 15 Pods, ordered by creation date (newest first) — not by engagement score.Each matching Pod in the response includes title, Pod id, CRM linkage when present, created date, creator, and live URL.
Fetch full Pod details (fetch tool)
Retrieve rich engagement and context for a single Pod using its trumpet Pod id from search (or elsewhere in your workflow).
The response includes items such as:
Title, URL, description, recipient company
Engagement score and how it relates to activity
CRM id, CRM name, and CRM object type when linked
Created date
Stakeholder coverage and viewer job-title summary
When statistics exist: views, comments, downloads, link clicks, shares, video and voice plays, time on page, last viewed, and related metrics
Optional AI analysis: fetch supports an analysis flag (boolean, default false). When set to true, the response may include an extra Coach Casey narrative section if Coach Casey is enabled for your brand. If not, you still receive the standard formatted Pod details.
Prompt template: pod-research-plan
The server registers an MCP prompt that guides multi-step work: search by account (including cases with multiple Pods), fetch the most relevant rooms, and summarize engagement, signals, risks, and which Pod is which.
Authentication (OAuth 2.0)
MCP requests require a valid OAuth token for your trumpet account. We support Dynamic Client Registration
First-time connection typically opens a browser flow at trumpet to approve access; the exact steps depend on the AI product you use.
Example use cases
Example 1 — Full picture before a call
“Get everything you can on our Acme Corp pod.”The assistant searches for Acme (and related terms if needed), picks the right Pod(s), then fetches each for full engagement and CRM context.
Example 2 — From CRM into trumpet
“Open the trumpet room tied to this CRM deal.”The assistant searches using the deal or opportunity id (and optional filters), then fetches the Pod you care about for full detail—alongside CRM data from your CRM’s own tools if available.
Example 3 — Recent rooms that might need attention
“Show pods from the last week with weak engagement.”The assistant searches with a creation-date window and relevant keywords; remember results are newest-first (up to 15), not pre-ranked by engagement, so it may fetch selected Pods to compare engagement scores and metrics.
Example 4 — Short narrative on top of metrics
“What should we do next on this pod?”The assistant fetches with analysis: true when Coach Casey is enabled to add a concise narrative on top of the standard stats.
Privacy
See our privacy policy:
https://trumpet.app/privacy
Support
Need help? Contact us at:
support@sendtrumpet.com