Helium 10

Name: Helium 10 MCP Server
Availability: InStock
Author: Helium 10

E-commerce34 tools

Query Amazon keyword research, listing scores, P&L and ad performance from your AI assistant. The directory record carries a rare full-paragraph read-only disclosure — and Helium 10's own documentation, updated the day we checked, now describes campaign and COGS write tools the paragraph does not mention.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on 19 August 2026.

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect Helium 10 via MCP

https://mcp.helium10.com/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Helium 10 Tools & Capabilities (34)

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

The directory's read-only paragraph is out of date. Helium 10's documentation, updated 2026-08-19, describes Amazon Advertising campaign management and COGS write tools. The 2026-08-16 directory record states the connector cannot create, change or delete anything. Trust the vendor reference over the listing.
The directory undercounts the surface by fourteen tools. 48 documented against 34 listed, counted 2026-08-19. Every write tool is among the missing.
Manage mode costs 2% of ad spend. Helium 10 states advertising data is not exposed to MCP unless the ad profile is in Manage mode, and that Manage mode incurs a 2% fee on all ad spend in that account.
Entitlement gaps narrow answers rather than hiding tools. Brand Analytics needs Diamond plus Brand Registry; keyword sales data needs Platinum or above and North America only; keyword research is capped at 100 searches per month on Platinum. A narrowed response is not visually distinct from a complete one.
1,000 tool calls per month, with no top-ups. Helium 10 states top-up packs are not currently available and the allowance resets on renewal.
Data is not live. Helium 10 documents periodic refresh — most metrics daily, Brand Analytics weekly — and query latency of roughly 2 to 15 seconds. Inactive products are searchable only within 360 days.
We could not verify tool behaviour ourselves. The endpoint returned HTTP 401 to an anonymous request on 2026-08-19, so no inputSchema and no readOnlyHint or destructiveHint annotations were readable. Every tool name here comes from Anthropic's snapshot or Helium 10's published reference; none carries a safety annotation we could read, and none should be assumed annotated.
Response fields are not published. Helium 10 does not document what each tool returns, so we cannot state from a public source whether any response can carry buyer-level Amazon order data. Nothing in the documented tool set suggests it does, and that is an absence of evidence, not evidence of absence.
One scope covers everything. mcp:tools is the only scope on either descriptor. It expresses no read/write distinction, so the OAuth grant cannot be narrowed to the read half of the product.
Prompts are unconfirmed. Anthropic's snapshot lists none, and the gated endpoint blocked our own check.
Amazon's own terms sit underneath. Helium 10's terms state it has no affiliation with or endorsement from Amazon, that it accesses Amazon data through your authorization of your Seller Central account, and that interpreting any applicable third-party terms is the customer's responsibility. Its acceptable-use clause separately prohibits reselling or commercially exploiting access to the service. We report the vendor's stated position and give no legal advice — read the terms yourself before redistributing anything an agent pulls out of this connector.
A directory field artefact. The name value in Anthropic's snapshot carries a trailing space, which matters only if you match on it programmatically.

Frequently asked questions

Is the Helium 10 MCP server really read-only?

Not any more, and the directory record has not caught up. Anthropic's 2026-08-16 snapshot carries a paragraph stating the connector cannot create, change or delete anything. Helium 10's own documentation, updated 2026-08-19, describes a V2 release with Amazon Advertising campaign management and per-SKU COGS write tools. Treat the paragraph as describing an earlier build.

What does execute_ads_query do — does it change my campaigns?

It runs a read query against advertising reporting data. Helium 10 documents a five-step workflow: pick a platform, explore the hierarchy, view the query schema, look up campaigns, then run the query. The action verb describes executing a query, not an ad change. Campaign edits go through a separate documented tool that the directory listing does not include.

Which Helium 10 plan do I need for MCP?

Diamond or higher. Helium 10's setup documentation lists a Diamond plan as a prerequisite and states MCP carries no additional fee at that tier. The monthly allowance is 1,000 tool calls, which Helium 10 estimates supports 500 to 1,000 conversations. Top-up packs are not currently sold, and the allowance resets when your subscription renews.

Can a Helium 10 agent see my Amazon customers' names or addresses?

Nothing in the documented tool set returns buyer-level records. The tools cover keywords, listings, competitors, P&L, inventory and advertising aggregates. Helium 10's terms do define a separate category of customer data collected from Seller Central, but no MCP tool in the directory listing or the vendor's reference is documented as returning it. Response fields are not enumerated publicly.

