Quick Start: Claude Cowork for Amazon Workflows

Use Claude Cowork with Kuudo's Amazon MCP servers and Amazon Skills to read Amazon data, run analyses, and produce client-ready files from one conversation.

This page covers how connectors, MCP servers, and Skills fit together inside Cowork; how to connect the Kuudo Amazon servers; how to manage permissions on Team and Enterprise plans; and which Amazon workflows to try first.

Replace the placeholder URLs below with the values from your Kuudo deployment:

{kuudo-amazon-ads-mcp-url}
{kuudo-amazon-selling-partner-mcp-url}
{kuudo-openbridge-mcp-url}

What Cowork does

Claude Cowork is a Claude Desktop workspace for file and task work. It can work with folders you grant it access to, run code in a sandboxed environment, use remote connectors, and apply Skills for repeatable workflows.

For Amazon work, the useful part is not file organization. It is that Cowork can combine a folder of client files with Kuudo's Amazon MCP servers and Skills, then produce a report, spreadsheet, listing audit, SQL query, or workflow plan without switching tools.

The building blocks

Kuudo's Amazon workflow stack uses three related concepts.

In practice, the MCP server gives Claude access and the Skill gives Claude the operating playbook.

For example, the Amazon Ads MCP can pull campaign and search-term data. A search-term mining Skill knows how to separate negative candidates, generic scale terms, branded defense terms, and rising-star queries.

Kuudo Amazon servers

Connect only the servers your workflow needs. Keep write tools approval-gated unless the workflow is deliberately automated.

Kuudo Amazon Skills

Skills can activate automatically when your request matches their purpose. You can also ask Cowork to use one explicitly by name.

If live MCP access is unavailable, several Skills can still work from a CSV or Seller Central export mounted into the Cowork folder.

Before you start

You need:

1. Claude Cowork access in Claude Desktop.
2. A Kuudo account with active Amazon connections.
3. The remote MCP URLs for the Kuudo servers you want to connect.
4. Owner approval on Team or Enterprise plans when connectors must be enabled organization-wide.

Permissions are inherited from the connected source. Cowork does not get more Amazon or Kuudo access than the authenticated user already has.

Add a Kuudo remote connector

Use the custom remote connector path for Kuudo servers unless your deployment appears in a connector marketplace.

1. Open Claude's connector settings.
2. Choose Add custom connector.
3. Name the connector clearly, such as Kuudo Amazon Ads.
4. Paste the remote MCP URL from your Kuudo deployment.
5. Add OAuth client details if your deployment requires them.
6. Complete the authentication flow.

Repeat for each server you need:

Amazon Ads MCP: {kuudo-amazon-ads-mcp-url}
Amazon Selling Partner MCP: {kuudo-amazon-selling-partner-mcp-url}
Openbridge MCP: {kuudo-openbridge-mcp-url}

Network requirements

Cowork may run locally, but remote connectors are reached through Claude's cloud connector path. That means a Kuudo MCP server must be reachable from Claude's connector infrastructure, not just from your laptop.

If a server is behind a VPN, private network, or corporate firewall, Cowork will not be able to connect unless your network team exposes an approved remote endpoint or allowlists the required cloud traffic.

Team and Enterprise setup

On Team and Enterprise plans, an Owner or Primary Owner may need to enable custom connectors before members can connect them.

Owner flow:

1. Open organization connector settings.
2. Add a custom web connector.
3. Enter the Kuudo remote MCP URL.
4. Configure OAuth details if required.
5. Save the connector for the organization.

Member flow:

1. Open personal connector settings.
2. Find the Kuudo connector.
3. Connect it with your own Amazon or Kuudo credentials.

Each member authenticates individually. Enabling a connector does not grant shared access to every account.

Restrict write actions

Amazon workflows often mix read-only reporting tools with live write tools. Keep those modes separate.

Recommended defaults:

Use Needs approval for listing and catalog changes unless the workflow has a separate human approval gate.

Enable connectors in a Cowork conversation

After the connector is added:

1. Open the Cowork conversation.
2. Open the connector menu from the composer.
3. Toggle on the Kuudo servers for that task.
4. Ask Cowork to list available tools before calling write actions.

Example verification prompt:

List the Kuudo Amazon tools available in this conversation.
Group them by server.
Do not call any write actions.

If you have many connectors enabled, use on-demand tool access so Cowork loads tool definitions only when needed.

Use Skills with live data or files

Cowork can combine live MCP data with files you mount into the workspace.

Useful patterns:

Example Amazon workflows

Search-term mining

Ask:

Pull the last 60 days of Sponsored Products search-term data and find negative candidates, generic gold keywords, branded defense terms, and rising queries.

Cowork uses the Amazon Ads MCP to gather the report, then applies the search-term mining Skill to produce an action list.

Campaign structure audit

Ask:

Audit my Sponsored Products portfolio for dead campaigns, budget concentration, and auto/manual balance.

The Skill checks the available fields, validates thresholds, and returns a portfolio-health report.

Listing optimization

Ask:

Review ASIN B0XXXXXXXX. Check title, bullets, images, and A+ Content. Propose a patch, but do not write anything live without approval.

Cowork reads listing context through the Selling Partner MCP and uses the listing optimizer Skill to produce a controlled diff.

Returns analysis

Ask:

Build a Q1 returns report by ASIN with top return reasons, dispositions, controllable issues, and red-flag products. Save it as a spreadsheet.

The returns Skill classifies issues and writes the deliverable to the mounted folder.

Warehouse SQL through the Agent Data layer

Ask:

Use the Amazon Agent Data layer to find my Amazon Ads tables, inspect the schema, and run SQL for spend by campaign last month.

The Openbridge Skill discovers tables, checks schema rules, and runs validated SQL through the query layer.

Amazon Marketing Cloud analysis

Ask:

Write an AMC query for new-to-brand reach across Sponsored Products and DSP last month. Explain which tables the query uses and why.

The AMC Skill produces SQL and explains the table choices before you schedule or export the workflow.

Recurring work

After Cowork builds a repeatable workflow, ask it to turn the steps into a recurring report or documented Skill:

Turn this search-term mining workflow into a weekly report.
Keep write actions approval-gated.
Save the runbook and output template in this folder.

For durable, data-backed automation, combine the Amazon Ads MCP or Selling Partner MCP with Skills and the Amazon Agent Data layer.

Security checklist

• Connect only servers you trust.
• Review OAuth scopes before signing in.
• Keep write tools on Needs approval by default.
• Disable write tools before unattended or research-style runs.
• Do not paste API keys, OAuth secrets, or client credentials into chat.
• Use mounted folders deliberately; Cowork can only work with folders you grant.
• Treat MCP tool output as untrusted input when it comes from unfamiliar servers.

Troubleshooting

Quick reference