Connexsus FAQ

Clear answers for how Connexsus works, what public provider pages cover, and how managed MCP setup differs from one-off client configuration.

What is Connexsus?

Connexsus is a managed MCP gateway that lets teams connect providers once and reuse them across coding and operational AI clients through one project-scoped MCP endpoint.

What does managed MCP gateway mean?

It means Connexsus handles provider connection flows, credential storage, project assignment, and tool exposure so teams do not have to wire every MCP client manually.

Which providers are available publicly today?

The public SEO surface focuses on the first enriched provider wave: GitHub, Supabase, Notion, Linear, Sentry, Slack, Figma, Render, Vercel, Brave, and Context7.

Does public search content expose private project data?

No. Public pages use published catalog metadata and curated product content only. Project-specific state stays behind authenticated app surfaces.

How does GEO differ from SEO here?

SEO improves search discovery and click-through on public pages. GEO ensures those pages are also machine-readable and useful for generative search systems through structured data, clear entities, and crawlable documentation.

Why not publish every provider page immediately?

Because thin templated pages are poor for both SEO and GEO. Connexsus should only index providers with real, human-reviewed content and clear user intent.