What OAuth scopes does the Helium 10 MCP server request?

One named scope, mcp:tools. Both the RFC 9728 protected-resource descriptor and the RFC 8414 authorization-server metadata advertise exactly that single entry, verified live on 2026-08-19. There is no separate read scope and no separate write scope, so the grant cannot express the read-only versus campaign-write distinction the tool surface actually contains.

Does Helium 10 document more MCP tools than Anthropic's directory lists?

Yes — 48 against 34. Helium 10's tool reference names fourteen tools absent from Anthropic's 2026-08-16 snapshot, including every advertising campaign management and COGS write tool. The directory lists one name the reference does not. Read the vendor reference, not the listing, if you want to know what an approval actually reaches.

Sources

Getting Started with Helium 10 MCP — https://kb.helium10.com/hc/en-us/articles/51580564409883-Getting-Started-with-Helium-10-MCP (fetched 2026-08-19 via the Zendesk help_center article JSON API, which returns clean article text; article updated_at 2026-08-19. This is the documentation URL Anthropic's directory publishes. Source of the 48-tool reference table, the Diamond plan requirement, the 1,000-call allowance, the five-step ads query workflow, the write-capability description, the 2% Manage-mode fee and the data-freshness limits) · retrieved 2026-08-19
Helium 10 knowledge base article search — https://kb.helium10.com/api/v2/help_center/articles/search.json?query=MCP%20Tool%20Usage%20Add-on (fetched 2026-08-19; 98 results, of which exactly one is a dedicated MCP article — no separate add-on or pricing article is published) · retrieved 2026-08-19
Cerebro (Plus Magnet) Platinum entitlement changes — https://kb.helium10.com/hc/en-us/articles/49174506499099 (fetched 2026-08-19 via the same JSON API; 100 keyword searches per month on Platinum, resetting on the billing cycle, no rollover) · retrieved 2026-08-19
Helium 10 terms and conditions — https://www.helium10.com/terms-and-conditions/ (fetched 2026-08-19; the "Connected AI Tools; Authorized Sessions" clause naming MCP explicitly, the Amazon third-party-platform disclaimer, the "Your Customer Data" definition and the acceptable-use restrictions) · retrieved 2026-08-19
Live RFC 9728 protected-resource descriptor — https://mcp.helium10.com/.well-known/oauth-protected-resource (fetched 2026-08-19; 200, 194 bytes, scopes_supported: ["mcp:tools"]. The path-append form at /.well-known/oauth-protected-resource/mcp returns a byte-identical body; the path-insert form at /mcp/.well-known/oauth-protected-resource returns 404 with a zero-byte body) · retrieved 2026-08-19
Live RFC 8414 authorization-server metadata — https://h10api.pacvue.com/authhub/api/scenarios/mcp/.well-known/oauth-authorization-server (fetched 2026-08-19; 200, issuer https://members.helium10.com/authhub/api/scenarios/mcp, S256, dynamic registration, five grant types, scopes_supported: ["mcp:tools"]. Both .well-known/oauth-authorization-server forms on the MCP host return 404) · retrieved 2026-08-19
Live anonymous probe — 2026-08-19: an initialize POST to https://mcp.helium10.com/mcp returns HTTP 401 with content-length: 0 and a standard www-authenticate: Bearer resource_metadata="…/oauth-protected-resource/mcp" header. No authentication was attempted and no tool was called · retrieved 2026-08-19
Anthropic connector directory — https://claude.ai/directory/e336ede2-5687-4590-a60b-12c3ab56fc63 (snapshot 2026-08-16; 34 tool names, prompt_names empty, permissions published as a full paragraph, name carrying a trailing space. The 1,434-of-1,897 count of records with no permissions field was computed from this snapshot on 2026-08-19) · retrieved 2026-08-16
Documentation discovery, 2026-08-19: kb.helium10.com/robots.txt is Zendesk's default help-centre file, disallowing admin and ticketing paths and publishing https://kb.helium10.com/hc/sitemap.xml; www.helium10.com/robots.txt publishes sitemap_index and two further sitemaps. No llms.txt exists on either host (both 404), no Content-Signal directive appears in either robots file or in response headers, and the .md suffix form is not applicable to a Zendesk help centre. The pricing page at https://www.helium10.com/pricing/ renders its plan tiers client-side, so no dollar figure is cited here — the plan requirement is taken from the KB article's prose instead · retrieved 2026-08-19