Use Store MCP from Cursor.
Checked against official docs on .
Bring authorized store context into Cursor Agent. Review a listing or check inventory alongside your work, without hard-coding marketplace credentials into a repository.
Connect Store MCP to Cursor
- Connect at least one available store in Store MCP.
- Add the JSON entry below to ~/.cursor/mcp.json for your user, or .cursor/mcp.json for this project. Merge it with existing mcpServers entries; do not replace unrelated configuration.
- Open Cursor’s MCP settings and confirm the server is enabled. Complete the browser authentication when Cursor prompts for it.
- On the Store MCP consent screen, select the intended stores and View only access. Never place marketplace tokens in mcp.json.
- Open Agent, ask it to list your stores through Store MCP and review the tool-call result. Keep tool approvals enabled when allowing changes.
Merge into your mcp.json
{
"mcpServers": {
"store": {
"url": "https://store-mcp.com/mcp"
}
}
}This is Cursor’s remote-server format. Preserve your other server entries. A project’s configuration location controls where the connection is available; Store MCP permissions control what it may access.
Authorize in your browser. Never paste store passwords or tokens into chat.
Verify your connection
Before you start
You need an available connected store, an eligible Cursor account and permission to add a remote MCP connection. Start with View only access to one selected store.
You’re done when…
stores.list returns only your authorized stores. A known listing matches its title and SKU in the provider dashboard. Connect AI shows the grant and Activity records the read.
If the first read fails
Do not enable write access to fix a failed read. Check the account, provider connection and selected store scope. A saved URL is not sufficient verification. Troubleshoot the connection.
A new live Store MCP authentication test in this client has not been performed. Published setup references do not imply directory approval.
Try your first requests in Cursor
Name the store and review proposed changes. Examples do not create automatic workflows.
Use Store MCP to list the stores Cursor can access. Do not make changes.Show orders needing attention, grouped by store, and explain any coverage limits.Review this listing and suggest a clearer title. Wait before updating it.Start with one store
Free to start with View only access. Compare plans and limits.
Questions before you connect?
Why is there no command or access token in this JSON?
Store MCP is a hosted remote server, not a local executable. The URL entry uses Cursor’s remote MCP support and the browser authorization flow.
Does committing the URL give teammates my store access?
No. The URL is not a credential. Teammates still need their own authorized access. Do not commit tokens or private authentication headers.
What should I check after connecting?
Ask the AI to list your stores, confirm their names and read one known listing or order. A saved URL is not proof of a working connection. Connect AI and Activity in Store MCP show grants and recorded tool use.
Why can it read a store but not make a change?
The Free plan is read-only for marketplace operations. Changes also need write permission, access to that store and a supported provider operation. Approval alone does not grant missing permissions.
Official references and setup availability
Documentation checked 2026-09-21. Menu labels and account eligibility can change. References do not imply a marketplace listing, endorsement or completed production acceptance.
Put your store data to work.
Start with the access you choose.