{"title":"Build on StoreConnect using AI agents","slug":"use-ai-agents-with-storeconnect","url":"https://support.storeconnect.com/articles/use-ai-agents-with-storeconnect","url_markdown":"https://support.storeconnect.com/articles/use-ai-agents-with-storeconnect.md","subtitle":null,"summary":"How to build, design, and configure your store with external AI agents and coding assistants. Connect your store\u0026#39;s MCP server and the StoreConnect skills toolkit so an agent can act in your Salesforce org, see what an agent can do, and learn how to work safely. Use this when setting up or building your store with AI assistance.","type":"AI","video_url":"","keywords":"ai agent, ai agents, mcp, model context protocol, coding assistant, llms.txt, markdown docs, claude, ai integration, agent, machine-readable docs, api","last_modified":"2026-08-21T07:12:35+0000","body_markdown":"Every StoreConnect store can be built, designed, and configured by AI, using the StoreConnect Model Context Protocol (MCP).\n\nThe MCP, together with StoreConnect's downloadable AI skills toolkit, acts as a translation layer between an agent and your store. Once it is set up, you describe what you want in plain language, and the agent proposes the changes for you to approve before they go live on your storefront.\n\nThere's no tool lock-in. You can connect a preferred agent, such as Claude, Codex, Gemini, GitHub Copilot, or Cursor, or install the skills on their own as a portable package from the [StoreConnect AI repository](https://github.com/GetStoreConnect/ai).\n\n## How it works\n\nThree things work together when an agent builds in your store:\n\n- The MCP server — the authorized gateway between the agent and your store. It is scoped to a single store, and an agent works only within the permissions of the StoreConnect user it signs in as.\n- The AI skills toolkit — a curated GitHub repository that teaches an agent how to work with StoreConnect, including how to find information and how to make changes.\n- Documentation — StoreConnect's docs provide the step-by-step recipes an agent follows to perform an action.\n\nBecause the MCP server belongs to your store, the agent you connect only ever works in that store. To get connected, see [Connect an AI agent to your store](connect-an-ai-agent-to-your-store).\n\n## What agents can do\n\nAn agent can do almost anything in StoreConnect, given the right access. So far we've focused on the areas that are specific to StoreConnect rather than Salesforce — store design and themes, POS layouts, and working with Liquid and custom objects — because these are the hardest to learn and the most valuable to speed up.\n\nYou prompt for changes in plain language, without needing to know the technical detail behind StoreConnect. Some scenarios we've tested:\n\n- Build a complete storefront from an existing website — for example, recreating a Shopify design in StoreConnect.\n- Create and update page content, sections, and media.\n- Set up StoreConnect for the first time: install it, add a sync user, and complete the basic configuration.\n- Bulk migrate media and other data, pre-mapped to StoreConnect custom objects.\n- Launch a sale: update page banners and promote discount codes.\n\n## Working safely with an agent\n\nAn AI agent acts with real effect in your store, so treat it as you would any tool with write access to your data. The following guardrails are in place:\n\n- Permissions — an agent signs in as a StoreConnect user and can only do what that user is allowed to do. Grant it only the access it needs for the task.\n- Approval — by default every change is staged for you to review, and nothing reaches your store until you approve it, much like changes work now in the website builder. Permissions can be widened to let an agent publish directly, so grant that only where you intend it.\n- Store scope — an agent only ever works in the one store you connect it to. Connecting a different store means using that store's own MCP server.\n\n:::warning\nTry agent-driven changes in a test store or Salesforce sandbox before you run them against your live store. See [Set up your test store](test-store) and [Move data from sandbox to production](migrating-from-sandbox).\n:::\n\n## Next steps\n\nWhen you are ready to connect an agent, work through [Connect an AI agent to your store](connect-an-ai-agent-to-your-store), then [Install the StoreConnect AI skills](install-ai-skills).\n\nFor jobs with enough moving parts that the order of operations matters, see [Agent recipes](agent-recipes)."}