Connect Claude Code

A terminal client wants a config file, not a browser. Generate a static key, declare the server — or commit the config so the whole team gets it.

Static keyRead-onlyFree

Steps

Four minutes, start to finish

In the dashboard, open your store's settings → connectors and generate an MCP key.
Run the command below, or commit the .mcp.json shape under it so the server travels with the repository.
Run /mcp in Claude Code to confirm the server is connected.
Ask for the store: getStoreContext returns plan, currency, markets, locales, themes and your granted scopes in one call.

Config

What to paste

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

Claude Codebash

Static key

claude mcp add --transport http boostecom https://www.boostecom.app/api/mcp/v1/<STORE_ID> \
  --header "Authorization: Bearer bst_mcp_<YOUR_KEY>"

# Or commit it with the project — the key stays in the environment,
# only its name is committed, in .mcp.json:
# {
#   "mcpServers": {
#     "boostecom": {
#       "type": "http",
#       "url": "https://www.boostecom.app/api/mcp/v1/<STORE_ID>",
#       "headers": { "Authorization": "Bearer ${BOOSTECOM_MCP_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.
Committing .mcp.json shares the URL, not the key — that is why the snippet references an environment variable rather than the key itself.

Claude Code's own documentation