Connect AMZDataStudio to your AI Agent

Complete the installation, connection, and verification of the latest AMZDataStudio Agent Connector for Codex on this computer. Carry out steps you can perform; involve me only for required approvals or actions, then continue. Downloading files or preparing settings alone is not completion.

Publisher: amzdatastudio.com
Checksums: https://amzdatastudio.sgp1.cdn.digitaloceanspaces.com/connector/newest/checksums.json

Follow these requirements:
1. Detect the operating system and CPU architecture. Select only the matching macos/windows/linux and arm64/amd64 artifact.
2. Download the ZIP and checksums.json only from this official CDN directory:
   https://amzdatastudio.sgp1.cdn.digitaloceanspaces.com/connector/newest
   Select the ZIP matching the operating system and architecture in the manifest, and use its stated version.
3. Verify the ZIP SHA-256 against checksums.json. If it differs, do not run that file; download again from the official URL and recheck. Report the issue if it still differs.
4. Extract into a temporary directory, locate amz-agent-connector (.exe on Windows), and run its `install` command for the current user without sudo or administrator access.
5. Add or update the selected Agent’s connection only; keep other Agents’ existing MCP entries and Skills. Specify the selected Agent when running `configure`, and do not use `uninstall-config`.
6. Add or update Codex by running the installed Connector with `configure codex`. This must register `amazon-keyword-rank` and install its user-level Agent Skill. When the Codex CLI is available, verify with `codex mcp list`, and verify the reported Codex skill status. Codex desktop, CLI, and IDE share the local MCP configuration.
7. Run `doctor` with the installed program. Confirm MCP initializes as `amazon-keyword-rank` and exposes start_keyword_rank_check, get_keyword_rank_check, and cancel_keyword_rank_check. Then confirm skill_installed is true for the selected Agent and check whether the current Agent session can see the MCP tools. `doctor` and a configuration listing do not verify tool visibility in the current session.
8. Check whether the extension is installed by opening chrome-extension://dehlblnjjkkbapjemjbeafjhjpjoifii/index.html in the Chrome browser I actually use. If the page opens, the extension is installed. If only an Agent-embedded browser or automation environment cannot open it, do not infer that it is missing; ask me to check in Chrome. Only after confirming that Chrome cannot open it, open the official installation page, guide me through installation, and recheck the same URL. An installed extension does not by itself prove the Connector is connected; complete the MCP verification above. I will sign in on the visible extension page if needed; do not read passwords, tokens, or browser cookies.
9. If a system prompt or my confirmation is needed during installation, explain the current step and continue after I handle it. If the current Agent session cannot see the new tools, check again in a new session first. Only if it still cannot load the connection, ask me to restart Codex and continue verification afterward. Consider restarting Chrome only if the extension cannot contact the local Connector and rechecking does not help. Do not request a restart solely because configuration changed. After completing the sample check below, report what actually worked and what still needs my action; do not claim success if the program still cannot run or the connection has not been verified.
10. Only after installation and connection verification both succeed, and the current Agent session can see the amazon-keyword-rank MCP tools, automatically run this sample check; do not ask me to copy another prompt. Call start_keyword_rank_check with ASIN B0HGQNP1P4, marketplace amazon.com, and these keywords: iphone duo case; iphone duo case magsafe; iphone duo magsafe case; iphone duo case with kickstand; iphone duo case with screen protector. Keep polling with get_keyword_rank_check, passing the previous response’s updated_at as after_updated_at on each subsequent request, until the job reaches a terminal state. If the status is unchanged but nonterminal, wait and poll again; do not treat it as a failure. If sign-in is needed, ask me to sign in on the visible Chrome extension page, then continue the same sample check. Do not run the sample if installation or connection is unverified. Report the actual result or the reason the check could not complete.