From Cursor you run Amazon advertising and operations tasks in the same window you build in: pull live campaign, search-term or catalog data into the agent, prototype an Amazon workflow against it, and keep every write behind Cursor's tool approval and your workspace policy.

Cursor reads MCP servers from a JSON file. Add your private Kuudo MCP server once, per project or for every project, and Cursor's agent can call the Amazon Ads MCP, the Amazon Selling Partner MCP and the Amazon Vendor Central MCP tools your deployment exposes.

Your MCP server hostname is private to your deployment. It comes from your cloud provider, belongs to your environment, and is not shared across customers. Replace {your-private-mcp-host} with the private host shown in your dashboard.

Prerequisites

Cursor installed and signed in.
A connected workspace with access to your private MCP server.
A dashboard API key from the Keys tab.
The private MCP host assigned to your deployment.

Copy prompt

Paste this into Cursor's agent if you want it to walk you through setup:

Walk me through setting up my private MCP server in Cursor, step by step.

Use Cursor's mcp.json configuration, not a local wrapper or one-off script.

Use the private host from my dashboard:
https://{your-private-mcp-host}/mcp

Read the key from my MCP_API_KEY environment variable with ${env:MCP_API_KEY}.
Do not ask me to paste or share the raw key in chat, and do not write the raw key
into any file. If MCP_API_KEY is not set, tell me to export it from my dashboard first.

Ask me whether to save the server for this project (.cursor/mcp.json) or for every
project (~/.cursor/mcp.json), then show me the file contents before saving.

1. Set your local key

Set the API key in the environment Cursor starts from:

export MCP_API_KEY="mcp_live_..."

For repeated use, store it in your shell profile or secret manager, and start Cursor from an environment that has it. Do not commit the raw value to the repository.

2. Add the MCP server

For one repository, save this as .cursor/mcp.json in the project root. For every project, save it as ~/.cursor/mcp.json.

{
  "mcpServers": {
    "private-mcp": {
      "url": "https://{your-private-mcp-host}/mcp",
      "headers": {
        "Authorization": "Bearer ${env:MCP_API_KEY}"
      }
    }
  }
}

Cursor resolves ${env:MCP_API_KEY} from the environment when it connects, so the key stays out of the file. A project file is safe to commit for that reason; the raw key never is.

3. Verify the server

Restart Cursor or reload the MCP server list after saving the file. In Cursor's settings, confirm private-mcp is enabled and shows as connected.

Then ask the agent:

"What MCP tools are available from private-mcp?"

If the server is connected, the agent lists the Amazon tools your deployment exposes.

Troubleshooting

Unauthorized or 401 errors

Make sure MCP_API_KEY is set in the environment Cursor was launched from, and that the header reads Bearer ${env:MCP_API_KEY}. The key must belong to the same workspace as the private MCP server.

Server not listed

Check that the file is named mcp.json, sits in .cursor/ at the project root or in ~/.cursor/, and is valid JSON. Then reload the MCP server list.

Tools not available in a chat

Start a new agent chat after changing MCP config. Cursor asks for approval before it runs an MCP tool by default; approve the call, or allowlist read-only tools you trust.

Slow responses

Check your network path to the private host and confirm the cloud deployment is healthy. The hostname is specific to your environment, so connectivity issues are usually tied to your cloud provider, DNS, firewall, or deployment status.

Run Amazon tasks from Cursor

Start with read-only prompts:

"List my Amazon Ads profiles, then show last week's Sponsored Products spend by campaign."
"Pull the search-term report for my top campaign and flag terms with spend and no orders."
"Show Fulfillment by Amazon (FBA) inventory for my ten best-selling ASINs."

For write-capable work such as a bid or budget change, ask the agent to explain the proposed change and wait for your approval before it calls any mutating tool. Write tools also apply your workspace policy, so a change can wait on a person even when Cursor would run it.

Add reusable workflows

Kuudo Skills package repeatable Amazon workflows, such as a campaign structure audit or budget pacing, with the inputs each one needs and the limits it keeps. See the Amazon Agent Skills reference, and the MCP client configuration page for the settings every client shares.

<- Previous Quick Start: Codex Next -> Quick Start: OpenClaw MCP

Quick Start: Cursor