Storerocket
StoreRocket is a store locator software platform that enables businesses to add customizable, interactive location finders to their websites. It provides location management, real-time opening hours, search filters, custom fields, lead collection, analytics, and a REST API for seamless integration with platforms like WordPress, Shopify, Webflow, and more.
Verdict
Common use cases
- Verify API key permissions before campaign launch
- Audit team member access for compliance reviews
- Pull user roster into onboarding documentation
- Confirm authenticated account in troubleshooting sessions
Integration
- Vendor
- Storerocket
- Category
- other
- Auth
- API_KEY
- Tools
- 2
- Composio slug
storerocket
Tools
- Get authenticated user information
Tool to retrieve authenticated user information. use when you need current user details after authentication.
- Get users list
Tool to retrieve a list of all users. use when you need to list users with optional pagination after authentication.
Setup
Setup guide
- 11. In Switchy, navigate to Settings > Integrations and click 'Add MCP Integration'. 2. Select Storerocket from the list. 3. Log into your Storerocket account, go to Settings > API, and generate a new API key (copy it immediately — you won't see it again). 4. Paste the API key into Switchy's connection form and click 'Connect'. 5. Switchy will verify the key by fetching your user profile. 6. Once connected, open any Space and type '@Storerocket get my user info' to confirm the integration works. 7. You'll see your account details returned in the chat — if that succeeds, the MCP is ready to use across all Spaces in your workspace.
What teammates see: by default, memories from Storerocket are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Check My Account
@Storerocket get my user information and show me the account detailsOpen in a Space →
List All Users
@Storerocket retrieve the complete list of users in this accountOpen in a Space →
Verify Connection
@Storerocket fetch my user profile to verify the connection is workingOpen in a Space →
Audit User Access
@Storerocket get the users list and format it as a table with names and rolesOpen in a Space →
Document Team Setup
@Storerocket show me all users in this account so I can document our team structureOpen in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Storerocket show me the current authenticated user's account details and subscription status
The authenticated user is Jane Smith (jane@example.com), account ID 12345. Subscription: Pro plan, active since March 2024, renews April 15, 2025. Account includes 3 team seats with 2 currently occupied. Storage usage: 4.2 GB of 10 GB limit. API rate limit: 1000 requests/hour, currently at 23% usage. Last login: today at 9:14 AM UTC.
This example uses the user-info tool to surface account metadata. Useful for confirming which Storerocket account the MCP is authenticated against before running bulk operations. Requires a valid API key with read permissions on user resources.
@Storerocket list all users in our organization, paginated by 50 per page, and show me the second page
Showing users 51–100 of 237 total. Includes: Mike Chen (mike@example.com, Admin, joined Feb 2024), Sarah Lopez (sarah@example.com, Member, joined Jan 2024), Tom Wu (tom@example.com, Member, joined Dec 2023)… [continues for 50 entries]. Each entry shows email, role, join date, and last-active timestamp. Use page=3 to see the next batch.
Demonstrates pagination for accounts with many users. The MCP returns structured user lists but does not filter by role or activity status — you'll need to ask the AI to parse results if you want 'only admins' or 'inactive for 90 days'. API key must have user-list permissions.
@Storerocket pull the full user list and summarize how many admins versus members we have, plus identify anyone who hasn't logged in since January
Fetched 237 users across 5 pages. Role breakdown: 12 Admins, 225 Members. Inactive since January 2025: 18 users, including alex@example.com (last login Dec 12, 2024), priya@example.com (last login Nov 3, 2024), and 16 others. The AI can generate a CSV export or draft an email to inactive users if needed.
This synthesis example pairs the list-users tool with AI reasoning to answer a question the MCP doesn't answer directly. The MCP provides raw data; the AI aggregates and filters. Expect multiple API calls if your user count exceeds one page — watch rate limits on large accounts.
Use-case deep-dives
When Storerocket MCP works for small app marketing teams
A 3-person mobile app team managing App Store and Play Store listings needs to coordinate screenshot updates and metadata changes across iOS and Android. The Storerocket MCP gives Switchy direct access to user accounts and team member lists, which matters when you're routing approval requests or checking who last touched a listing. The two-tool scope is narrow—this MCP won't pull asset files or edit store metadata directly—so it's best paired with a file-storage MCP for the actual creative handoff. If your workflow is just "check who's on the Storerocket account," this MCP delivers. If you need to automate listing updates or pull analytics, you'll hit the tool ceiling fast. For teams under 10 people doing light coordination around store presence, the auth overhead is worth it.
Using Storerocket MCP to audit account access during onboarding
A startup brings on a freelance ASO consultant and needs to confirm which team members already have Storerocket access before issuing new credentials. The Storerocket MCP's user-list tool lets Switchy pull the current roster in a standup thread without opening the Storerocket dashboard. This is a 2-minute task that happens once per quarter, so the MCP's value is in eliminating context-switching, not automating a high-frequency workflow. The API key auth means you're trusting Switchy with full account read access, which is fine for a 5-person team but worth a second thought if you're managing dozens of contractors. If your onboarding checklist includes "verify tool access" for more than one SaaS product, a dedicated identity provider beats stitching together single-purpose MCPs.
When Storerocket MCP helps customer success look up user details
A SaaS company using Storerocket internally gets a support ticket: "I can't log in to update our Play Store listing." The support agent needs to confirm whether the user exists in Storerocket and surface their account details without pinging the product team. The Storerocket MCP's authenticated-user tool pulls that info into Switchy in one query, cutting a 10-minute Slack thread down to 30 seconds. This scenario assumes your support team already has API key access, which is uncommon outside of technical support orgs. If your support workflow involves more than occasional Storerocket lookups, the two-tool limit makes this MCP a poor fit—you'll want a fuller integration or a direct dashboard login. For teams fielding fewer than 5 Storerocket-related tickets per month, the MCP is overkill.
Frequently asked
What does the Storerocket MCP do in Switchy?
It connects your Storerocket account so AI agents can pull user data and account details without leaving the chat. Useful when your team needs to check who's in your Storerocket workspace or verify account permissions during a conversation. The MCP handles authentication and returns structured user lists or profile info on demand.
Do I need admin access to connect Storerocket MCP?
You need a Storerocket API key, which typically requires account owner or admin permissions to generate. The key authenticates all requests, so whoever connects it in Switchy will grant the AI access to user lists and profile data visible to that API key's permission level.
Can the Storerocket MCP create or edit users?
No. It only reads user information—fetching your authenticated profile or listing all users with pagination. If you need to add users or change permissions, you'll still use Storerocket's web interface or a separate API client. This MCP is read-only for user data retrieval.
Why use this instead of just logging into Storerocket?
Speed and context. When you're mid-conversation in Switchy and need to confirm who has access or check a user's email, the AI fetches it inline without tab-switching. It's faster than opening Storerocket, navigating to settings, and copying data back into chat—especially for repetitive lookups.
Who on my team should connect the Storerocket MCP?
Whoever manages your Storerocket account and has API key access. Since the MCP exposes user lists, connect it only if your team is comfortable with AI agents seeing that data. One connection per workspace is enough—all team members in Switchy can then query Storerocket through the shared MCP.