← All integrations

Storerocket MCP server

13 operations0 webhooks

Storerocket is a store locator. This plugin reads the token profile and projects, manages locations with opening hours, filters and custom fields through the create, PATCH, PUT and DELETE contracts, and schedules holiday special-hours rules with idempotency keys.

Try Storerocket with your agent

Connect Storerocket, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in Storerocket on my account, then run one read-only example and show me the result.

Runs once, when you ask

Storerocket tools and triggers

Tools are what your agent can do in Storerocket through Corsair's MCP server. Triggers are the Storerocket events a routine can start from.

Locations

  • CreateWrite

    Create a location; name and city are required

    locations.create

  • DeleteDestructive

    Delete a location from a project

    locations.delete

  • GetRead-only

    Read one location and its optional attached information

    locations.get

  • ListRead-only

    List locations with filters, include flags and pagination

    locations.list

  • ReplaceWrite

    Replace a location with the PUT contract; omitted markers and types reset to defaults

    locations.replace

  • UpdateWrite

    Update selected location fields; omissions keep their saved values

    locations.update

Special Hours

  • CreateWrite

    Create a special-hours rule, with an optional idempotency key

    specialHours.create

  • DeleteDestructive

    Delete a special-hours rule; locations fall back to weekly hours

    specialHours.delete

  • GetRead-only

    Read one special-hours rule

    specialHours.get

  • ListRead-only

    List the holiday and special-hours rules of a project

    specialHours.list

  • UpdateWrite

    Change selected fields of a special-hours rule

    specialHours.update

Projects

  • ListRead-only

    List the projects the token can access

    projects.list

Connect Storerocket to Claude, ChatGPT or Cursor

  1. 1

    Connect Storerocket in Corsair

    Add your Storerocket API key once in Corsair. Corsair stores the credential encrypted and makes the Storerocket API calls for your agent, so it never goes into a prompt or a config file. Connect Storerocket

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Storerocket. On a ChatGPT personal plan, connect Storerocket here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Storerocket's read and write operations run right away and its 2 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/storerocket, add the Storerocket plugin, and connect with an API key. Then call methods like corsair.storerocket.api.locations.create() from your app. Corsair keeps each tenant isolated.

Yes. Storerocket requires an API key from your Storerocket account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Storerocket, GitHub, Notion, Stripe, and the rest. Trigger Storerocket from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for storerocket is a store locator. This plugin reads the token profile and projects, manages locations with opening hours, filters and custom fields through the create, PATCH, PUT and DELETE contracts, and schedules holiday special-hours rules with idempotency keys. Common builds include sync jobs, admin tooling, and agents that call Storerocket APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Storerocket API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/storerocket in the open repo. When Storerocket ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Storerocket data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Storerocket data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put Storerocket on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 2 destructive Storerocket operations. You can change a link's mode at hub.corsair.dev/me.