Integrations.
OAuth and MCP connectors. Shopify, Google, Meta, Notion inbound. The BoostEcom MCP server as the outbound surface. Token rotation handled, scopes never escalate.
What it is
Integrations is the connectivity layer of BoostEcom. Inbound connectors bring third-party data into the workspace; the outbound MCP server lets external agents reach the BoostEcom platform itself.
How it works
- OAuth flow for Shopify, Google Ads, Meta Ads, Notion.
- Encrypted credential storage, refresh-token rotation, 401 retry handling.
- Each connector exposes structured tool calls. not raw HTTP.
- Outbound BoostEcom MCP server for Cursor, Claude Desktop and custom agents.
- Per-store scope: a connector connected at the org level cascades to stores you choose.
When to use it
Connect Shopify the moment you sign up. Add Google/Meta when you want @Atlas to read ad performance. Add Notion when your brand book lives there. Expose the MCP server when your team uses other AI tools and you want them grounded in BoostEcom.
Limitations
- Inbound connector catalog is curated. bespoke integrations require Custom plans.
- Webhook reliability follows the upstream provider's SLA.
- OAuth token revocation upstream can degrade an integration to read-only.
Connect once, query everywhere.
OAuth in, MCP out, scopes locked down.