Skip to main content

External tools (MCP)

Glowtify ships native connectors for the channels you publish on (Meta, LinkedIn, TikTok, Mailchimp, Klaviyo, CyberImpact, Google Ads, Shopify, WordPress, Canva, Google Analytics). Most users never need anything else.

But when you do — when the AI needs to read your CRM before drafting an announcement, or you want to publish content to Discord or Slack that Glowtify doesn't natively support — that's what MCP is for.

What MCP is​

MCP (Model Context Protocol) is an open standard that lets AI assistants talk to external tools through a common interface. Glowtify uses MCP to expose third-party apps to the chat assistant during generation.

The MCP provider Glowtify uses is Composio — a service that aggregates hundreds of app integrations behind one consistent layer (OAuth, scopes, API mappings). The catalog is deep: Gmail, Slack, Notion, Linear, GitHub, Jira, HubSpot, Salesforce, Calendly, Stripe, Discord, Asana, Trello, Airtable, Pipedrive, Zendesk, Mailchimp, Twilio, Shopify, QuickBooks, Stripe, Plaid… and several hundred more. Browse them at composio.dev/toolkits.

What you can integrate​

A non-exhaustive snapshot of the categories Composio covers — anything in this list (and several hundred more) can be wired up as either a context provider or an extra publishing destination.

  • CRM — HubSpot, Salesforce, Pipedrive, Zoho CRM, Close
  • Project management — Jira, Linear, Asana, Trello, ClickUp, Notion, Monday
  • Communication — Slack, Discord, Microsoft Teams, Gmail, Outlook
  • Helpdesk / Support — Zendesk, Intercom, Freshdesk
  • Finance & payments — Stripe, QuickBooks, Plaid, PayPal
  • Files & storage — Google Drive, Dropbox, Box, OneDrive
  • Calendars & scheduling — Calendly, Google Calendar, Cal.com
  • Forms & surveys — Typeform, Tally
  • Knowledge bases — Confluence, Coda, Notion (docs)
  • Dev & code — GitHub, GitLab, Bitbucket
  • Marketing & email (beyond native) — ActiveCampaign, Brevo, ConvertKit, Sendgrid, Twilio
  • Analytics — Mixpanel, Amplitude, Segment, Google Analytics 4
  • Web & CMS — Webflow, Framer, Ghost, Substack, Beehiiv
  • Social (beyond native) — Pinterest, Reddit, Threads, Bluesky, YouTube, Vimeo
  • Data & automation — Airtable, Zapier, n8n, Webhooks

If a tool isn't listed, check composio.dev/toolkits — the catalog moves fast.

Two distinct use cases​

Most teams reach for MCP for one of two reasons. The distinction matters because the setup, the scopes, and the way you'd phrase your chat prompt are different in each case.

1. MCP as a context provider​

The assistant reads from an external tool to inform what it writes. Read-only flow.

You're drafting a quarterly recap email and you want the assistant to pull the actual numbers from Stripe and the open deals from HubSpot. Or you're writing a customer-success story and you want it to quote real feedback from Linear. The MCP tool fetches; Glowtify uses that fetched context inside the generation prompt; the published content is still on a Glowtify-native channel (email, post, blog).

Go deeper: Use MCP to bring in context.

2. MCP as extra publishing destinations​

The assistant writes back to an external tool — using MCP as a way to publish to surfaces Glowtify doesn't have a native connector for. Write flow.

You want every approved campaign to also be cross-posted to a Discord channel. Or you want a Jira ticket created automatically when a new epic is reviewed. Or you want a Notion database row added for every published article. The MCP tool takes Glowtify's output and pushes it into the third-party system — no native connector needed.

Go deeper: Use MCP as extra publishing destinations.

Built for advanced users​

A few honest expectations before you dive in:

  • Setup is more involved than a normal connector. You're authenticating to a third-party (sometimes with multiple OAuth scopes), and you have to think about what the assistant should and shouldn't be allowed to do. There's no "easy mode" — by design.
  • The assistant decides when to invoke a tool. It uses signals from your brief and the conversation. Sometimes it'll use a tool you wired up; sometimes it won't. Tighten your brief to nudge it.
  • 3 apps maximum per chat. Don't try to plug every app at once — focus on the 2–3 that matter for the current epic.
  • Scope discipline matters. Especially for write-side MCP tools. Granting a sweeping scope ("Notion full workspace") for a tool that should only add to one database is a footgun.
caution

If you're getting started with Glowtify, skip MCP for now and lean on the native connectors. MCP rewards users who already know what they want the assistant to do and where the data they want is.

Need help wiring this?​

MCP is the area of the product where the gap between "what's possible" and "what makes sense for my workflow" is widest. If you're not sure whether MCP fits your use case, or you want to wire it to something specific — your custom CRM, an internal Notion database, a private API — write to support@glowtify.com.

We'll look at your workflow and tell you honestly whether MCP, a native connector, or a different approach (Zapier, a Glowtify ticket for native support) makes the most sense.

Articles in this section​