Give Claude Code secure store access.
Checked against official docs on .
Let Claude Code inspect supported store data without writing an integration first. Add the hosted connection once, then use it from the projects where you need it.
Connect Store MCP to Claude Code
- Connect an available store in Store MCP.
- Run the command below in your terminal, outside a Claude Code session. The user scope makes the server available to you across projects.
- Start Claude Code and run /mcp. Select store, then Authenticate, and complete the browser sign-in.
- Choose the stores Claude Code should see and begin with View only access. Keep the client’s tool-permission checks enabled.
- Run claude mcp list to inspect connection status, then ask Claude Code to list your stores and read a known listing.
Run in your terminal
claude mcp add --scope user --transport http store https://store-mcp.com/mcpVerify after browser authorization
claude mcp listInside a Claude Code session, /mcp opens the connection panel. If another server is already named store, choose an unused name rather than removing or replacing it blindly.
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 Claude Code 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.
Claude Code OAuth has recorded staging acceptance. Published setup references do not imply directory approval.
Try your first requests in Claude Code
Name the store and review proposed changes. Examples do not create automatic workflows.
Use Store MCP to list the stores Claude Code 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?
Do I need to edit a configuration file?
No. The add command saves the entry for you. User scope is private to your user across projects; a project-scoped .mcp.json is a separate option for shared configuration.
What if the status says Needs authentication?
That is expected before browser sign-in. Start Claude Code, open /mcp, select the Store MCP server and choose Authenticate. A saved server entry alone is not an authorized store connection.
Has this connection been tested live?
Store MCP’s Claude Code authorization flow was tested on staging. That does not certify every production marketplace action or replace checking the stores and permissions in your own account.
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.