This repository is a starter template for integrating DataDoe MCP with VS Code + GitHub Copilot in a secure, team-friendly way.
- What you can do with this repo
- What This Repo Includes
- Prerequisites
- How to get a DataDoe subscription and get MCP Key
- Configure DataDoe MCP in VS Code + Copilot
- Example prompt library starter pack
- VS Code Copilot Settings
- DataDoe MCP Configuration Options
- How to Get Help
- Connect GitHub Copilot chat to DataDoe MCP in a secure way.
- Ask Amazon seller questions using DataDoe-backed data.
- Reuse this setup as a template for new Amazon-focused assistant projects.
- VS Code + Copilot MCP setup via
.vscode/mcp.json - Secure secret handling with
.envand.env.example - Agent instructions in
AGENTS.mdfor GitHub Copilot .gitignoreconfigured to protect secrets
- Visual Studio Code (latest stable)
- GitHub Copilot extension installed and active
- A valid DataDoe subscription
- A generated DataDoe MCP key
- Go to app.datadoe.com
- Create account
- Purchase subscription
- Accept Terms and Conditions and Privacy Policy
- Go to
Integrations - Click
MCPtile (/integrations/mcp) - Click
MCP Key, add name + expiration, clickCreate - Copy key and store in a secure secret manager
This repository already includes .vscode/mcp.json configured with a secure input prompt for your API key. When Copilot first connects to the DataDoe MCP server, VS Code will prompt you to enter your API key.
The config uses VS Code's built-in input variables so your key is never stored in the file:
{
"inputs": [
{
"type": "promptString",
"id": "datadoe-key",
"description": "DataDoe MCP API Key",
"password": true
}
],
"servers": {
"datadoe": {
"type": "http",
"url": "https://api.datadoe.com/mcp/v1",
"headers": {
"datadoe-mcp-key": "${input:datadoe-key}"
}
}
}
}Replace the config with your key inline:
{
"servers": {
"datadoe": {
"type": "http",
"url": "https://api.datadoe.com/mcp/v1",
"headers": {
"datadoe-mcp-key": "YOUR_API_KEY"
}
}
}
}- Open the Command Palette (
Cmd+Shift+P/Ctrl+Shift+P) - Run MCP: List Servers
- Confirm
datadoeappears and shows as connected
Reference: VS Code MCP server docs
To help you start faster with an AI Agent + DataDoe MCP workflow, this repo includes a small prompt library at:
.vscode/prompts/EXAMPLES.md
Use it as a starter pack:
- Open
.vscode/prompts/EXAMPLES.md. - Copy a prompt block and adjust placeholders (for example
{{seller_name}}) to your account context. - Run the prompt in GitHub Copilot chat with DataDoe MCP enabled.
- Save your own high-performing prompts in the same file to build a reusable internal playbook.
VS Code + GitHub Copilot uses these configuration files:
- Workspace MCP config:
.vscode/mcp.json(shared with this repository team) - Agent instructions:
AGENTS.md(team-shared assistant guidance for Copilot) - VS Code settings:
.vscode/settings.json(workspace-level editor settings)
To customize Copilot behavior for this project, edit AGENTS.md at the repository root.
Reference: VS Code MCP configuration reference
The MCP server is configured in .vscode/mcp.json using servers key with type: "http":
{
"servers": {
"datadoe": {
"type": "http",
"url": "https://api.datadoe.com/mcp/v1",
"headers": {
"datadoe-mcp-key": "${input:datadoe-key}"
}
}
}
}Caution
Treat DATADOE_MCP_KEY like a password. Do not publish repositories, screenshots, or logs that contain this key.
Never commit real keys to git.
If a key is exposed, rotate it immediately.
- Email: contact@datadoe.com
- GitHub Copilot Documentation: https://docs.github.com/en/copilot
- VS Code Documentation: https://code.visualstudio.com/docs
- VS Code MCP servers: https://code.visualstudio.com/docs/copilot/customization/mcp-servers