> For the complete documentation index, see [llms.txt](https://docs.maker.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maker.co/features/connectors.md). # Connectors Use Connectors to link Maker to your other tools so you can pull in content, data, and media without leaving the editor. *** {% embed url="" %} #### Access connectors 1. In the editor, click the **+** button in the prompt box. 2. Choose **connectors** from the menu. 3. From here you can enable and disable connector or click on Manage connectors 4. Selecting Manage connectors opens **Settings → Connectors**. Alternatively, you can also go to **Settings → Connectors** directly. *** #### Add or manage a connector On the **Connectors** tab you’ll see available integrations, such as: * **Atlassian** – connect Jira & Confluence content * **Cloudinary** – manage and deliver your images & videos * **Notion** – connect your Notion workspace * **Add custom connector** – connect other data or services To add one: 1. Click the **+** on the connector card. 2. Follow the prompts to sign in and authorize access. Once connected, the connector will be available inside Maker wherever that integration is supported (for example, when inserting content or media into your projects). Maker offers several ways to connect your store's product data, either through **MCP connectors** (for AI-assisted chat and search) or **native integrations** (built directly into Maker for use inside projects). ### MCP Connectors MCP (Model Context Protocol) connectors let you chat with and query external data sources in natural language. * Shopify Storefront MCP (*Enterprise plan) :* Chat with your own Shopify store. Search your products and ask natural-language questions about your own catalog — scoped only to your store's data. * Shopify Global Catalog MCP ( All plans): Chat with Shopify's global catalog. Search products and ask questions across all Shopify stores, not just your own — useful for competitive research or cross-store product discovery. * Atlassian ( All plans): Access to Jira & Confluence, for pulling tickets and documentation in as context. * Cloudinary (All plans) : Manage, transform, and deliver images and videos — for teams whose media library lives in Cloudinary rather than Maker's own asset storage. * Figma (All plans): Pulls in Figma design context so Maker can generate code and content that matches an existing design file. * Notion (All plans): Connects your Notion workspace to search, update, and power workflows across tools — for example, pulling in brand docs or content briefs. ### Native Integrations Native integrations are built directly into Maker (not MCP-based) and connect data sources for use in projects, reporting, and workflows. * Your Store Products (*Enterprise plan):* A platform-agnostic integration that lets Maker search and use your store's product data inside projects. Works with any ecommerce platform, not Shopify-specific. * Shopify Storefront API (*Enterprise plan):* Pulls live product data directly from your Shopify store into your Maker projects — real-time inventory and pricing, for building projects rather than conversational search. * Google Analytics — Analytics (*Max plan):* Powers AI-driven insights by reading traffic and conversion data from your GA4 property. Broader, general-purpose analytics and performance reporting. * Google Analytics — Variants (*Max plan):* Tracks A/B experiment events. Sends variant impression and conversion events to GA4 — built specifically for testing different versions of a page or email. * Google Ads (*Max plan):* Connects Google Ads to track ad performance and conversions for your organization. * Meta Ads (*Max plan):* Connects Meta Ads to access ad accounts and product catalogs for your organization (Facebook/Instagram equivalent of Google Ads). * Maker Insights (*Max plan):* AI-powered analytics and insights generated from your own Maker data, as opposed to an external analytics platform like GA4. ### Quick Reference | Connector | Type | Plan | Scope | | ---------------------------- | ------ | ---------- | ------------------------------------ | | Shopify Storefront MCP | MCP | Enterprise | Your store only | | Shopify Global Catalog MCP | MCP | All | All Shopify stores | | Your Store Products | Native | Enterprise | Any ecommerce platform | | Shopify Storefront API | Native | Enterprise | Your store only (live data feed) | | Google Analytics — Analytics | Native | Max | General traffic/conversion analytics | | Google Analytics — Variants | Native | Max | A/B experiment tracking | | Google Ads | Native | Max | Ad performance | | Meta Ads | Native | Max | Ad performance | | Maker Insights | Native | Max | Maker-native analytics | | Atlassian | MCP | All | Jira & Confluence | | Cloudinary | MCP | All | Image/video management | | Figma | MCP | All | Design context | | Notion | MCP | All | Workspace docs/workflows | ### Add Custom MCP For any MCP server not listed as a pre-built connector, use **Add custom MCP** to connect it manually. You'll need: * **Name** — a label to identify the connector in Maker * **Remote MCP server URL** — the endpoint of the MCP server you're connecting to * **Advanced settings** (optional) — additional configuration such as authentication headers This is the option to use when connecting a private, internal, or third-party MCP server that isn't part of Maker's built-in list (e.g., a custom-built tool or a vendor's MCP endpoint not yet natively supported). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.maker.co/features/connectors.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.