Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
npx -y @datadive-tools/[email protected]Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
claude mcp add datadive-tools-mcp -- npx -y @datadive-tools/mcp@0.21.0รันในเทอร์มินัล
{ "mcpServers": { "datadive-tools-mcp": { "command": "npx", "args": [ "-y", "@datadive-tools/[email protected]" ] } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
An MCP server that lets Claude (or any MCP-compatible client) query your DataDive niches, keywords, competitors, and Rank Radar data using your existing API key.
Runs locally on your machine over stdio. Your API key never leaves your machine
except as the x-api-key header on requests to .
MCP server for DataDive — query your niches, keywords, competitors, and Rank Radar data from Claude Desktop, Claude Code, or Cursor.
api.datadive.toolscom."z515cGOFg3?"/api-key).Requires the Billing Manager or Owner role and the Standard plan or higher. Contact your org admin if you can't see the page.
Edit your config file:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonAdd the datadive entry under mcpServers:
{
"mcpServers": {
"datadive": {
"command": "npx",
"args": ["-y", "@datadive-tools/mcp"],
"env": {
"DATADIVE_API_KEY": "YOUR_API_KEY"
}
}
}
}
Restart Claude Desktop. You should see datadive in the tools menu.
claude mcp add datadive -- npx -y @datadive-tools/mcp
# Then add the env var via:
# claude mcp add datadive --env DATADIVE_API_KEY=YOUR_API_KEY -- npx -y @datadive-tools/mcp
Or edit .mcp.json in your project / ~/.claude/mcp.json globally with the
same JSON shape as above.
Settings → MCP → Add new MCP server and paste the same JSON shape:
{
"datadive": {
"command": "npx",
"args": ["-y", "@datadive-tools/mcp"],
"env": { "DATADIVE_API_KEY": "YOUR_API_KEY" }
}
}
Ask Claude: "List my DataDive niches."
You should see a tool call to list_niches and a JSON response with your
niches, plus pagination metadata. If you don't, see Troubleshooting below.
All data is scoped to the organization that owns the API key. Most tools are
read-only. The tools that change something are marked above; the ones that
cannot be undone also require an explicit confirm: true — see
Tools that change something.
Six tools cannot be undone, so they require an explicit confirm: true
argument. Called without it, they change nothing and return a note asking the
assistant to confirm the cost with you first:
create_niche_dive, redive_niche — spend dive tokens (scales with
numberOfCompetitors).create_rank_radar — spends Search Term tokens (scales with
numberOfKeywords).generate_listing_copy — spends one AI Copywriter prompt per call.delete_niche, delete_rank_radar — destroy data permanently.Check your remaining balance any time with get_quota.
create_rank_radar uses that first, unconfirmed call to preview the creation
against the API, so the note it comes back with can tell you something specific
rather than only the token cost — for instance that the product family you asked
for is already tracked by another of your Rank Radars, which would spend Tracked
Search Terms on it twice. The preview creates nothing and spends nothing, and a
warning never blocks the creation: two Rank Radars on one family is how you
track two different sets of search terms and keep separate statistics.
The other write tools — pause_rank_radar, resume_rank_radar and the three
*_rank_radar_search_terms tools — need no confirmation. They only move Daily
Tracked Keywords capacity, which is freed again when you pause, and each is
undone by its counterpart.
add_niche_keywords asks for confirm: true only when it would spend: on a
niche dived in the last 24 hours its first call adds the keywords for free, while
on an older niche that call changes nothing and returns the Dive token cost of the
re-dive the add triggers. remove_niche_keywords and the keyword exclusion
tools are free and need no confirmation.
To skip the per-call confirmation (e.g. in an automated setup), set
DATADIVE_AUTO_CONFIRM_WRITES=true in your client config — then all six run
without confirm, deletes included.
None of the three is safe to retry — each call spends tokens again and
creates a separate dive / re-dive / Rank Radar, even with identical arguments. If
a call errors or times out, check get_dive_status / list_niches /
list_rank_radars for what already exists before calling again.
Dives are asynchronous. create_niche_dive returns a diveId and an
estimated completion time immediately; poll get_dive_status with that diveId
until it reports success, which carries the new nicheId you then feed to
list_niches, get_niche_keywords, and the other niche tools.
redive_niche refreshes a niche you already have rather than creating another
one, and it keeps the same nicheId — so rank radars and reports built on that
niche follow the refreshed data. It takes a mode:
same_competitors — re-dive the niche's current competitor set. Nothing else
to supply; use it purely to pull in current sales, price and keyword data.discover — search for a fresh competitor set of numberOfCompetitors ASINs.
Steer it with heroAsin (the seed to build around; defaults to the niche's
highest-selling competitor, preferring one of your own ASINs), lockedAsins
(kept no matter what discovery finds) and excludedAsins (never selected).⚠️ For
create_niche_dive,marketplaceuses full Amazon domain suffixes (com,co.uk,com.mx,co.jp, …) — e.g. the UK marketplace isco.uk, notuk.
If a tool call returns an error message, it'll be one of these — each maps to a specific HTTP status from the DataDive API.
If the server itself fails to start, look in your MCP client's log output:
DATADIVE_API_KEY environment variable is required — the env var isn't
being passed through to the binary. Confirm your client config has it under
env (not args), and that you've restarted the client after editing.api.datadive.tools with your API key as the x-api-key header.npm install
npm run build # tsup -> dist/index.js (with shebang)
npm test # vitest run
npm run typecheck # tsc --noEmit
npm run lint # eslint
Test the binary end-to-end with the MCP Inspector:
DATADIVE_API_KEY=YOUR_API_KEY npx @modelcontextprotocol/inspector dist/index.js
The repo uses Changesets:
npx changeset # add a changeset describing the change (patch/minor/major)
git commit -am "fix: ..."
git push
A "Version Packages" PR opens automatically. Merging it bumps the version, updates CHANGELOG.md, and publishes to npm with provenance.
MIT — see LICENSE.
MCP server for DataDive — query your niches, keywords, competitors, and Rank Radar data from Claude Desktop, Claude Code, or Cursor.
{ "mcpServers": { "datadive-tools-mcp": { "command": "npx", "args": [ "-y", "@datadive-tools/[email protected]" ] } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
@datadive Tools/mcp ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-14 MCP server for DataDive — query your niches, keywords, competitors, and Rank Radar data from Claude Desktop, Claude Code, or Cursor.