Read StoreRocket projects and store-locator locations; create and update locations. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"storerocket": {
"url": "https://storerocket.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"storerocket": {
"type": "http",
"url": "https://storerocket.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your StoreRocket API token.
Create it at storerocket.io → API Tokens (storerocket.io/app/api-tokens). Choose only the permissions you want the AI to have: location:read to look things up, location:update to edit, location:create to add; leave location:delete off. The API needs a project on the Business plan. Your token is used only to call the StoreRocket API on your behalf; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your StoreRocket API token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the StoreRocket connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
storerocket_get_user | read | Get user The StoreRocket user the API token belongs to: id, name, email and company. GET /user. |
storerocket_list_projects | read | 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 | read | 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. Needs the location:read permission. GET /projects/{project_id}/locations. |
storerocket_get_location | read | 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 | 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 coming-soon or draft location. Opening hours: omit, or give all seven days. Creating twice makes two locations, so check storerocket_list_locations before retrying after an error. Needs the location:create permission. POST /projects/{project_id}/locations. |
storerocket_update_location | write | 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-17:00'}), null for a day clears it, hours:null removes the whole schedule; fields and calls_to_action merge by name (a null value removes that entry); filters REPLACES the list ([] clears it). To take a location off the locator without deleting it, set visible=false. An invalid value saves nothing. Needs the location:update permission. PATCH /projects/{project_id}/locations/{location_id}. |
storerocket_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
storerocket_request_feature | Request a missing feature Tell usefulapi that the user needs something the StoreRocket tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
storerocket_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on StoreRocket (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $19/month or $190/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
storerocket_cancel_subscription | Cancel the Pro subscription Cancel the caller's StoreRocket Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run storerocket_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this StoreRocket server only. Subscribe with storerocket_upgrade (it returns a Stripe Checkout link). Cancel any time with storerocket_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running storerocket_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by StoreRocket. The server calls the StoreRocket API with your own StoreRocket access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your StoreRocket API token. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your StoreRocket API token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the StoreRocket API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in StoreRocket.
Yes, if you approve it. 2 of the 6 StoreRocket tools can create or change data. The other 4 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this StoreRocket server only. Cancel any time: Pro then runs to the end of the paid period. Run storerocket_usage_status to see how many calls you used.
Ask the AI to run storerocket_upgrade: it returns a Stripe Checkout link. To cancel, run storerocket_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with storerocket_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.