Connect Cursor
Cursor reads an mcp.json. Give it your store's URL, sign in from its MCP settings, and the tools show up in the agent.
OAuth 2.1Static key for CIRead-onlyFree
Four minutes, start to finish
Copy the URL from your store's settings, then Connectors, External LLM Access.
Add the server to ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one. The URL is all it needs.
Open Cursor's MCP settings and log in to the server: your browser opens on the BoostEcom consent screen, where you approve the scopes.
Check the server is listed as connected, then ask about the store: the agent calls the tools directly, no glue code.
What to paste
Replace <STORE_ID> with your store id. The dashboard shows the same URL fully resolved, next to the key.
OAuth 2.1
{
"mcpServers": {
"boostecom": {
"url": "https://www.boostecom.app/api/mcp/v1/<STORE_ID>"
}
}
}What bites
- 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.
- A static key never passed a consent screen, so it opens the relay and nothing else: the 15 read-only Shopify tools, within what you granted the BoostEcom app. The documentation tools, Studio and your store's intelligence record need the OAuth sign-in. On a machine with no browser, add a headers entry with Authorization: Bearer and the key, and keep it in the global ~/.cursor/mcp.json: a project file tends to end up in git.
Next
3 other clients, tested end to end
Ask @Atlas about the store you connect
The same store Cursor reads is one question away here. Ask it in your own words.