Skip to main content

MCP Client

Connect apps like Notion, HubSpot, Linear, Granola, and Sybill so CoPilot can pull their data into your Pods - no tab-hopping or copy-pasting required.

Written by Maddi Rose

Overview

MCP Client lets CoPilot connect out to the other apps your team already works in - Notion, HubSpot, Granola, Sybill, Glean, Linear(and more) and pull their data straight into trumpet.

CoPilot can then use that context to build or update Pod content, create widgets, or simply answer questions. It can also write data back to those tools, though the main use case is pulling context in.

💡 MCP Client is different from the trumpet MCP Server. MCP Client is CoPilot reaching out to other apps for context. The MCP Server is the reverse - it lets you connect Claude or ChatGPT to trumpet to query your Pods from there.

Why use it

Deal data lives in your CRM, call notes live in Granola or Sybill, project updates live in Linear, and company knowledge lives in Notion or Glean. MCP Client means you don't have to tab-hop and copy-paste that context into a Pod - one prompt, and CoPilot pulls the right information from the tools you already use and turns it into polished, buyer-ready content.

If a tool you use isn't on the curated list, your admin can add any custom MCP server, so trumpet fits into your stack rather than the other way around.

How to set it up

For admins: managing available servers

  • Admins control which MCP servers are available to the workspace, and can toggle each one between Enabled and Disabled

  • To add a server that isn't on the list, click + Add Server and provide:

    • Server name and URL (required)

    • Description (optional)

    • OAuth Client ID and Secret (optional)

    • Custom headers (optional)

For everyone: connecting your account

  • Tap Connect on any enabled server

  • You'll be taken to that tool to authorise the connection (standard OAuth), then brought straight back to trumpet

Using it in CoPilot

  • Open CoPilot in a Pod

  • Tap the + button in the chat input (same pattern as ChatGPT or Claude)

  • Your connected MCP servers appear under More

  • Select the server(s) you want CoPilot to use for that request - even if it's already connected, it needs to be added to the chat first

  • Prompt as normal. CoPilot fetches what it needs from the connected tool, then follows the same widget creation and Pod editing flow you already know

Example use cases

Pull deal context from HubSpot

Pull live deal information from HubSpot and have CoPilot create a "where we're at" summary widget for buyer execs, covering deal value, timelines, and next steps.

Turn Notion docs into widgets

Find an internal doc in Notion, summarise it, and drop it into a Pod as a widget without leaving trumpet.

Meeting notes to follow-ups

Pull call notes from Granola or Sybill into a Pod so the buyer-facing summary reflects what was actually discussed.

Company knowledge on tap

Use Glean to surface internal knowledge while building or updating Pod content.

Synthesis across tools

Combine sources in one prompt - for example, CRM data plus meeting notes - and have CoPilot turn it into a single, polished Pod section.

Refresh a Pod

Refresh Pod content from all your source tools rather than manually re-copying updated information.

Good to know

  • Pulling large amounts of external data can add some latency to CoPilot's response

  • Each connected app has its own limits on what information it allows to be read into trumpet

Support

Need help? Contact us at: support@sendtrumpet.com

Did this answer your question?