Skip to main content

Connect Amazon Seller Central, Vendor Central and Ads data to Claude Code and Cursor

To query Amazon data from Claude Code or Cursor, the coding agent needs live access to your Seller Central, Vendor Central and Amazon Ads data, and Nova's MCP connector gives it that access through one remote MCP server. Add https://mcp.novadata.io/api/mcp to Claude Code with one command, or to Cursor's mcp.json, sign in to Nova, and the agent can read sales, profit, ads, stock and listings while it builds scripts, dashboards or reports.

https://mcp.novadata.io/api/mcp

Before you start

  • A Nova account with your Amazon accounts connected. A trial works.
  • Pick how the agent signs in:
    • Nova sign-in (OAuth): the agent opens Nova's sign-in in your browser. It sees every workspace you can open, and it can use Nova's write tools (cost imports, events) after you confirm each one.
    • Workspace token: in the Nova app, open the Nova MCP page and click "Generate a token instead". The token reads one workspace and cannot write. Use it for scripts, CI and machines without a browser. It is shown once.

Claude Code

Nova sign-in:

claude mcp add --transport http nova https://mcp.novadata.io/api/mcp

Then run /mcp in Claude Code and sign in to Nova in the browser.

Workspace token:

claude mcp add --transport http nova https://mcp.novadata.io/api/mcp --header "Authorization: Bearer <your-nova-token>"

Scope: the server is added for the current project by default. Add --scope user to use it in every project, or --scope project to share it with your team through .mcp.json (keep the token in an environment variable such as NOVA_MCP_TOKEN, never in the file).

Cursor

Add Nova to .cursor/mcp.json in your project, or ~/.cursor/mcp.json for every project.

Nova sign-in:

{ "mcpServers": { "nova": { "url": "https://mcp.novadata.io/api/mcp" } } }

Cursor opens Nova's sign-in the first time a tool is called.

Workspace token:

{ "mcpServers": { "nova": { "url": "https://mcp.novadata.io/api/mcp", "headers": { "Authorization": "Bearer ${env:NOVA_MCP_TOKEN}" } } } }

What to ask first

  • "List my Nova accounts and the marketplaces in each."
  • "Pull net sales, net profit and ad spend per marketplace for last month and write it to a CSV."
  • "Write a script that sends me yesterday's top 5 sales movers every morning."

How Nova customers use this

Real requests from Nova customers, names removed.

  • “Capture real Nova responses as test fixtures for our dashboard, then sync traffic, ads and inbound data into it every night.”

    list_accounts then query_advertising then query_metrics then query_sqp then query_listing_health then query_inbound_shipments

    It saved sample responses so the dashboard's unit tests and ingest validation run against real data, then ran a nightly sync of page views, campaigns, placements, listing health and inbound shipments.

  • “Rebuild month to date against last month and last year per client, to check our new calculation script matches the live dashboard.”

    list_accounts then query_metrics

    It pulled the month-to-date comparisons per account as the reference set for the script test.

  • “Our automated weekly PPC recap shows a different margin than the real one. Find the bug.”

    describe_metric then list_metrics then list_tags then query_metrics

    It read Nova's definitions of net profit, net sales and net margin, then recomputed the week's spend, sales and margin per brand to compare with the flow's formula.

Limits

  • Workspace tokens read one workspace and cannot write. Nova sign-in is needed for writes, and each write is previewed and confirmed.
  • 120 requests a minute per user or token. After a trial ends without a subscription, 15 data calls a day.
  • Nova has no advertising write tool: bids, budgets and campaigns are read only.
  • Treat the token like a password. Revoke it on the Nova MCP page, where each token shows when it was last used.

Your Amazon numbers, one question away