Manage Seal Subscriptions on Shopify: subscriptions, billing attempts, items, discounts, rules. 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": {
"seal-subscriptions": {
"url": "https://seal-subscriptions.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"seal-subscriptions": {
"type": "http",
"url": "https://seal-subscriptions.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 Seal Subscriptions API token.
Find it in your Shopify admin → Apps → Seal Subscriptions → Settings → General Settings → API. Use the API token, not the API secret. The token belongs to one shop and can manage its subscriptions; your token is used only to call the Seal Subscriptions API on your behalf and 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 Seal Subscriptions 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 Seal Subscriptions connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
sealsubscriptions_list_subscriptions | read | List subscriptions List or search the shop's subscriptions (50 per page): status, customer, interval, total value, shipping address and card brand/last digits. Search by customer email, first or last name; filter by status; optionally include the items and the billing attempts of each. GET /subscriptions. |
sealsubscriptions_list_subscriptions_by_billing_date | read | List subscriptions by billing date Subscriptions that have at least one billing attempt scheduled between two UTC date-times: the way to see what will be charged tomorrow or this week. Each subscription carries a cursor; pass the last one's cursor as `cursor` to get the next page. GET /subscriptions-by-billing-date. |
sealsubscriptions_get_subscription | read | Get subscription One subscription with everything Seal knows: customer, shipping and billing address, status, intervals, delivery method, items with discounts, billing attempts (with status and error messages), fulfillment orders, invoices, tags and the activity log. Private customer links are removed. GET /subscription?id=. |
sealsubscriptions_list_subscription_rules | read | List subscription rules List the subscription rules (plans) of the shop: name, payment type, the products and variants they apply to and their selling plans. GET /subscription-rules. |
sealsubscriptions_get_subscription_rule | read | Get subscription rule One subscription rule by id, with its products, variants and selling plans. GET /subscription-rule?id=. |
sealsubscriptions_list_webhooks | read | List webhooks List the webhooks registered for this shop through the API (topic and address). GET /webhooks. |
sealsubscriptions_pause_subscription | write | Pause subscription WRITE: Pause an active subscription: no further charges or shipments until it is resumed. Undo with sealsubscriptions_resume_subscription. PUT /subscription action=pause. |
sealsubscriptions_resume_subscription | write | Resume subscription WRITE: Resume a paused subscription so charges and shipments continue on the schedule. PUT /subscription action=resume. |
sealsubscriptions_reactivate_subscription | write | Reactivate subscription WRITE: Reactivate a cancelled subscription (the effect is the same as resume; use this for cancelled ones). Charges restart on the schedule, so the customer may be billed. PUT /subscription action=reactivate. |
sealsubscriptions_cancel_customer_subscription | write | Cancel subscription WRITE: Cancel a subscription now: all future charges and shipments stop and the customer may get Seal's cancellation email. It can be brought back with sealsubscriptions_reactivate_subscription. For a later cancellation use sealsubscriptions_schedule_cancellation. PUT /subscription action=cancel. |
sealsubscriptions_schedule_cancellation | write | Schedule subscription cancellation WRITE: Schedule the cancellation of a subscription for a future date and time (it stays active until then). PUT /subscription-schedule-cancellation. |
sealsubscriptions_add_items | write | Add items to subscription WRITE: Add products to a subscription. Prices are in the subscription's currency and change what the customer pays on the next charge. An item with one_time=true is removed after the next renewal. PUT /subscription action=add_items. |
sealsubscriptions_edit_items | write | Edit subscription items WRITE: Change existing items of a subscription: variant, quantity (> 0), price (>= 0), SKU, one-time flag, properties. Changes what the customer pays on the next charge. PUT /subscription action=edit_items. |
sealsubscriptions_remove_items | write | Remove items from subscription WRITE: Remove items from a subscription by item id. The customer stops receiving and paying for them. PUT /subscription action=remove_items. |
sealsubscriptions_edit_subscription | write | Edit subscription WRITE: Edit a subscription's schedule and details: delivery and billing interval (a billing interval longer than the delivery interval makes it prepaid), min/max number of payments, note attributes (an empty list removes them), delivery method and price, and the shipping address. Only the fields you pass change. To change items use the item tools. PUT /subscription action=edit. |
sealsubscriptions_reschedule_billing_attempt | write | Reschedule billing attempt WRITE: Move a billing attempt that has not been processed yet to another date and time. With reset_schedule=true the later attempts are rebuilt from the new date. PUT /subscription-billing-attempt action=reschedule. |
sealsubscriptions_skip_billing_attempt | write | Skip billing attempt WRITE: Skip one upcoming billing attempt so the customer is not charged for that cycle. Undo with sealsubscriptions_unskip_billing_attempt. PUT /subscription-billing-attempt action=skip. |
sealsubscriptions_unskip_billing_attempt | write | Unskip billing attempt WRITE: Bring back a skipped billing attempt, so it is charged on its date again. PUT /subscription-billing-attempt action=unskip. |
sealsubscriptions_delete_billing_attempt | write | Delete billing attempt WRITE: Delete a billing attempt that has not been processed. Seal keeps 65 days of attempts scheduled, so a deleted one is recreated within hours unless the schedule is moved first (see sealsubscriptions_reschedule_billing_attempt). DELETE /subscription-billing-attempt. |
sealsubscriptions_reschedule_fulfillment_order | write | Reschedule fulfillment order WRITE: Move a fulfillment order of a prepaid subscription to another date and time. PUT /subscription-fulfillment-order action=reschedule. |
sealsubscriptions_create_charge_now | write | Charge subscription now WRITE: CHARGES THE CUSTOMER'S PAYMENT METHOD IMMEDIATELY for the next billing attempt of the subscription and creates a Shopify order; it does not wait for the scheduled date. Only call it when the user clearly asked for an immediate charge. With reset_schedule=true the later attempts are rebuilt from today. PUT /subscription-create-charge-now. |
sealsubscriptions_process_charge | write | Process a specific charge WRITE: CHARGES THE CUSTOMER'S PAYMENT METHOD NOW for one specific billing attempt (for example a failed or upcoming one) and creates a Shopify order. Only call it when the user clearly asked for that charge. PUT /subscription-process-charge. |
sealsubscriptions_apply_discount_code | write | Apply discount code WRITE: Apply a Shopify discount code to an auto-charging subscription (not to recurring-invoice subscriptions); it lowers what the customer pays on the next charges. PUT /subscription-discount-code action=apply. |
sealsubscriptions_remove_discount_code | write | Remove discount code WRITE: Remove a discount code from a subscription. Use the discount code id from the subscription's items[].discount_codes[].id (a uuid), not the code text. DELETE /subscription-discount-code. |
sealsubscriptions_send_payment_method_update_email | write | Email customer to update payment method WRITE: SENDS AN EMAIL TO THE CUSTOMER of the subscription with a link to update their payment method (for example after failed charges). Only call it when the user clearly asked to contact the customer. PUT /subscription action=send_payment_method_update_email. |
sealsubscriptions_edit_subscription_rule | write | Edit subscription rule WRITE: Edit a subscription rule: its name, the plan selector label (`options`, e.g. "Deliver every") and the products it applies to. product_variants REPLACES all products and variants linked to the rule: to add some without removing the others use sealsubscriptions_append_rule_product_variants. PUT /subscription-rule. |
sealsubscriptions_append_rule_product_variants | write | Add products to subscription rule WRITE: Add products or variants to a subscription rule without touching the ones already linked. PUT /subscription-rule/append-product-variants. |
sealsubscriptions_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. | |
sealsubscriptions_request_feature | Request a missing feature Tell usefulapi that the user needs something the Seal Subscriptions 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. | |
sealsubscriptions_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Seal Subscriptions (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. 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. | |
sealsubscriptions_cancel_subscription | Cancel the Pro subscription Cancel the caller's Seal Subscriptions 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 sealsubscriptions_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 Seal Subscriptions server only. Subscribe with sealsubscriptions_upgrade (it returns a Stripe Checkout link). Cancel any time with sealsubscriptions_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running sealsubscriptions_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 Seal Subscriptions. The server calls the Seal Subscriptions API with your own Seal Subscriptions 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 Seal Subscriptions 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 Seal Subscriptions 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 Seal Subscriptions 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 Seal Subscriptions.
Yes, if you approve it. 21 of the 27 Seal Subscriptions tools can create or change data. The other 6 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 Seal Subscriptions server only. Cancel any time: Pro then runs to the end of the paid period. Run sealsubscriptions_usage_status to see how many calls you used.
Ask the AI to run sealsubscriptions_upgrade: it returns a Stripe Checkout link. To cancel, run sealsubscriptions_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 sealsubscriptions_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.