# StoreRocket Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## StoreRocket

Manage store locations and store-locator maps for your business.

- Record: https://musedirectory.ai/connector/storerocket
- Category: Shopping & Commerce
- Developer: usefulapi (https://usefulapi.io/storerocket/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 267ms, checked 2026-10-29T23:01:12Z
- Endpoint: https://storerocket.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-29T23:01:12Z)
- Source: Found in the official MCP Registry (io.usefulapi/storerocket) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Fstorerocket

Connect to StoreRocket store-locator projects. Read, create and update store locations with addresses, hours, phone numbers and custom fields. Muse can help you add new locations, update store information, and search your store network.

Example request: "Add a new store location to my store locator with the address, phone number and opening hours."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use StoreRocket to help me. It is a free service with an MCP server at https://storerocket.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- storerocket_get_user: The StoreRocket user the API token belongs to: id, name, email and company. GET /user.
- storerocket_list_projects: List the StoreRocket projects (store locators) the token's user belongs to: public id, name, number of locations, status and plan. Use the id as project_id in every location tool. Location tools need a project on the Business plan (API access). GET /projects.
- storerocket_list_locations: List the locations of a project (name, address, city, coordinates, phone, visibility, location type, marker, cover image), 25 per page by default, with optional filters on name, address, city, state, country and postal code and optional hours/filters/custom fields/calls to action
- storerocket_get_location: One location by id, optionally with its opening hours, search filters, custom fields and calls to action. Needs the location:read permission. GET /projects/{project_id}/locations/{location_id}.
- storerocket_create_location: WRITE: add a location to a project's store locator. name and city are required; supply lat and lng for a precise pin (otherwise StoreRocket geocodes the address, which can be off). It appears on the live locator immediately unless visible is false, so set visible=false for a comi
- storerocket_update_location: WRITE: change selected fields of one location with a partial update (PATCH): only the fields you send change, everything else is kept. The change shows on the live locator at once. Use null to clear phone, email, url, socials or cover; hours accepts single days (hours:{mon:'09:00

Screening checks:
- MCP handshake: pass (Answered in 267ms)
- Domain against threat feeds (Cloudflare security DNS): pass (storerocket.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (6 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)