Connect Cursor
Let Cursor operate your shop while you build: products, orders, customers, and site changes from the editor.
Wire Aly into Cursor so the in-editor agent can manage sites, products, orders, and customers alongside your code.
Cursor speaks MCP natively. Once configured, Cursor's agent can use Aly tools alongside its file-system, terminal, and code tools — letting you ask things like “publish the new product I just edited” and have the agent execute end-to-end.
Prerequisites
- Cursor 0.42 or later (HTTP MCP support).
- An Aly API key with the scopes you want available.
1. Open Cursor settings
Cursor → Settings → Cursor Settings → MCP → Add new MCP server. Or edit ~/.cursor/mcp.json directly.
2. Add the Aly server
{ "mcpServers": { "aly": { "type": "http", "url": "https://aly.store/api/mcp", "headers": { "Authorization": "Bearer aly_..." } } }}After saving, Cursor shows the server with a green dot when the connection is healthy. Open the MCP panel to confirm the tool list loaded.
3. Use it
From any chat in Cursor, you can ask the agent to do work against your Aly workspace:
- “Add a new variant called ‘XL’ to product prod_abc123 priced at $34.”
- “List unfulfilled orders from the last 7 days.”
- “Mark order order_xyz as shipped with carrier USPS, tracking 9400...”
read:orders + write:orders for a fulfillment workflow, not delete:sites.Per-project vs global config
The ~/.cursor/mcp.json path is global. For per-project overrides, place .cursor/mcp.json in your repo root. Cursor merges, with project-level taking precedence.
Troubleshooting
- Server fails to start — Almost always JSON syntax. Cursor surfaces the parse error in the MCP panel.
- Tool calls return 401 — Bad key. Mint a new one from Aly → Settings → API keys.
- 403 on specific tools — Scope mismatch. See Operator vs storefront scopes for which scopes back which tools.
Was this page helpful?