Linear, Notion, GitHub in Sume: why there is no Connect button
Sume lists Linear, Notion and GitHub as coming soon because no reviewed read-tool allowlist or registered OAuth app exists in its stack for them yet.
Linear, Notion and GitHub are in Sume's catalog but have no Connect button. Sume's rule is that a provider goes live only with a registered OAuth app and a reviewed read-tool allowlist, and for these three neither exists in the stack yet. The catalog doc says not to add callback clients or enable Connect from a catalog change alone.
What the doc records
docs/operations/integrations-catalog.md has a table titled "Official MCP URLs not wired yet". It records that Linear, Notion and GitHub each have a documented hosted MCP, and gives a reason each stays coming soon: the tool allowlist was not reviewed for Linear and Notion, and GitHub uses a host-implemented authorization that is not the PKCE pattern used for Meta, Slack and the Google connectors.
What a reviewed allowlist means
For Meta Ads it was 52 exact reads out of 97 tools on 2026-09-09, each checked against an input-schema snapshot. That is the work that remains for every new provider, because Sume never relies on a server's own read-only claim. See readOnlyHint is not authorization.
Other catalog-only providers
Airtable, WhatsApp Business, ManyChat, Dropbox, OneDrive, Frame.io, Pinterest, YouTube, TikTok Ads, Webflow, Supabase and Figma have no verified hosted MCP and OAuth pair in the doc. The plan is a follow-up for each once an official URL and an app exist.
Meanwhile
Webhook-driven flows work today without a connector. A Linear or Notion automation can call the Sume API and receive job events by webhook; see the Linear 5-second webhook post and can Notion send webhooks. That is your code calling Sume, not a workspace integration.
What would change it
Three things together: an official hosted MCP and an OAuth app registered in Sume's stack, a reviewed list of read tools with input-schema snapshots, and the availability gate flipped for that provider. A catalog edit alone is explicitly not enough, and the doc forbids adding callback clients from one.
So when you do not see a Connect button, it is a deliberate safety step, not a missing UI.
Related posts
More in Integrations
- Linktree video background 50 MB limit: bitrate budget by length
Linktree video backgrounds loop with no time limit but a 50 MB cap. A 15-second loop can average 26.7 Mbps, a 60-second one 6.7 Mbps. Table and trim steps.
- Linktree video background 9:16 or 16:9: make both from one clip
Linktree's page pairs 9:16 with landscape and 16:9 with portrait. Cut both ratios from one Sume clip with video filter crop fractions: 0.3164 wide, x 0.3418.
- Linktree video background is muted: drop the audio with trim
Linktree plays a video background on a loop with the sound muted, so audio only adds bytes. Send audio set to drop on Sume video trim, then probe has_audio.
- Can a MAI-Voice-2.1 WAV join a Sume timeline? Hosted audio only
Sume timeline audio joins only Sume-hosted files, and the import route takes TikTok or Instagram URLs, so a MAI-Voice-2.1 file stays outside. What to do.
Written by Sume