stackgate.ai
Log in Create profile
All integrations

Chrome Web Store

Connect the Chrome Web Store to Claude, ChatGPT or Cursor via MCP. Check review status, read ratings, reviews and install metrics, and publish extension updates.

OAuth 9 tools

Example questions

Try asking your AI client

  • Is my latest Chrome extension submission still pending review?

  • What is my extension's average rating, and what do the newest one-star reviews complain about?

  • How many installs and daily active users did my extension get last month, by country?

  • Upload the zip I put in Temp Storage, but do not submit it for review until I confirm.

  • Raise the staged rollout of my extension from 10 to 50 percent.

Overview

Manage your Chrome extensions in the Chrome Web Store from AI clients. This Chrome Web Store MCP integration lets developers check review status, read ratings, reviews and install metrics, and ship new versions without opening the Developer Dashboard for every release.

Common use cases

  • Release status - see whether the latest submission is pending review, approved, staged, or published, and at which rollout percentage.
  • User feedback - read the rating summary and recent reviews, filtered by star rating.
  • Growth metrics - query daily installs, uninstalls, active users, impressions, and page views, sliced by country, OS, version, or UTM source.
  • Publishing - upload a new extension zip, submit it for review, raise a staged rollout, cancel a submission, or roll back to a previous package.
  • Private gateway - combine the Chrome Web Store with GitHub, Temp Storage, and other integrations in one release workflow.

Prerequisites

  • A Google account that is a member of a Chrome Web Store publisher with at least one published item
  • Your publisher ID from the Chrome Web Store Developer Dashboard (Account page)
  • A stackgate.ai account

Getting credentials

  1. Open Integrations → Chrome Web Store.
  2. Click Activate, then Connect with Google OAuth.
  3. Choose Standard access (Read and Write) or pick specific tools. Read-only access cannot upload or publish.
  4. Grant Chrome Web Store access on the Google consent screen (chromewebstore.readonly for Read, chromewebstore for Write).
  5. On the Connection tab, paste your publisher ID and click Save publisher ID. Tools use it unless the AI client passes a different publisher_id.

The Chrome Web Store API has no endpoint for listing your items, so keep the 32-character item IDs of your extensions handy. They appear in the Developer Dashboard and in each store URL.

Using with AI clients

  • Dedicated endpoint: POST /mcp/chrome-web-store
  • Private gateway: chrome-web-store__* tools

Available tools:

  • get_item_status, get_rating_summary, list_reviews, query_metrics (Read)
  • upload_package, publish_item, cancel_submission, set_deploy_percentage, rollback_item (Write)

To ship an update, upload the extension zip to Temp Storage first, pass its file_id to upload_package, wait until get_item_status shows the upload has finished, then call publish_item.

Example prompts:

  • What is the review status of my extension abcdefghijklmnopabcdefghijklmnop?
  • Show the newest one-star reviews and summarize the complaints.
  • How many installs and daily active users did my extension have in October, by country?
  • Upload the zip I just put in Temp Storage and submit it for review with a 10 percent rollout.

Troubleshooting

  • "No Chrome Web Store publisher ID is set" - save your publisher ID on the Connection tab, or ask the AI client to pass publisher_id.
  • Item not found / 404 - check the item ID and that it belongs to the saved publisher.
  • Permission denied / 403 - confirm the Google account is a member of the publisher, and reconnect with Write access if you want to upload or publish.
  • Upload stays in progress - large packages are processed asynchronously. Poll get_item_status before publishing.
  • Publish rejected - the API reports validation errors as-is. Fix the manifest or listing in the Developer Dashboard and retry. skip_review only works for items that qualify.
  • Deploy percentage rejected - rollouts can only increase. Use rollback_item to revert a release instead.
  • Auth errors - reconnect Chrome Web Store from My Integrations to refresh tokens.

Available tools

  • get_item_status

    Get the status of a Chrome Web Store item: published and submitted revisions, review state, upload state, and deploy percentage.

  • get_rating_summary

    Get the average rating and rating counts for a Chrome Web Store item.

  • list_reviews

    List user reviews for a Chrome Web Store item, optionally filtered by star rating.

  • query_metrics

    Query daily install, uninstall, user, impression, and page-view metrics for a Chrome Web Store item, optionally sliced by one dimension.

  • upload_package

    Upload a new extension package (zip) to an existing Chrome Web Store item. Put the zip in Temp Storage first and pass its file_id. Then poll get_item_status until the upload finishes before publishing.

  • publish_item

    Submit the latest uploaded package of a Chrome Web Store item for review and publishing. Only call when the user explicitly asks to publish.

  • cancel_submission

    Cancel the pending review submission of a Chrome Web Store item.

  • set_deploy_percentage

    Raise the rollout percentage of the published revision of a Chrome Web Store item. The percentage can only go up.

  • rollback_item

    Roll a Chrome Web Store item back to a previously published package and publish it to all users under a new, higher version number. Use validate_only for a dry run.

MCP endpoint: https://stackgate.ai/mcp/chrome-web-store (HTTP) or via the private gateway.

Create account Documentation