Add Shindig to Cursor with your API key

This page is a setup guide for Shopify merchants who use Cursor with Shindig. Cursor connects the same way as every other assistant, over Streamable HTTP with your Bearer API key. 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).

Follow these steps in Cursor

  1. Copy the MCP URL and API key. The server is Streamable HTTP.
  2. Create mcp.json. Create .cursor/mcp.json in a project, or ~/.cursor/mcp.json for every project. If both files define a server named shindig, confirm in Cursor which one is active.
  3. Set the URL and the Authorization header. Use a url and a headers object. Set Authorization to Bearer, a space, and the API key. Cursor's docs also accept Bearer ${env:SHINDIG_API_KEY} so the key can stay in an environment variable that exists when Cursor starts.
  4. Restart Cursor and ask for a tool. Save the file and restart Cursor. In Customize, confirm the shindig server is on. Ask for a tool by name, such as list_active_events. Cursor asks before it runs a tool unless you change that approval setting.

Use this mcp.json for Shindig

This uses the same fields as Shindig's MCP client example: a url and an Authorization header. Replace YOUR_API_KEY.

{
  "mcpServers": {
    "shindig": {
      "url": "https://shindig.directsales.software/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

To keep the key out of the file, set the header value to Bearer ${env:SHINDIG_API_KEY} and put the key in the environment Cursor starts with. Restart Cursor after you change that variable. Remote servers do not load an envFile. That option is only for local command servers.

These steps follow Cursor's MCP docs checked on 2026-10-21: Model Context Protocol and MCP integrations.

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.