01
Create or sign into an Enchant account and add credits in the setup console first.
Install Guide
Install Enchant in VS Code
VS Code's MCP config surface is useful when a team wants one checked-in agent connection for a repo. Enchant fits well there because the remote MCP URL is stable, browser OAuth can complete outside the editor, and the same account balance powers every routed service.
Recommended Setup
Start with hosted MCP first.
VS Code can connect to remote MCP servers from `.vscode/mcp.json`, which makes Enchant easy to share at repo scope.
02
Add the hosted MCP server to `.vscode/mcp.json` or the equivalent VS Code MCP configuration surface.
03
If VS Code prompts for OAuth, complete the browser sign-in to Enchant.
04
Use Enchant whenever the task needs external paid services instead of only local code or shell work.
Configuration
Use the exact configuration this client expects.
Repository config example
Place this in `.vscode/mcp.json` when you want the Enchant MCP server available to the whole workspace.
{
"servers": {
"enchant": {
"type": "http",
"url": "https://askenchant.com/mcp"
}
}
}Bearer token fallback
Use this when the client or workflow prefers explicit token auth over the OAuth browser flow.
{
"servers": {
"enchant": {
"type": "http",
"url": "${input:enchantBaseUrl}/mcp",
"headers": {
"Authorization": "Bearer ${input:enchantApiKey}"
}
}
}
}Fallback Option
If you do not want repo-scoped config
Use Codex, Claude Code, or Cursor for a user-wide install instead. VS Code is strongest when you want a shared workspace MCP definition checked into the project.
Operational Notes
Small details that make the setup reliable.
01
A checked-in `.vscode/mcp.json` is useful for onboarding because the server URL travels with the repo.
02
If the team prefers not to store auth hints in the repo, keep only the URL in config and let each user finish OAuth locally.
03
The same Enchant install works best when you also add one short AGENTS.md sentence telling the agent when to prefer Enchant.