Doe gives you the complete Amazon data layer — every metric, clean and AI-ready — so your AI runs on your terms.
GitHub Copilot already answers your questions, writes code, and opens PRs through Workspace. It just can't see your Amazon. Until you wire DataDoe in.
DataDoe is the Amazon data layer that bridges Seller Central, Advertising, Vendor Central and SP-API to GitHub Copilot inside VS Code via MCP — the open standard for connecting live data to AI. Connect your Amazon accounts once via OAuth, drop the DataDoe MCP URL into your .vscode/mcp.json, and every Copilot Chat answer, inline completion and Workspace PR sees your real, live Amazon data.
Yes — every Copilot surface in VS Code that supports MCP. That includes Copilot Chat (sidebar and inline), inline ghost-text completions when contextually relevant, and Copilot Workspace for spec-to-PR agent runs. One DataDoe MCP server, all surfaces.
Model Context Protocol is the open standard for connecting live data sources to AI agents. GitHub Copilot in VS Code supports MCP natively — paste a server URL into .vscode/mcp.json or your user settings and Copilot can read that data source whenever it's relevant. DataDoe runs as an MCP server, so Copilot reads your Amazon data securely without API keys, copy-paste or custom plumbing.
Two options. For team-wide setup, add it to .vscode/mcp.json in your repo so every contributor inherits the connection. For personal setup, add it to your VS Code user settings under the MCP servers section. The DataDoe URL is workspace-scoped and authenticated, so each user keeps their own credentials.
Yes — that's how Workspace ships work. You hand it a spec, Copilot Workspace plans, edits, tests and opens a PR against your repo. With DataDoe wired in, those PRs land with code that already runs against your live Amazon — no mocks to swap out, no fixtures to maintain. Your team reviews and merges through your existing GitHub workflow.
Yes. DataDoe is Amazon-audited and SP-API compliant. Your data flows through secure OAuth and an authenticated MCP endpoint, isolated per tenant. Copilot Business and Enterprise apply your existing audit logs, content filters and code-reference policies to every Amazon-aware completion. GitHub never trains on your business data.
About fifteen minutes. Connect your Amazon accounts via one-click OAuth (~2 min), paste the DataDoe MCP URL into your .vscode/mcp.json or VS Code settings (~30 sec), then your first Copilot Chat answer is grounded in real Amazon data. No extension to install, no engineers required for the integration itself.
Any Copilot tier that includes Chat and MCP support works with DataDoe — Pro, Business and Enterprise. Workspace requires the appropriate plan as well. The DataDoe MCP server itself is plan-agnostic; it just needs a Copilot client that can read MCP configs.
Same underlying DataDoe MCP — different developer experience. Cursor is a Composer-first fork of VS Code with stronger inline agent flows. Codex is async cloud agents on OpenAI models. GitHub Copilot in VS Code is the most enterprise-deployed assistant — works in the editor your team already uses, ships through your existing GitHub PR review process, and applies your Copilot Business compliance controls automatically.
Yes. DataDoe handles multi-account, multi-brand, multi-marketplace setups natively. Vendor Central, Seller Central and Advertising accounts unified into one MCP endpoint. Agencies use it to ship custom internal tools across dozens of client brands without per-client SP-API rebuilds. B2B SaaS startups skip the 6-month integration sprint and start shipping product on day one.
Every integration. Full onboarding support. If it’s not the best decision you made in 2026, you can cancel anytime.
Know what makes you money
Catch problems instantly
Connect anything with API & MCP
Replace tools with your own apps
Access Amazon-audited infrastructure
Every integration. Full onboarding support. If it’s not the best decision you made in 2026, you can cancel anytime.