Add Shindig to ChatGPT with your API key
This page is for Shopify merchants who use ChatGPT with Shindig. Add the MCP URL and the Bearer key the same way as every other assistant. A custom GPT can also call the REST API with an API key action while custom GPTs remain available. The Free plan does not include API or MCP. Plus is $4.99 per month or $45 per year, and Plus50 is $24.95 per month or $224.55 per year. Each paid plan includes a 14-day free trial. API and MCP need Plus or Plus50.
Every assistant connects the same way
Shindig's MCP endpoint is Streamable HTTP. Send this header on every request. The value is the Company Config API key:
Authorization: Bearer <Company Config API key>In the Shopify admin, open Shindig, then Settings, then Company Config, then API & MCP Access. Company Config shows the URL and the API key. Rotate the key there if it may have been exposed. API and MCP need Plus or Plus50. The same key works for the REST API. REST API quickstart.
When the client connects, it receives Shindig's server instructions plus these resources: guide://shindig/agent, schema://shindig/save-event, and Help Center articles at help://shindig/... (the index is help://shindig/index).
In ChatGPT, add the MCP URL and the Bearer key as a custom connector. Send Authorization: Bearer and the Company Config API key. Do not put the API key in the URL.
A custom GPT can call the REST API with an API key action
OpenAI's actions article says you open the GPT editor, go to Actions, and select Create new action. Authentication can be None, API key, or OAuth. For API key, the choices are Basic, Bearer, or a custom header. Choose Bearer and paste the key from Company Config. The schema is an OpenAPI file in JSON or YAML. You can paste Shindig's contract or import it from the OpenAPI URL. Company Config shows the API base. A GPT can use apps or actions, but not both at the same time. Test the action in Preview. Public GPTs with actions need a privacy policy URL. Actions are not available in Pro mode. Enterprise and Edu workspaces can block actions unless an admin allows the domain.
OpenAI's retirement FAQ says the transition affects all ChatGPT plans. Custom GPTs are scheduled to retire on Dec 11, 2026. For affected Enterprise workspaces with an approved deferral, the retirement date is Feb 11, 2027. Custom actions do not transfer when a GPT is migrated to a plugin. Until then, the action can call the REST API. After retirement, keep using the MCP connection above. Sources: Configuring actions in GPTs and Custom GPT retirement and migration FAQ.
Read another Shindig guide
Claude is a trademark of Anthropic. ChatGPT is a trademark of OpenAI. Grok Bot and Cursor are trademarks of their respective owners. Shindig is not affiliated with, endorsed by, or sponsored by those companies. Works with means you connect your own account.