Helium 10 MCP server for your AI

No. PopMCP is a registered OAuth client of Helium 10, so you open Helium 10 in PopMCP, click Authorize with Helium 10, sign in to Helium 10 and click Authorize. The sign-in uses OAuth 2.1 with PKCE, and there is no key to copy, no developer app to create and no callback URL to register. The connection sees what the Helium 10 account you sign in with sees.

Diamond or above. Helium 10 includes its MCP with Diamond (US$359 a month, or US$279 a month billed annually) and the plans above it; Platinum does not include it. On a plan without it the sign-in still works, but Helium 10 returns no tools, so PopMCP stops and tells you the plan is the reason rather than connecting an empty server.

Every tool Helium 10 gives your account. PopMCP mirrors Helium 10's own MCP server live: when you connect it reads the tool list your plan includes and turns each one into its own tool with Helium 10's parameters. That covers Keyword Research (Cerebro reverse-ASIN, Magnet and the keyword database), Product Research (Black Box), Brand Analytics, Keyword Tracking, Listings, Listing Builder, Profits, Inventory and Ads, across Amazon in 24 marketplaces plus the Walmart and TikTok Shop data Helium 10 offers. list_tools re-reads the list and call_tool runs any tool by name, so one Helium 10 adds later works straight away.

Only on a connection with writes allowed. sync_listing_to_amazon publishes a listing and overwrites the live one, and manage_ads_campaigns changes live bids, budgets and campaign states. Both wait until an owner or admin allows write actions in PopMCP; on a read-only connection, the default, call_tool still runs reads but refuses those two. Drafting with generate_listing or rewrite_listing_section changes nothing on Amazon, and even with writes on, the AI is told to show you the final text and get your go-ahead before it publishes.

Through Helium 10's Ads Query, which runs in five steps: get_ads_query_platforms, get_ads_query_list, get_ads_query_schema, get_ads_query_materials, then execute_ads_query. The middle steps return the fields you can query and the profile and campaign IDs a query needs, so the AI builds it from Helium 10's own names instead of guessing them. Each of those tools tells the AI where it sits in the order, so spend, ACoS or ROAS by profile and date is one request from you.

Helium 10 signs a connection out after a period of inactivity. When that happens the AI gets a plain message that the sign-in has ended instead of a raw token error. Reconnect Helium 10 in PopMCP: it is one click and a sign-in to Helium 10, with nothing else to set up again.

No. PopMCP hosts it and gives you a Streamable HTTP MCP URL. There is nothing to deploy, no callback URL to register, and no infrastructure to keep running or patch.

Any client that supports a remote Streamable HTTP MCP server: Claude Desktop, Claude Web, Claude Code, ChatGPT custom connectors, Codex and the Codex CLI, OpenCode and Z.ai's ZCode, as well as editors such as Cursor, Windsurf and Zed. Your client signs in to PopMCP with OAuth; the provider credential never leaves the server.

Connect Helium 10 in PopMCP first, then run claude mcp add --transport http popmcp https://app.popmcp.com/mcp in a terminal. Inside Claude Code, run /mcp and sign in to PopMCP in the browser window it opens, ticking Helium 10 on the consent screen. The Helium 10 tools are then available in that session, and no Helium 10 credential is stored on your machine.

Yes. The Helium 10 catalog is small enough that all 43 tool definitions load into every conversation, so your AI never has to search for one before it can call it.

A tool is something your AI calls, and there are 43 here. A trigger is an event PopMCP watches for on its own. Helium 10 has no triggers yet, so everything on this page happens when your AI calls a tool.