MCP setup & troubleshooting
This is the concrete how-to for wiring Composio-backed apps into Glowtify — the steps, the scope decisions, and the failure modes you'll actually hit.
If you're new to MCP, start with the Overview first. This page assumes you already know whether you're after a context provider or an extra publishing destination.
Where MCP lives in Glowtify
MCP lives on the Connectors page. The page has five tabs:
- Connected — native connectors you've already authorized
- Available — native connectors you can add
- Coming Soon — native connectors on the roadmap
- Request Connector — ask us for a specific native integration
- MCP — the Composio-backed catalog
Open the MCP tab and you'll see a searchable catalog of apps (Notion, HubSpot, Discord, Linear, Stripe… hundreds more). Once you connect one, it shows up in your "Connected MCP apps" list.
In any chat surface — the Epic editor chat, the homepage chat, or the email automation generation chat — you can enable up to 3 connected MCP apps per conversation.
Connecting a Composio app — step by step
- Open the Connectors page and click the MCP tab.
- Browse the catalog or search for the app you need (e.g.
Notion,HubSpot,Discord). - Click the app card → click Connect.
- The Composio OAuth modal opens. Sign into your third-party account.
- Review the scopes the app is requesting. This is the most important step — see the warning below.
- Approve. You're redirected back to Glowtify and the app card flips to Connected.
Scopes are where MCP setups go wrong. As a rule of thumb:
- Read-only scopes for context-provider use cases (the assistant just needs to fetch data).
- Write scopes only if you're using the tool as an extra publishing destination.
- Skip scopes you don't need. Most Composio apps let you tick individual scopes — be picky.
If you're unsure which scopes to grant — especially for write-heavy use cases — email support@glowtify.com before you approve. Easier than tearing down and reconnecting later.
Multi-account on the same app
Some teams need multiple accounts of the same app — two HubSpot orgs, several Notion workspaces, a prod and a sandbox Stripe. Composio supports multiple accounts per app per Glowtify Workspace.
In the MCP picker inside a chat, each account shows up separately — pick the one relevant to the current Epic before you start the conversation.
Naming hygiene matters. Rename your connections clearly — HubSpot — Acme prod, HubSpot — internal sandbox, Notion — Marketing wiki, Notion — Content log — so you don't fire a campaign at the wrong workspace.
If you don't see a rename option on the card yet, it's coming. For now the OAuth-side account name is what shows.
Enabling an MCP app in a chat
Once an app is connected, you still need to turn it on for each conversation:
- In the chat input area, open the MCP picker (icon or button — exact placement depends on the chat surface).
- Toggle on up to 3 apps.
- The assistant now sees those tools for the rest of the conversation.
- Toggle one off mid-chat and it's gone from the assistant's context for the next message.
This per-conversation gating is intentional — it keeps each chat focused and avoids the assistant pulling tools you didn't expect.
OAuth & token lifetime
Token lifetimes vary by app. Some last months, some auto-refresh in the background — Composio handles the refresh dance transparently in most cases.
When a token finally does expire (or gets revoked from the third-party side), the connection card flips to Needs reconnect. Click Reconnect and walk through OAuth again — it's a few seconds.
Troubleshooting
"The tool didn't get invoked when I asked"
The assistant decides when to invoke a tool — sometimes it doesn't. Quick checks:
- Open the MCP picker — is the app actually toggled on for this conversation?
- Make your prompt explicit:
USE the HubSpot tool to fetch the open deals— caps help nudge. - Try a fresh chat — long threads sometimes confuse the model about which tools are still relevant.
"Composio OAuth error during setup"
Most common cause: the third-party is blocking the OAuth redirect because of corporate SSO or admin-only-install rules. A few things to try:
- Sign in from a different account (a personal admin account, for instance) and re-attempt.
- Confirm the app is actually in the Composio catalog — search at composio.dev/toolkits.
- If it's still failing, email support@glowtify.com with the OAuth error message — we can usually diagnose from the error code.
"The tool returned an error during generation"
The assistant should surface the error inline in the chat. Common causes:
- Scope too narrow — you authorized read but the model tried to write. Reconnect with the right scopes.
- Rate limit — the third-party throttled you. Wait it out or upgrade your plan on their side.
- Third-party API outage — check the app's status page.
"Connection shows 'Needs reconnect'"
Token expired or got revoked at the third-party (admin yanked it, password rotation, security event). Click Reconnect on the card and re-authorize.
"Multiple connected accounts but the wrong one was used"
By default Glowtify uses the first matching connection. To avoid the wrong one firing:
- In the MCP picker, explicitly select the right account before starting the chat.
- Or rename your connections (see Multi-account) so the wrong one is obvious at a glance.
"I don't see the MCP tab in Connectors"
The MCP feature shipped in June 2026 — if your account is older, the tab should already be visible. If it really isn't, email support@glowtify.com; it's likely a feature-flag issue we can flip in seconds.
When to email support
Reach out to support@glowtify.com when:
- You want to wire MCP to a tool that isn't in the Composio catalog. (Composio is deep — hundreds of apps — so most things are there, but not everything.)
- You're unsure which scopes to grant for a write-heavy use case, and you'd rather get it right the first time.
- You're hitting a bug and the troubleshooting above didn't clear it.
We'd rather hear from you before you blow away a connection and rebuild it three times.