Connect Store MCP to Grok.
Checked against official docs on .
Ask Grok about your stores with an authorized connection to the underlying operations. Use its custom MCP connector rather than assuming Store MCP already appears in a connector catalog.
Connect Store MCP to Grok
- Connect an available sales channel in Store MCP first.
- On Grok web, open grok.com/connectors.
- Choose New Connector, then Custom. Enter https://store-mcp.com/mcp as the server URL.
- Complete the authentication Grok requests. In the Store MCP browser consent flow, select the intended stores and View only permissions. Business or Enterprise administrators may need to provision the connector first.
- Use the connector in a Grok conversation and ask it to list your stores. Verify an actual tool response before relying on the connection.
Copy a setup request
Help me add Store MCP in Grok using New Connector → Custom and https://store-mcp.com/mcp. I will complete browser authorization myself. Once connected, list my authorized stores without changing anything.Adding the connector and authorizing it are separate from sending this prompt. If authentication is not offered or fails, keep the connection untrusted and use support rather than disabling authentication.
Authorize in your browser. Never paste store passwords or tokens into chat.
Verify your connection
Before you start
You need an available connected store, an eligible Grok account and permission to add a remote MCP connection. Start with View only access to one selected store.
You’re done when…
stores.list returns only your authorized stores. A known listing matches its title and SKU in the provider dashboard. Connect AI shows the grant and Activity records the read.
If the first read fails
Do not enable write access to fix a failed read. Check the account, provider connection and selected store scope. A saved URL is not sufficient verification. Troubleshoot the connection.
A new live Store MCP authentication test in this client has not been performed. Published setup references do not imply directory approval.
Try your first requests in Grok
Name the store and review proposed changes. Examples do not create automatic workflows.
Use Store MCP to list the stores Grok can access. Do not make changes.Show orders needing attention, grouped by store, and explain any coverage limits.Review this listing and suggest a clearer title. Wait before updating it.Start with one store
Free to start with View only access. Compare plans and limits.
Questions before you connect?
Do I need an xAI API key?
This guide uses the Grok application’s custom connector flow, not the separate xAI API remote-tools integration. Do not paste an xAI key or marketplace credentials into a chat to follow these steps.
Do I need to run a server or tunnel?
No. Store MCP supplies a hosted HTTPS endpoint. The local-server tunneling instructions in Grok’s documentation are not needed for this URL.
Is Grok production compatibility certified?
No certification or catalog approval is claimed. The official custom connector flow has been checked, but a successful Store MCP connection still needs to be verified in your Grok account.
What should I check after connecting?
Ask the AI to list your stores, confirm their names and read one known listing or order. A saved URL is not proof of a working connection. Connect AI and Activity in Store MCP show grants and recorded tool use.
Why can it read a store but not make a change?
The Free plan is read-only for marketplace operations. Changes also need write permission, access to that store and a supported provider operation. Approval alone does not grant missing permissions.
Official references and setup availability
Documentation checked 2026-09-21. Menu labels and account eligibility can change. References do not imply a marketplace listing, endorsement or completed production acceptance.
Put your store data to work.
Start with the access you choose.