Connect MerchantFlow to VS Code (GitHub Copilot)
Connect MerchantFlow to VS Code via GitHub Copilot MCP support so Copilot can read your ecommerce data.
Connect MerchantFlow to VS Code
GitHub Copilot supports MCP servers as of VS Code v1.95+. Copilot Chat can call MerchantFlow tools from any file you're editing.
Prerequisites
- VS Code v1.95 or newer
- GitHub Copilot active subscription
- A MerchantFlow account on any paid plan
Step 1: Copy the config
From Settings → Developer → MCP (/dashboard/settings/developer/mcp) in MerchantFlow, click Install in VS Code and copy the config.
Step 2: Create .vscode/mcp.json
In your project root, create .vscode/mcp.json (or add to the existing file) with:
{
"servers": {
"merchantflow": {
"url": "https://merchantflow.ai/api/mcp",
"type": "http"
}
}
}Step 3: Reload the window
Command palette (Cmd+Shift+P / Ctrl+Shift+P) → Developer: Reload Window.
Step 4: Authorize
The first Copilot chat that uses a MerchantFlow tool will open a browser window for OAuth. Click Allow access.
Step 5: Ask Copilot
Open the Copilot Chat panel and ask in plain English -- there is no special prefix or server-mention syntax. Copilot picks the tool itself:
What's my bank runway at current burn?
Copilot will call get_bank_balance and answer.
If you want to point it at a specific tool, VS Code lets you reference any available tool by typing # followed by the tool name in the chat input (for example #get_bank_balance). You can also open Configure Tools in the chat input to see and toggle every MerchantFlow tool Copilot has loaded.
Add the Skill file to Copilot instructions
Download https://merchantflow.ai/api/mcp/skill?format=vscode and save it as .github/copilot-instructions.md in your repo. Copilot automatically reads this file for every chat.
Last updated on
Connect MerchantFlow to Windsurf
Connect MerchantFlow to Windsurf via MCP so Cascade can reason about your store data alongside your code.
MCP Personal Access Tokens (Headless Connections)
Generate scoped personal access tokens to connect MerchantFlow MCP from headless environments - VMs, SSH sessions, CI runners, and dev containers - without an OAuth browser flow.