Skip to main content
StoreInspect MCP exposes focused tools over the same store and contact intelligence used by the REST API.
Tool availability can depend on the OAuth scopes granted to the connected client and the current StoreInspect plan.
See MCP quotas and credits for request quota, search-row quota, and contact-credit behavior.

Tools

Search tools return at most 25 records per call. Domain enrichment accepts at most 10 specified domains and returns store and technology data only.

Search filters

Use list_taxonomy to get current filter values before building a search. search_shopify_stores accepts focused store filters:
search_shopify_contacts accepts person and store filters:
Technology filters support:

Scopes

Billing tools

Free users can connect MCP and use the billing tools. Store and contact tools remain unavailable until Stripe confirms an active paid plan. create_subscription_link accepts only StoreInspect plan and cadence values:
The response contains a short-lived Stripe URL. New subscriptions created through MCP use paid Checkout and do not include a free trial. Creating the link does not subscribe, upgrade, cancel, or charge the account. A human must open the URL and confirm in Stripe. After confirmation, call get_billing_status until the webhook-reconciled plan is visible.

Contact reveal safety

The reveal_contacts tool requires explicit confirmation:
If confirm_spend_credits is missing or false, StoreInspect refuses the reveal. Use the ct_... contact IDs returned by search_shopify_contacts. Do not pass a name, role, or store domain to reveal_contacts. Reveal rules:
  • Contact search previews do not return raw email, phone, or LinkedIn URL.
  • Revealing a contact for the first time spends one shared contact credit.
  • Re-revealing a contact already revealed to your account does not spend another credit.
  • Reveals use the same monthly contact-credit pool as the StoreInspect web app and REST API.

Example prompts

For full prompt sequences, see MCP example workflows.

Output shape

MCP responses contain only the result fields needed for the requested operation. StoreInspect keeps request identifiers in internal logs for support and abuse monitoring rather than returning them to the AI client. StoreInspect does not return raw collection records or source-processing metadata through MCP.