Storerocket for AI agents
StoreRocket is store-locator software that lets businesses embed a searchable map of locations on their website, with lead capture and location management tools. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Storerocket.
Confirm the connection is healthy
Ping the API to confirm the connection to a store locator account is working before making other changes.
Look up the connected account
Retrieve the authenticated user tied to the API key, a safe read-only check with no changes made.
Verify access before location edits
Confirm which account is connected before an agent updates a store's hours or details on the map.
2 Storerocket actions, graded by risk.
Every Storerocket action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
2Look things up. Allowed by default.
- storerocket.get_usersGet authenticated user
- storerocket.pingPing API health check
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Storerocket in three steps.
- 01Your users connect StorerocketThey add their Storerocket api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls Storerocket through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('storerocket', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Storerocket connects.
Users add their Storerocket api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Storerocket connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Storerocket from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Storerocket and Arc0, answered.
Can I use Storerocket with Claude, ChatGPT or Cursor?
Yes. Connect Storerocket to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Storerocket actions you allow.
How do users connect Storerocket?
Users add their Storerocket api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Storerocket actions can my agent take?
2 in total: 2 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Storerocket?
Yes. Allow read actions and deny writes in the Storerocket policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Storerocket too?
Yes. The same Storerocket connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Storerocket into your agent.
Your users connect Storerocket once, under your brand. Your agent gets 2 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan