Connect Cursor

Cursor reads an mcp.json. Point it at your store endpoint with a static key and the tools show up in the composer.

Static keyRead-onlyFree

Steps

Four minutes, start to finish

Generate an MCP key from your store's settings → connectors.
Add the server to ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one.
Reopen Cursor's MCP panel and check the server is listed as connected.
Ask about the store — the model calls the tools directly, no glue code.

Config

What to paste

Replace <STORE_ID> with your store id. The dashboard shows the same URL fully resolved, next to the key.

Cursorjson

Static key

{
  "mcpServers": {
    "boostecom": {
      "url": "https://www.boostecom.app/api/mcp/v1/<STORE_ID>",
      "headers": {
        "Authorization": "Bearer bst_mcp_<YOUR_KEY>"
      }
    }
  }
}

What bites

A static key never passed a consent screen, so it IS the grant: it reaches every tool the Custom App allows. Use OAuth where a human can approve, and keep static keys for CI and headless runs.
The endpoint is per store, so two stores are two entries in mcp.json — give them distinct names or the second silently replaces the first.

Cursor's own documentation